You can use the Maven Enforcer plugin ( http://maven.apache.org/plugins/maven-enforcer-plugin/ ) to force a specifc JDK for the modules you are building yourself. But I don't think there is anything for your dependencies that you can specify.
regards, Wim 2008/3/28, david delbecq <[EMAIL PROTECTED]>: > > Hello, > > using maven2, i notice that, while there are options to specify which > java version to use when compiling, there is little information on > released jars in repo about which version there are compiled for. It's a > problem in an environment where the java version has limitation. For > example, we are working now on a tomcat using java 1.4. After upgrading > to maven and making a test deploy, we noticed that some of the > transitive dependencies are build with java 1.5. But nothing on project > makes it visible until you deploy and requires one of those jars. > > So question is, are there any recommendations on how to handle java > version in releases and in dependencies. If, in the build, i set the > "target" and "source" in compiler, will the compiler check that > dependencies respect those target (so in my case, if i point to 1.4, it > will build error because some transitive dep are java 5?) > > What are the best practice when deploying artifact about java version > used for compiling? I read somewhere that the purpose of maven release > process is to make the build "reproductible", but if that build does not > include aimed compiler, we can't assure a "rebuild" will be fully > compatible with previous build, if the java version changed... > > Thanks for giving information :) > > Regards, > David Delbecq > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
