1.6.0 is mandatory, this thread was just about the TomEE targetting JavaEE 7 (1.6 targets JavaEE 6) Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau
2013/10/29 Alex The Rocker <[email protected]>: > Hi, > > Just to make sure, this dicussion won't affect the versioning of the > official TomEE version based on current 1.6.0 snapshots, so that the next > version to be officialized is 1.6.0, right? > > After 1.6.0, I'd say, use whatever you like, but for the short term keeping > 1.6.0 would be best for my company... > > Thanks, > Alex > > > On Tue, Oct 29, 2013 at 8:50 AM, Romain Manni-Bucau > <[email protected]>wrote: > >> @Andy: basically you are right but the point is today the same guys >> are working on these projects so splitting them will create more work >> (it is already hard enough to get a release, we had been forked so >> much time because of it in companies) >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >> >> 2013/10/29 Andy <[email protected]>: >> > I'm happy to get versions aligned with each other, especially for maven >> > simplification. I'd prefer to keep our own logical version though, so >> I'd >> > opt for 2.0. >> > >> > However, I would probably rock the boat with suggesting OpenEJB and TomEE >> > could be separated into their own trunks/versions? >> > >> > I use OpenEJB in embedded and in standalone (Although I will eventually >> move >> > to TomEE in standalone). >> > >> > TomEE sits on OpenEJB, as TomEE sits on Tomcat. I think this should >> remain >> > an obvious separation as they should really be interchangeable to some >> > degree. Imagine the development benefits of easily swapping out the >> > following stable versions for snapshots ;-). >> > >> > OpenEJB 2.0 - TomEE 2.0 - Tomcat 7.0.42 >> > >> > Andy. >> > >>
