Closed staenker closed 10 years ago
Hi,
I have had an anonymous benefactor that has kindly pushed c10n to central already)) http://mvnrepository.com/artifact/c10n/c10n-core/1.1
The thing is that I didn't mean that to happen, so it was pushed with my "experimental" package name "c10n" without any proper root like "io.github.rodionmoissev.c10n". I don't know how it got onto central with the current package name, as I believe package naming rules are quite strict, and would typically require to own the "c10n" domain.
So the current state is that c10n is already on central but not under my control. I can re-apply to maven central myself, but that would probably require to change package names.
Hi, there is only the core module hosted on central. c10n-ext-guice and c10n-tools are not available. If that requires a package name change I'm happy with it. c10n groupId is indeed a bit experimental :). I never had a problem with changing groupId and artefactId when upgrading to a new version since I'd have the pom file already open. The old packages can still be hosted for backwards compatibility. As stated in here: https://docs.sonatype.org/display/Repository/Choosing+your+Coordinates you just need to own the project, no need to own the domain. Thanks for your efforts, Richard
Thanks for the suggestions. I will get working on it.
I already have an account with Sonatype, so will use that. The new libraries will be packaged under com.github.rodionmoiseev.c10n
namespace.
Awesome! Thank you very much, Richard
Have pushed all updates, and released to central (might take some time to sync though). Please let me know if it has worked for you, I will then update the Wikis.
The new artifact descriptor is
<groupId>com.github.rodionmoiseev.c10n</groupId>
<artifactId>c10n-core</artifactId>
<version>1.2</version>
Other artifacts: c10n-ext-guice
and c10n-tools
are also on maven now.
Cheers!
Absolutely awesome - you even refactored the package names!!! Thanks a million, Richard
Cheers!
Adding custom repositories to your pom file is possible and nice for open source projects. But it does not scale in the context of forced company repo proxies like nexus. So it would be nice to have the artefacts available on central. The process itself just a bit of work and not too complex. I already went through this so tell me if you need a helping hand on this.