sebb-2-2 wrote > > >> Since it is targeted at new projects or at least very active ones, the >> deployment will require at least Java 1.6. > > Now if 1.6 is absolutely required to support certain new features, > that is a different matter. > > I should have said that 'not useful' too. I believe it is not useful to incur the cost of maintaining knowledge about 1.5 and 1.6 differences in this case. I also think that if you want to use "new" stuff, it is better to avoid putting it on top of unsupported ones (1.5 is eol afaik); instead of adapting some code to Jexl3, someone would be doing a better job at migrating towards Java 6. Henrib
-- View this message in context: http://apache-commons.680414.n4.nabble.com/Re-jira-Created-JEXL-123-Redesign-API-for-stability-tp4157779p4157896.html Sent from the Commons - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
