Am 05.08.2013 um 01:28 schrieb [email protected]:

> Hello all. I'm new to releasing on jenkins-ci.org so this may be a newbie 
> mistake.
> 
> I've successfully ran 'mvn release:prepare release:perform', but the plugin 
> does not appear in 
> http://repo.jenkins-ci.org/releases/org/jvnet/hudson/plugins/
> or
> http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/
> 
> However, it is showing up here:
> http://maven.jenkins-ci.org:8081/content/repositories/releases/org/owasp/dependency-check/dependency-check-jenkins-plugin/1.0.1/
> 
> Repo: https://github.com/jeremylong/dependency-check-jenkins
> Forked: https://github.com/jenkinsci/dependency-check-plugin
> Github ID: stevespringett
> 
> What am I doing wrong?
> 

You need to change your group ID in your pom from
<groupId>org.owasp.dependency-check</groupId>
to 
<groupId>org.jenkins-ci.plugins</groupId>


> Also, what is the relationship between the original repo (which I commit to), 
> the forked repo (not exactly sure why it's there), and the release that I 
> upload (built from the original repo)? 
> 
> I've made changes to the original repo, but the changes are not showing up in 
> forked repo. So I guess I need a pull request? What purpose does this 
> actually serve if the plugin I'm building and uploading is being built from 
> the original repo?
> 

Since you are the owner of the plug-in you should continue your work in the 
forked repository now (jenkinsci). Pull requests are only for other developers 
who would like to submit changes to your plug-in. So it is important that the 
plugin below jenkinsci is up to date so that others see the latest changes. 

(You can keep the original repository up to date but this is not really 
required. Actually I'm not sure if you need the original repository anymore…) 

Ulli

> Thanks in advance
> --Steve
> 
> 
> 
> 
> 
> -- 
> 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.
>  
>  

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to