I do mainly agree on the result and the consequences to have 2 different versions in the same tree. The best would have been to have OpenEJB as a separate subproject with its own lifecycle and versioning and to use it in TomEE like any other dep (openjpa, cxf to name a few).
Because usually we update in both sides OpenEJB and TomEE, we decided to stick with one tree only containing TomEE, the Maven plugin, OpenEJB, etc with the consequences you mentioned Andy. It definitely has some benefits but yes the drawbacks are heavy as well. That said, I'm wondering if OpenEJB and TomEE at least have a different lifecycle. If not, then at least they should have the same version in the same tree. The problem I can see. - bumping TomEE version to 4.x for example is quite "dangerous". TomEE by itself is pretty young even if most of the codebase is old. Switching from 1.x to 4.x without anything in the middle is doable but hard to argue considering we only released less than 10 TomEE versions. - using tomcat versioning, I'm -1 for this. Same drawbacks as previous and no real benefits. We could use the Java EE web profile versions or Java EE versions, like TomEE 6.x for Java EE 6 Web Profile, TomEE 7.x for Java EE 7 Web Profile, etc - downgrading OpenEJB version is even more complicated in my opinion and as we kept the same groupId / artifactId, it can be a big Maven hell. What's "the less worst" solution we could use? Considering OpenEJB and TomEE have their own lifecycle, I'd then keep the versions and split the source tree and the releases Considering OpenEJB and TomEE have different lifecycle, I'd go with the same versioning, probably using OpenEJB versions or better EE version. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Sat, Jan 3, 2015 at 10:46 AM, Andy Gumbrecht <[email protected]> wrote: > I know this is a flamed subject, but here goes. > > A major problem on release is the double barrelled version of OpenEJB 4.x > and TomEE 1.x and 5.x / 2.x. This makes using release tools virtually > impossible and the whole process has to have manual interaction. We shoot > ourselves in the foot with this one every time. > > I know project separation is a no go area for some, so another option > would be to get versions aligned. Also a huge point of contention. The > issue is the version to use? > > So this is just to throw a rabbit into the lions den - How about aligning > with the underlying Tomcat major version, something like TomEE/OpenEJB 7.x > for Tomcat 7.x and 8.x for Tomcat 8? > > Andy. > > -- > Andy Gumbrecht > https://twitter.com/AndyGeeDe > http://www.tomitribe.com > >
