> However, should this not have picked this up during compile time? if it was
You might need to use toolchains to handle this properly (I think, never done this). http://maven.apache.org/guides/mini/guide-using-toolchains.html Or the more hackish -bootclasspath etc. http://docs.codehaus.org/display/MAVENUSER/Compile+and+Test+with+Different+JDK+Versions > compiling on 1.5? Is there anything I can do to ensure that this scenario > doesn't happen again? Actually compile on jdk5. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
