I saw the same problem when I was testing the [configuration] release with a .mavenrc set to force maven itself to run under 1.3. (which, btw is another workaround for the jdk spec in manifest problem), but I did not mention it since the build with maven.compile.executable pointing to jdk 1.3 worked (I guess maven does not fork the test class compiles). From my perspective, test class dependencies on later jdks are not show-stoppers. I think we had the same problem in [lang] in 2.0 and concluded that it was OK to release with tests depending on a later jdk than sources, since what is important from a usage standpoint is that the jar work with the targed jdk.
+1, though for getting hsqldb released with 1.3 compatibility. On 12/3/05, Oliver Heger <[EMAIL PROTECTED]> wrote: > Emmanuel Bourg wrote: > > > Oliver Heger wrote: > > > >> As I found out the cause for that is the hsqldb.jar distributed through > >> ibiblio, which was built for JDK 1.4 and later. Indeed I was able to > >> recompile hsqldb on JDK 1.3 and then the problem disappears. > >> Unfortunately there does not seem to be a JDK 1.3 compatible version of > >> a hsqldb.jar on the ibiblio maven reository (at least I did not find > >> one). So this makes the build process on a JDK 1.3 very hard because the > >> correct hsqldb.jar cannot be automatically downloaded. > > > > > > Maybe we could request the JDK 1.3 version of hsql to be uploaded in > > the repository at Ibiblio ? As hsqldb-x.y.z-jdk13.jar for example ? > > > > Emmanuel Bourg > > > +1, I think this would be the best solution. How would we do that? > > Oliver > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
