ok great! IIUC, it calculates version per package, based on automatic API comparison
for release plugin, we need to calculate a version of the whole artifact. And since it's java, not OSGi, then there is no strict separation between API and internal details, I fear such approach won't give a good result: it will often find a difference in internal details for whole artifact, when the more I think about it, the more I fear there is no real (automagic) automation possible: - some changes are internal, then are not to be taken into account - some functional changes don't have any visible impact on API Regards, Hervé Le samedi 31 octobre 2015 13:45:20 Uwe Barthel a écrit : > > great: what is the bundle-maven-plugin feature you're talking about? > > The ‘baseline’[1] goal. > It based on the BND Tool[2] (by Peter Kriens), gets the previous release (!) > and check the difference between the byte code. Following semver, any new > method (new feature) requires a new minor change. Changes in Interfaces or > method signatures are incompatible and forces a major change. It is a bit > more complex but not rocket science. :-) > > [1] > http://svn.apache.org/repos/asf/felix/releases/maven-bundle-plugin-3.0.0/do > c/site/baseline-mojo.html [2] http://www.aqute.biz/Bnd/Versioning > > mit freundlichen Grüßen > Uwe Barthel > > > On 31 Oct 2015, at 13:26, Hervé BOUTEMY <[email protected]> wrote: > > > > great: what is the bundle-maven-plugin feature you're talking about? > > > > Regards, > > > > Hervé > > > > Le samedi 31 octobre 2015 13:18:35 Uwe Barthel a écrit : > >>> I'm not sure "strict semver" can be automated: functional change can't > >>> be > >>> easily detected if there is no API change > >> > >> The bundle-maven-plugin behaviour is a good base to discuss about I > >> think. > >> > >> mit freundlichen Grüßen > >> Uwe Barthel > >> > >>> On 31 Oct 2015, at 12:32, Hervé BOUTEMY <[email protected]> wrote: > >>> > >>> I'm not sure "strict semver" can be automated: functional change can't > >>> be > >>> easily detected if there is no API change > >>> > >>> semver is a great buzzword, but we should try to explain more precisely > >>> what can be automated in the plugin to try to follow the buzzword > >>> > >>> Regards, > >>> > >>> Hervé > >>> > >>> Le samedi 31 octobre 2015 12:14:09 Uwe Barthel a écrit : > >>>> Hi, > >>>> > >>>> I’m with Jason to move Maven forward to use (strict) semver as default > >>>> version strategy. > >>>> > >>>> I understand the 'cloudbee' strategy as a more exotic way. > >>>> But I'm interested in more than one strategy, configurable via plugin > >>>> or > >>>> providing by default plugin. > >>>> > >>>> mit freundlichen Grüßen > >>>> Uwe Barthel > >>> > >>> --------------------------------------------------------------------- > >>> 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] > > > > --------------------------------------------------------------------- > > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
