Thanks for the info. I asked the owner of the library to push the artifact to sonatype. I wasn't sure how long that was going to take, so I also added the artifact directly to the Jenkins repo using my existing credentails. I'm not sure I uploaded the artifact correctly though. I uploaded it to the "bogus" repository, which I'm now thinking was probably the wrong choice. Should I have targeted the snapshots or releases repository?
The current artifact is published here: bogus:com/veracode/api/clients/veracode-client/13.1.1.1/veracode-client-13.1.1.1.jar<http://repo.jenkins-ci.org/simple/bogus/com/veracode/api/clients/veracode-client/13.1.1.1> Let me know if you need anymore info. On Wednesday, April 24, 2013 7:59:56 AM UTC-5, Stephen Connolly wrote: > > 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] <javascript:>>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] <javascript:>. >> 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.
