This is what I understood as well. (about m-r-p 2.5.1) Le 11 oct. 2014 10:07, "Stephen Connolly" <[email protected]> a écrit :
> IIUC the release plugin version 2.5.1 has the fix for non-root pom > releases (but I *might* be wrong about that) > > On Friday, October 10, 2014, Ulli Hafner <[email protected]> wrote: > >> >> Am 10.10.2014 um 21:19 schrieb Jesse Glick <[email protected]>: >> >> > On Fri, Oct 10, 2014 at 3:04 PM, Ulli Hafner <[email protected]> >> wrote: >> >>> which workaround are you referring to? >> >> >> >> specifying version 2.5 explicitly on the command line >> > >> > Ah, well that is just using a new plugin version, which you would also >> > get by using a newer parent POM. >> > >> >> The release plugin does not work if you have … >> > >> > Did you mean that one or all of these are regressions compared to an >> > earlier version of maven-release-plugin? Are they filed as such? >> >> All 3 types. The bug has been filed, yes. Seems that it has been fixed >> now in maven-scm-provider-gitexe 1.9.2. As new workaround one should use >> now: >> >> <plugin> >> <groupId>org.apache.maven.plugins</groupId> >> <artifactId>maven-release-plugin</artifactId> >> <version>2.5</version> >> <dependencies> >> <dependency> >> <groupId>org.apache.maven.scm</groupId> >> <artifactId>maven-scm-provider-gitexe</artifactId> >> <version>1.9.2</version> >> </dependency> >> </dependencies> >> </plugin> >> >> > >> >> The problem reported here is of type c) >> > >> > Right, see that now. The plugin sources really ought to be moved to >> > top level for consistency with other plugins. >> > >> >> one module (a library) is changed only about once a year, the plugin >> itself is released several times a year. So I want to be able to release >> only the module that actually has been changed. >> > >> > I guess you could just keep the library in its own repository. Or an >> > unrelated branch of the same repository (git checkout --orphan). >> > Either would have beneficial side effects beyond maven-release-plugin, >> > such as ensuring that the commits between two successive release tags >> > actually correspond to changes in that component, and making >> > plugin-compat-tester work without my having to fix it for this plugin. >> > :-) >> > >> > -- >> > 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/d/optout. >> >> > > -- > Sent from my phone > > -- > 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/d/optout. > -- 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/d/optout.
