Robert, Before the introduction of the plugable policy the release plugin would transform a version number like 1.8.0-1.7.1.0-alpha-1 to 1.8.0-1.7.1.0-alpha-2-SNAPSHOT whereas since sometime after m-r-p 2.2 it now does 1.8.0-1.7.1.0-alpha-1 to 1.8.0-2.7.1.0-alpha-1-SNAPSHOT which is a major pain in the posterior for use when we have the CJOC 1.x release line of embedded elasticsearch providers... e.g. we had
1.6.0-1.3.1.0 - the first release in CJOC 1.6 that is compatible with the CJOC-es-provider api 1.6.0 and bundles ES 1.3.1 1.7.0-1.3.1.0 - the first release in CJOC 1.7 that is compatible with the CJOC-es-provider api 1.7.0 and bundles ES 1.3.1 1.7.1-1.3.1.0 - a release in CJOC 1.7 that requires at least CJOC-es-provider api 1.7.1 and bundles ES 1.3.1 1.7.1-1.7.1.0 - a release in CJOC 1.7 that requires at least CJOC-es-provider api 1.7.1 and bundles ES 1.7.1 1.7.2-1.3.1.0 - a release in CJOC 1.7 that requires at least CJOC-es-provider api 1.7.2 and bundles ES 1.3.1 1.7.2-1.7.1.0 - a release in CJOC 1.7 that requires at least CJOC-es-provider api 1.7.2 and bundles ES 1.7.1 1.7.2-1.7.1.1 - a bug fix release in CJOC 1.7 that requires at least CJOS-es-provider api 1.7.2 and bundles ES 1.7.1 1.8.0-1.7.1.0 - a release in CJOC 1.8 that requires at least CJOC-es-provider api 1.8.0 and bundles ES 1.7.1 in other words this *integration* module has to track two version numbers and allow for repeated builds when the integration code has bugs [version number of es-provider-api]-[version number of elasticsearch].[build number] -Stephen On 30 October 2015 at 15:35, Robert Scholte <[email protected]> wrote: > Stephen, you are saying that the implementation of the default version policy > has changed? That would be a bug. CloudBees implementation looks > natural,although Aether is aware of more classifiers , not just alpha and > beta. > > Robert > > Verzonden vanaf Samsung Mobile. > > <div>-------- Oorspronkelijk bericht --------</div><div>Van: Stephen Connolly > <[email protected]> </div><div>Datum:30-10-2015 05:16 > (GMT-08:00) </div><div>Aan: Maven Developers List <[email protected]> > </div><div>Onderwerp: Maven Release Version Policy </div><div> > </div>Hey, so... > > Do we want to accept this implementation I knocked together: > https://github.com/CloudBees-community/cloudbees-maven-release-version-policy > > If not I'm fine leaving it where it is... but I can get it donated to > the ASF if there is interest > > -Stephen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
