> -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED]] > > On Sat, 2002-03-30 at 12:42, Daniel Rall wrote: > > [EMAIL PROTECTED] writes: > > > > > I'm not sure if this is something Maven should handle in general: > > > different classpath's for different jdks. An idea would > be to have that as > > > an optional <dependency> tag, e.g. > <java-version>1.2</java-version>. > > > > That seems reasonable. What do the rest of you think about that? > > I don't think this is the place to specify a jdk version. I > think this is an overall project dependency don't you?
Let's take Avalon for example. Avalon has several subprojects (that have subprojects), and we have work arounds so that it builds successfully in JDK 1.4 and Java 1.3. Avalon included Xerces so that it could parse the build files and compile the configuration object to XML mapping code. In JDK 1.4 this particular jar is not necessary. In Avalon's Excalibur Datasources project, we have some dynamic class choosing so that we can compile the JDBC connection pooling code (as we all know they changed the JDBC API in JDK 1.4). We still need to test to make sure Avalon works with prior JDKs, but some features are not available until you have the proper JDK level. One example is dynamic proxy support--which is available in JDK 1.3. Avalon has a base JDK dependency of 1.2. So we need to be able to work with all those dependancies. > > Or something like Gump specifies in the workspace where you > decide what version of Java you are dealing with. > That is what we typically do now. We use Ant to determine our environment and adapt. If we have minimum JDK dependancy that should be global. However, some libraries will only be needed with certain JDKs. Xerces/Crimson would only be needed in JDKs prior to 1.4, and there might be some libraries that only become available for use at a minimum JDK level. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
