I was hoping for a more formal way than binding to a new phase, but this could work since the prebound test compile phase would detect nothing needs to be done. I need to do this in a parent pom, but I'm not sure what effect binding this would have on non-jar projects. http://docs.codehaus.org/display/MAVENUSER/Compile+and+Test+with+Different+JDK+Versions
I guess what is really missing from maven is a way to accurately modify the configuration of lifecycle bound plugins. (like to run multiple iterations of war for example) -----Original Message----- From: Rémy Sanlaville [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 04, 2006 8:59 AM To: Maven Users List Subject: Re: Can Testcompile and compile have different target/source configurations? Did you have a look to this thread ? http://www.nabble.com/-solved--product-codes-at-java-1.4%2C-test-sources-at-java-1.5-tf2233884.html#a6204244 Hope this help, Rémy 2006/10/4, Brian E. Fox <[EMAIL PROTECTED]>: > > Sorry I guess I wasn't too clear in what I want. I want to compile my > tests using java 1.5 but the rest of my sources as 1.4. Why? Because > we use TestNG and the Javadoc runner doesn't work yet and we can't > update our product to 1.5 yet. I figured if I could just build the > tests using 1.5, then we could use the java annotations and everyone would be > happy. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
