Releasing Plugin -

[Robert Reeves]

Hello!

Last fall, when I released a new version of Datical DB plugin, I issued the following command:

mvn release:prepare release:perform 

Last week, I had to perform the following for the plugin to be released to the update site

mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare
mvn org.apache.maven.plugins:maven-release-plugin:2.5:perform

I'm using Git 2.1.4, so I'm a bit confused as to why that is. Just a little confused as to why I needed to make a change from the "vanilla" release method. Would love to hear if there's something I should do on my end to resolve this.

https://wiki.jenkins-ci.org/display/JENKINS/DaticalDB4Jenkins

Thanks!

Robert

[Kanstantsin Shautsou]

Who said that you need execute second commands?

[Mark Waite]

If you're dependent on too old a version of the parent pom, that older parent pom may be specifying an old version of the release plugin.  There was a period where I had to release the git plugin and git client plugin using that longer syntax because the plugin was intentionally based on an older parent pom and the older parent pom was declaring an outdated version of the maven release plugin.

The git client plugin pom now includes a properties section that has several versions of plugins which it is overriding.

Refer to https://github.com/jenkinsci/git-client-plugin/blob/master/pom.xml if you're interested in that technique.

Mark Waite

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/743307e2-97de-4721-9f89-7d646bf883ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite

[Robert Reeves]

Thanks, Mark!

I wound up bumping the parent version to 1.580.1 and that fixed the problem.

Thanks again!

Robert

[Kanstantsin Shautsou]

Using latest core version you can thousand user installations from using new plugin version.

Mark provided the best variant for setting new release-plugin version.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/nXp0PfsYmog/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CABZDr3mjHwiGP6FE1VSZNmJ54X2s8mt1D%2BKLSvveuQ1RJypz%3Dg%40mail.gmail.com.

[Jesse Glick]

On Tue, Apr 7, 2015 at 6:47 PM, Mark Waite <mark.ea...@gmail.com> wrote:
> If you're dependent on too old a version of the parent pom, that older
> parent pom may be specifying an old version of the release plugin.

…which does not work with newer versions of Git, whereas the newer plugin does.

I would recommend using 2.5.1 which has some additional fixes.