there is java 6 API for these things but got some surprises using them and not j7 one on some UNIx. I would really prefer to go with j7 code even in 1.7 than j6. If we manage to do a 7.x AND 1.7 vote (ie both in the same thread) I'm +1 to remove it from 1.7.x and I can do the extraction in a module on 7.x if everybody is happy with it. If we can't I'm tempted to keep it like that since it is the less hurting solution IMO to get this included.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2015-11-02 17:09 GMT-08:00 agumbrecht <agumbre...@tomitribe.com>: > Well we just need a JDK6 compatible & green build solution for 1.7.x and > TTx, > so I'm going to let you work this one out the best way you see fit. > > All PMCs should be commenting on this and working towards a solution that > is > backwards compatible and does not break the status quo for any application > that is running on a TomEE 1.7.x, it must be 100% compatible, this includes > the build. > > When we have this then it will be safe to take a snapshot, and also do a > roll for a 1.7.3 release. If these changes are not required then we should > not backport them at all. 1.7.x is currently our only production stable > branch. I'm a big -1 for any code in this branch that 'needs' Java 7+ to > work. > > Andy. > > > > > > ----- > -- > Andy Gumbrecht > > http://www.tomitribe.com > agumbre...@tomitribe.com > https://twitter.com/AndyGeeDe > > TomEE treibt Tomitribe ! | http://tomee.apache.org > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/Fwd-tomee-git-commit-JDK-6-tp4676696p4676701.html > Sent from the TomEE Dev mailing list archive at Nabble.com. >
