Artifacts are not propagating to Maven Central

[marc0der]

Just looked at pulling this lib in, but it seems to be stuck on a very old version (0.2.0) on Maven Central, whild Bintray has it a 1.1.0. Many organisations don't allow JCenter directly, so it would be very beneficial if it was published to Maven Central too.

[howyp]

@marc0der AFAIK HMRC artifacts only go to Bintray now, mainly because of propagation speed being pretty slow for Maven Central/Sonatype. @charleskubicek maybe could have a mirror there?

[SteveSmithTech]

@marc0der Good to hear from you, and thanks for the above. HMRC artifacts are published to bintray.com/hmrc and there are no plans to change that policy. Maven Central, Sonatype etc. are deemed slower and less reliable. JCenter is not actually involved at all.

The 0.2.0 artifact you refer to should not be present.

[marc0der]

Bintray actually encourage you to propagate your artifacts to Maven Central (https://bintray.com/docs/usermanual/uploads/uploads_syncingartifactswithmavencentral.html). They provide you a convenient way of entering your Sonatype credentials and they do the rest for you. You publish once to BinTray (JCenter) and it also ends up in Maven Central.

@agilestevesmith JCenter is BinTray's Maven repository much like Maven Central is Sonatype's, and you are probably already publishing to it.

The reason I asked this was because some organisations don't know about BinTray and this could only help increase your reach.