You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Thomas Wabner (JIRA)" <ji...@codehaus.org> on 2007/01/22 11:50:17 UTC
[jira] Created: (MCOMPILER-50) using jdk1.5 with maven2 and try to
compile with jdk1.3 fails
using jdk1.5 with maven2 and try to compile with jdk1.3 fails
-------------------------------------------------------------
Key: MCOMPILER-50
URL: http://jira.codehaus.org/browse/MCOMPILER-50
Project: Maven 2.x Compiler Plugin
Issue Type: Bug
Environment: win XP, jdk 1.5.1_10, jdk 1.3.1_18, maven 2.0.4
Reporter: Thomas Wabner
Priority: Critical
We try to compile a project with following setting for the compiler plugin:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.3</source>
<target>1.3</target>
<executable>${env.JAVA_DEV}\bin\javac</executable>
<compilerVersion>1.3</compilerVersion>
<fork>true</fork>
<verbose>true</verbose>
</configuration>
</plugin>
the JAVA_DEV environment variable points to the jdk_1.3.1_18 directory (no spaces in the path like C:\Programme\jdk1.3.1_18.
We got following exception:
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
Failure executing javac, but could not parse the error:
[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.BuildFailureException: Compilation failure
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure
at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:505)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:111)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
... 16 more
This is not a problem with a too long path (as reported by other bugs).
We don't know how to set a logging environment to get a more detail stacktrace or problem report.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCOMPILER-50) using jdk1.5 with maven2 and try to
compile with jdk1.3 fails
Posted by "Thomas Wabner (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCOMPILER-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Wabner closed MCOMPILER-50.
----------------------------------
Resolution: Duplicate
Duplciate to MCOMPILER-22
You have to use the compiler snapshot
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.1-SNAPSHOT</version>
...
with the snapshot repository:
<pluginRepository>
<id>Apache Snapshots</id>
<url>http://people.apache.org/maven-snapshot-repository/</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
<releases>
<enabled>false</enabled>
</releases>
</pluginRepository>
> using jdk1.5 with maven2 and try to compile with jdk1.3 fails
> -------------------------------------------------------------
>
> Key: MCOMPILER-50
> URL: http://jira.codehaus.org/browse/MCOMPILER-50
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
> Environment: win XP, jdk 1.5.1_10, jdk 1.3.1_18, maven 2.0.4
> Reporter: Thomas Wabner
> Priority: Critical
>
> We try to compile a project with following setting for the compiler plugin:
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-compiler-plugin</artifactId>
> <configuration>
> <source>1.3</source>
> <target>1.3</target>
> <executable>${env.JAVA_DEV}\bin\javac</executable>
> <compilerVersion>1.3</compilerVersion>
> <fork>true</fork>
> <verbose>true</verbose>
> </configuration>
> </plugin>
> the JAVA_DEV environment variable points to the jdk_1.3.1_18 directory (no spaces in the path like C:\Programme\jdk1.3.1_18.
> We got following exception:
> [ERROR] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Compilation failure
> Failure executing javac, but could not parse the error:
> [INFO] ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.BuildFailureException: Compilation failure
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure
> at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:505)
> at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:111)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> ... 16 more
> This is not a problem with a too long path (as reported by other bugs).
> We don't know how to set a logging environment to get a more detail stacktrace or problem report.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira