APIMan 1.2.2-SNAPSHOT not available in JBoss public repo about apiman

[kunallimaye]

Obvious workaround is the download and build apiman locally. Not ideal though

[EricWittmann]

Our artifacts are actually deployed to sonatype. You can see that 1.2.2-SNAPSHOT is available:

https://oss.sonatype.org/content/repositories/snapshots/io/apiman/apiman-manager-api-core/1.2.2-SNAPSHOT/

Sadly we neglected to add the sonatype snapshot repository to the relevant pom.xml files. :( I'll get that taken care of asap.

[kunallimaye]

Thanks Eric.

Any reason why we wouldn't add to JBoss Public though?

[EricWittmann]

We used to publish to jboss public, but it sometimes took a couple of days for artifacts to be rsync'd over to central. This was problematic for releases and for some downstream projects.

I guess there's no reason we couldn't go back to jboss just for snapshot releases. But I think central tends to be more stable and is easier to deploy into.

[msavy]

And another reason is that JBoss Nexus is slow for those of us outside of US (and also slow for CI, for whatever reason - I think they have transparent caches for central but not JBoss ).

On 10 Feb 2016, at 01:13, Eric Wittmann [email protected] wrote:

We used to publish to jboss public, but it sometimes took a couple of days for artifacts to be rsync'd over to central. This was problematic for releases and for some downstream projects.

I guess there's no reason we couldn't go back to jboss just for snapshot releases. But I think central tends to be more stable and is easier to deploy into.

—
Reply to this email directly or view it on GitHub #371 (comment).

[EricWittmann]

@kunallimaye - by the way, can you confirm the original bug report? I'm looking at the quickstarts and remembering that they don't actually reference any apiman components.

Did you perhaps mean that the apiman-plugins repository failed to build?

[kunallimaye]

@EricWittmann you are correct. I meant apiman-plugins and not apiman-quickstarts.

Apologies for the confusion.