You're right about beeing easier to have multiple branches for various JRE, but from a user point of view, having the same jar working on java1.3 as minimal but having support for java 1.4 classes and maybe tiger is great.
I have the same use case for some common-code in my corporate work. I had to setup such a multi-compiler conf for maven2, but using some simple convention made it work fine (example : java1.4 classes have "java14" or "jdbc3" prefix.). I'm not sure if testing under multiple JRE with various includes/excludes is possible/simple with maven. This would require not only the rt.jar but a fully installed JRE. If you're interested in such a build process I can give help. 2007/4/19, Emmanuel Bourg <[EMAIL PROTECTED]>:
nicolas de loof a écrit : > I agrea with Jörg : having some classes depend on java 1.4 should not make > all the lib depend on java 1.4 when possible. This can be handled in maven2 > with some compiler configuration (two executions with includes/excludes), > just by having some naming convention (or deticated package) for java > 1.4classes. I'm a bit reluctant to rely on Maven to manage a mixed build correctly. We have test cases that don't run on Java 1.3 for classes that do work on Java 1.3, it's getting weird. I feel it'll be easier to manage 2 branches than fine tuning Maven to build both Java 1.3 and Java 1.4 versions. Emmanuel Bourg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
