i had the same thought but that's not possible (not logical, we'll lost users...)
we can split tomee and openejb in 2 projects but then the version will still be in tomee subproject. An alternative is a small groovy script in mvn to set this var (if project.version startswith 1 -> 4 else nothing) That said using sed on both versions helps releasing ;) *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/5/24 AndyG <[email protected]> > Ouch, see what you mean. But this still seems wrong somehow to have this > hard > coded? > > It makes versioning a two step process outside the scope of current maven > modules. I am still playing with the push snapshot to local repo and a new > version. > > Maybe aligning the OpenEJB version with TomEE is worth thinking about? > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Fwd-svn-commit-r1485786-tomee-tomee-trunk-pom-xml-tp4663194p4663197.html > Sent from the OpenEJB Dev mailing list archive at Nabble.com. >
