|
this should work now. I've tested it using the unit test with JDK 1.4 Needs documentation for users trying to build JDK 1.4 projects. If animal sniffer is the best way through for now, then let's at least document how that would work. The following configuration works for me: <build> <pluginManagement> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> <version>2.0.2</version> <configuration> <source>1.4</source> <target>1.4</target> </configuration> </plugin> </plugins> </pluginManagement> <plugins> <plugin> <groupId>org.jvnet</groupId> <artifactId>animal-sniffer</artifactId> <version>1.2</version> <executions> <execution> <id>check-java-version</id> <phase>compile</phase> <goals> <goal>check</goal> </goals> <configuration> <signature> <groupId>org.jvnet.animal-sniffer</groupId> <artifactId>java1.4</artifactId> <version>1.0</version> </signature> </configuration> </execution> </executions> </plugin> </plugins> </build> This is for a 1.4 project, obviously. Also, I've added the http://download.java.net/maven/2 http://maven.apache.org/guides/mini/guide-building-jdk14-on-jdk15.html This mini-guide will be deployed shortly, once I've added a little more documentation for |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Investigating going back to 1.4 source compat, and simply catching NoClassDefFoundError for javax.xml.xpath.* classes, then printing a large warning to the user to encourage JDK 1.5+ usage.