The other approach of course is to change your JAVA_HOME and use the jdk4 compiler to run your Java process. Then everything will match up and you won't need any extra configuration.
Wayne On 9/25/07, Tim Kettler <[EMAIL PROTECTED]> wrote: > Hi, > > this is because the compilation of the sources (compiler-plugin) and the > packaging (jar-plugin) is done in two steps. Even if you fork the > compiler, the jar-plugin execution isn't forked and thus runs under the > java version you invoked maven with. > > You can override the maven generated entry like this: > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-jar-plugin</artifactId> > <configuration> > <archive> > <manifestEntries> > <Build-Jdk>1.4.2</Build-Jdk> > </manifestEntries> > </archive> > </configuration> > </plugin> > > -Tim > > Guillaume Boucherie schrieb: > > My problem is not on jdk version. > > I just want to test maven. > > And when you use the fork mode in compiler the jdk's manifest entry is not > > correct. > > So I want to know how to get the correct value in manifest. > > Thanks > > > > > --------------------------------------------------------------------- > 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]
