With a public Maven project, it is important that the declared dependencies are available from a public repository, so that your project can be effectively shared, forked, and built by curious, anti-social engineers like me. Luckily, as Jesse stated, there is a relatively simple path for you to become a first-class open-source artifact publisher. Sonatype maintains a staging repository system for freely distributed projects that provides you with an almost completely self-service process to publish your artifacts to Maven Central. Just follow the steps outlined here:
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide Mark Adamcin http://adamcin.net/ "*Beware of he who would deny you access to information, for in his heart he dreams himself your master."* On Thu, Nov 14, 2013 at 7:50 PM, Jesse Glick <[email protected]> wrote: > On Thu, Nov 14, 2013 at 9:05 PM, Greg Peters <[email protected]> > wrote: > > Do I need another repository just to host this artifact? > > You say it is decoupled from the plugin for possible reuse, so it > should be published to Central via OSSRH. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
