The best way is to get the artifact pushed to Central, e.g. via oss.sonatype.org
Failing that you can just deploy directly to Jenkins' repo using your existing credentials, but ensure that you pick a sensible groupId so that when/if we ever get Jenkins' repo syncing to Central you don't screw everything up for everyone ;-) On 24 April 2013 13:52, Mike Bockus <[email protected]> wrote: > I'm developing a plug-in for Jenkins that has a dependency on a library > that is not in the Jenkins Maven repository. For now I've just added the > file manually to my local repository. How do I go about adding a new > artifact to the Jenkins Maven repository? > > -- > 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.
