Here's an altogether different approach, but if your developers' goal is
to control what version of byte code is created, have them utilize the
-source and -target attributes of the <javac> task. I have my
developers do that and it allows me to use the latest JDK for all builds
(400+ development streams) while they're able to build components and
applications executing in JVMs from 1.4 --> 1.6
Its been awhile...but if memory serves, I had a situation at work where
we were using a newer JDK and compiling for an older VM. Some method that
existed in the new JDK didn't exist in the old - and targeting for the
older VM didn't complain about the method not being there. Honestly, I
cannot rememebr the exact scenario - its been over a year.
However, just be aware in case that happens to you :)
---
Scot P. Floess
RHCT (Certificate Number 605010084735240)
Chief Architect FlossWare http://sourceforge.net/projects/flossware
http://flossware.sourceforge.net
https://github.com/organizations/FlossWare
Chief Architect JPlate http://sourceforge.net/projects/jplate
Chief Architect JavaPIM http://sourceforge.net/projects/javapim
Chief Architect Keros http://sourceforge.net/projects/keros
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@ant.apache.org
For additional commands, e-mail: user-h...@ant.apache.org
