Hey, While in theory a diff release would be possible it's quite hard to do in reality. Someone would need to add a maven plugin either checking the SCM or the binaries for differences. BUT this could be quite a challange since there are some parts of a binary changing for each release without any real changes. So a simply md5 calc won't do for .jar files... On the other hand some scm diffs and pom parsings could do some wonders... not sure...
On the other hand it would be (of course) possible to generate a list or diff release manually but I think this is WAYs to error prone to give it any real chance. So if you (or someone else) would like to give it a shot I think we'll be very pleased adding an additional diff based release to our release cycles; otherwise I'm afraid such a process would be simply too risky :-( Kind regards, Andreas On Mon, Sep 10, 2012 at 10:05 AM, lbu <[email protected]> wrote: > Hi Jean-Baptiste, > thank you for the quick answer. > > Do you think it would be possible to ship in any karaf release what files > have been changed? This would simplify the upgrade process for karaf > installations on which I "deploy on". > > e.g: > > * Karaf 2.2.9: > - etc/shell.init.script > - lib/karaf.jar > * Karaf 2.2.8: > - etc/startup.properties > - lib/karaf.jar > > > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/karaf-in-production-tp4025971p4025973.html > Sent from the Karaf - User mailing list archive at Nabble.com.
