Hi Kiyofumi, thanks for bearing with me. I did upgrade to Maven 3.0.5 but the problem persists. I worked around that problem and manually performed the steps release:prepare apparently omitted. After that, release:perform worked just fine and the plugin seems to be deployed<http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/stashNotifier/1.0.2/>now.
However, my Jenkins (1.500) still doesn't show the plugin nor does the plugin wiki page <https://wiki.jenkins-ci.org/display/JENKINS/StashNotifier+Plugin>show any details with the jenkins-plugin-info macro. Is there another step after the maven release I need to perform? Cheers, Georg On Friday, 1 March 2013 17:25:30 UTC+1, Kiyofumi Kondoh wrote: > > Hi Georg > > I try to use git-flow. > Worked fine for me. > > tested repository > https://github.com/kkkon/test_git-flow_maven-release-plugin > > git flow release start X.Y.Z > mvn release:prepare > mvn release:perform > git flow release finish -n X.Y.Z > > 'git flow release finish' merge to develop and master branch. > > > environment: > > S:\GITREPO\test_git-flow_maven-release-plugin>git flow version > > S:\msysgit\1.8.1.2_git-flow\bin\git-flow: line 118: init: command not > found > > 0.4.2-pre > > > > S:\GITREPO\test_git-flow_maven-release-plugin>mvn -version > > Apache Maven 3.0.4 (r1232337; 2012-01-17 17:44:56+0900) > > Maven home: S:\Maven\3.0.4 > > Java version: 1.6.0_37, vendor: Sun Microsystems Inc. > > Java home: D:\Java\x64\jdk1.6.0_37\jre > > Default locale: ja_JP, platform encoding: MS932 > > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" > > S:\GITREPO\test_git-flow_maven-release-plugin> > > > I'm sorry, distributionManagement doesn't need for your pom.xml > > distributionManagement seted by > <groupId>org.jenkins-ci</groupId> > <artifactId>jenkins</artifactId> > It is grand-parent pom. > > > Cheers, > Kiyofumi Kondoh > > > On 2013/03/01 21:41, Kiyofumi Kondoh wrote: > > Hi Georg > > > > > I'm using the git-flow branching model. Might that be the problem? > > You forgot run 'git flow release finish' at release 1.0 and 1.0.2 > > > > > Not sure I understand. Doesn't Maven first commit locally and then > push > > > that commit to the remote? If there's no local commit, I reckon there > can't > > > be anything that's pushed to a remote, right? > > > > Sorry, you are right at release:prepare. > > But it different at release:perform > > > > You read this? > > http://maven.apache.org/maven-release/maven-release-plugin/ > > You use maven 3.0.3. > > You try to upgrate to 3.0.4 or newer. > > > > > > Cheers > > Kiyofumi Konodh > > > > On 2013/02/28 15:44, Georg Gruetter wrote: > >> Hi Kiyofumi, > >> > >> On Thursday, 28 February 2013 06:14:02 UTC+1, Kiyofumi Kondoh wrote: > >>> > >>> Hi, Georg > >>> > >>> Sorry, your pom doesn't have distributionManagement at github > >>> > https://github.com/jenkinsci/stashnotifier-plugin/blob/develop/pom.xml > >>> > https://github.com/jenkinsci/stashnotifier-plugin/blob/master/pom.xml > >>> > >> Actually it does, just not on the develop or master branch but on the > >> corresponding release branch: > >> > https://github.com/jenkinsci/stashnotifier-plugin/blob/release/1.0.2/pom.xml > >> > >> I'm using the git-flow branching model. Might that be the problem? > >> > >> > >>> maven-release-plugin use scm repogitory, not your local git > repogitory. > >>> > >> Not sure I understand. Doesn't Maven first commit locally and then push > >> that commit to the remote? If there's no local commit, I reckon there > can't > >> be anything that's pushed to a remote, right? > >> > >> > >>> > >>> you should read this > >>> > >>> > http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html > > >>> > >>> and > >>> mvn -DdryRun=true release:prepare release:perform > >>> check to release phase. > >>> > >> > >> That's good advice, I'll do that before I release next. > >> > >>> > >>> > >>> There is other option etc. > >>> > >>> > http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html > >>> > >>> > http://maven.apache.org/maven-release/maven-release-plugin/perform-mojo.html > >>> > >>> Cheers > >>> Kiyofumi Kondoh > >>> > >>> On 2/28/13, Georg Gruetter <[email protected] <javascript:>> wrote: > >>>> Hi Kiyofumy, > >>>> > >>>> sorry to bother again. I followed your advice and added the > distribution > >>>> management section to my local pom, assuming that the information on > the > >>>> hosting wiki page is inaccurate, as you suggested. I did another > release > >>>> yesterday but ended up with the same problem. mvn release:prepare > >>>> release:perform does not change the artifact version of my plugin (it > >>>> remains 1.1-SNAPSHOT despite me entering 1.0.2, in this case. No > commits > >>>> and only a push to a SNAPSHOT repository. From what I can tell from > the > >>> mvn > >>>> > >>>> output, mvn tries to > >>>> issue the right git commands to commit and push changes to the pom, > but > >>> I > >>>> never see anything locally. As I said, I use maven at work for > releases > >>>> often and I have never seen such behaviour. Could it be that the > parent > >>> pom > >>>> > >>>> has problems? > >>>> > >>>> In any case I've attached the maven console output in case anybody > can > >>> give > >>>> > >>>> me a clue as to what is going wrong. > >>>> > >>>> Thanks in advance for your support and cheers, > >>>> Georg > >>>> > >>>> > >>>> On Tuesday, 26 February 2013 11:19:16 UTC+1, Kiyofumi Kondoh wrote: > >>>>> > >>>>> Hi Georg, > >>>>> > >>>>> Did you read this? > >>>>> > >>>>> > >>>>> > >>> > https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-OverridetheMavenrepositorylocation%281.395andbefore%29 > > >>> > >>>>> > >>>>> > >>>>> '1.395 and before' may be wrong. I think '1.396 or newer' > >>>>> > >>>>> Or check other plugin's pom at github.com/jenkinsci > >>>>> > >>>>> > >>>>> You set the 1.466, maven used this pom. > >>>>> > >>>>> > >>> > http://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/plugin/1.466/plugin-1.466.pom > > >>>>> > >>>>> > >>>>> plugin-1.466.pom have <distributionManagement> element > >>>>> http://maven.jenkins-ci.org:8081/content/repositories/snapshots > >>>>> > >>>>> You released to that Maven repository. > >>>>> > >>>>> You try to override the maven repository location. > >>>>> > >>>>> > >>>>> Cheers > >>>>> Kiyofumi Kondoh > >>>>> > >>>>> On 2013/02/26 17:00, Georg Gruetter wrote: > >>>>>> Hi Kiofumy, > >>>>>> > >>>>>> thanks for following up. I'm using Maven in my day to day work and > I > >>>>> don't > >>>>>> understand how this can happen. Maven even asked me for the new > >>> release > >>>>>> > >>>>>> number during the release process (as you can tell from the log I > >>>>> attached) > >>>>>> and I specified 1.0.1, not 1.1-SNAPSHOT. Also, mvn release usually > >>>>> create > >>>>>> two commits in my local repository - not here. Any advice as to > what > >>> I > >>>>>> should do differently? > >>>>>> > >>>>>> > >>>>>> On Tuesday, 26 February 2013 00:46:58 UTC+1, Kiyofumi Kondoh wrote: > >>>>>>> > >>>>>>> Hi Georg, > >>>>>>> > >>>>>>> You released snapshot. > >>>>>>>> > >>>>>>> > >>>>> > >>> > http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/stashnotifier/1.1-SNAPSHOT/stashnotifier-1.1-20130225.184741-1.hpi > > >>> > >>>>> > >>>>>>> > >>>>>>> Cheers > >>>>>>> Kiyofumi Kondoh > >>>>>>> > >>>>>>> On 2/26/13, Georg Gruetter <[email protected] <javascript:>> > wrote: > >>>>>>>> Hi Kiyofumi, > >>>>>>>> > >>>>>>>> thanks for your suggestions. I changed the artifact ID to all > >>>>> lowercase > >>>>>>>> letters. I didn't change the distribution management section of > the > >>>>>>> pom.xml > >>>>>>>> > >>>>>>>> as the documentation you pointed at is valid for a parent pom of > >>>>> version > >>>>>>>> 1.395 or earlier. I'm using version 1.466. Did I misunderstand > your > >>>>>>>> suggestions? > >>>>>>>> > >>>>>>>> I just performed another release (1.0.1) - let's see how this > goes. > >>>>> I've > >>>>>>>> attached the maven output just in case. > >>>>>>>> > >>>>>>>> Cheers, > >>>>>>>> Georg > >>>>>>>> > >>>>>>>> -- > >>>>>>>> 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] <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.
