There is also the case we had in fileinstall very recently, where the behavior was changed in an incompatible way while there has been no API changes per se.
On Thu, May 6, 2010 at 02:22, David Jencks <[email protected]> wrote: > I've been trying to figure out some package versions for some geronimo code > today and think that, given an existing bundle and its next version, it's > pretty much beyond human capabilities to correctly determine the package > versions for the new bundle. Certainly I don't think anyone trying to tie > up the loose ends for a release is going to be able to do it correctly. > > Are there any tools available to help with this? > > I don't think that anyone can expect any correct package versions in > bundles until this is well supported by tooling. > > Ideally I'd like the maven-bundle-plugin to have a goal to determine the > package versions by analyzing the code differences between the current code > and the previous released version of a bundle, and for the normal operation > of the plugin to compare these correct versions with explicitly configured > versions to make it obvious when you have unintentionally changed > compatibility. > > thanks > david jencks > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
