Hi, it's maven magic.... afaik, the plugin searches for the previous release in maven and does the comparison. The plugin uses bnd, and compares exported packages based on semantic versioning - depending on the api change and the type of the interface (provider type or consumer type) it can easily find out what the new package version should be. It compares this with the declared version and reports an error if they don't match.
Works pretty good and easily detects if people mess up the api or forget to increase the version. Carsten 2014-10-01 10:24 GMT+02:00 Bertrand Delacretaz <[email protected]>: > Hi Carsten, > > On Wed, Oct 1, 2014 at 9:17 AM, Carsten Ziegeler <[email protected]> > wrote: > > ...I just updated trunk to our latest parent pom which enables > baselining... > > Am I correct that this works as per the "Baselining" section of > http://www.aqute.biz/Bnd/Versioning ? > > How does BND find the "old" classes that it is used to compare the APIs? > > And how does it decide which packages to verify for backwards > compatibility? > > RTFM links welcome ;-) > > -Bertrand > -- Carsten Ziegeler Adobe Research Switzerland [email protected]
