It's really not that difficult to upgrade and the improvements in Karaf 3.x are certainly worth it. I think the biggest changes end up being in integration tests, but the cellar and karaf integrarion tests are a great way to see what the upgraded tests look like.
I'd highly recommend upgrading and think the risk isn't as great as it seems. Ryan On Nov 24, 2014 5:35 PM, "Achim Nierbeck" <[email protected]> wrote: > If you look at the current progress with Karaf 3.0.x and 4.0 which is > available as first Milestone, I think going into the 2.4 direction is > rather a dead end. > > regards, Achim > > 2014-11-24 23:06 GMT+01:00 thully <[email protected]>: > >> What would I really gain by using 3.0.2 over 2.4.0? I'm inclined to go >> with >> the less risky choice - which would seem to be 2.4.0.. >> >> I've attached the pom.xml from our assembly - it uses some variables >> stored >> in a parent pom elsewhere, but those are just for versions. This is the >> same >> one we used for 2.3.5 - for 2.4.0, we simply changed the parent pom >> version >> number... >> >> pom.xml <http://karaf.922171.n3.nabble.com/file/n4036644/pom.xml> >> >> >> >> -- >> View this message in context: >> http://karaf.922171.n3.nabble.com/Upgrading-Karaf-2-3-5-to-2-4-0-or-3-0-2-tp4036578p4036644.html >> Sent from the Karaf - User mailing list archive at Nabble.com. >> > > > > -- > > Apache Member > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & > Project Lead > blog <http://notizblog.nierbeck.de/> > Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> > > Software Architect / Project Manager / Scrum Master > >
