L.S.,
Earlier this year, we cleaned out some of our POM files to remove duplicate versions. Unfortunately, we also linked our builds even closer together. This means that we're always looking at big bulky releases and we are also waiting for all the planets (aka dependency releases) to get aligned before we can start moving. I took a look at some of the latest CXF/ActiveMQ/Camel upgrades we did and most of the time, especially those that are about a fix releases (e.g. Camel 2.8.0 -> 2.8.x), don't require any code change on our side in the components and NMR project - we just update the POMs with the new version. Technically though, we don't really need a new release for the NMR and components in that scenario: the OSGi import version ranges should already allow us to update to the newer fix version. If nobody objects, I would like to investigate refactoring the features build so it can be released independently of anything else, which will allow us to just do a new ServiceMix 4 (aka features) release whenever we have new versions of Camel/Karaf/ActiveMQ/CXF available. P.S. This improvement will not help us with the upcoming 4.4.0-fuse release, that one does require everything to be released in one go. Regards, Gert Vanthienen ------------------------ FuseSource Web: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/
