You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2006/03/23 03:52:12 UTC
[jira] Updated: (MCOMPILER-22) Compilation fails: "The command line
is too long."
[ http://jira.codehaus.org/browse/MCOMPILER-22?page=all ]
Carlos Sanchez updated MCOMPILER-22:
------------------------------------
Fix Version: (was: 2.0.1)
2.0.2
> Compilation fails: "The command line is too long."
> --------------------------------------------------
>
> Key: MCOMPILER-22
> URL: http://jira.codehaus.org/browse/MCOMPILER-22
> Project: Maven 2.x Compiler Plugin
> Type: Bug
> Reporter: Matthew Beermann
> Assignee: Jason van Zyl
> Priority: Critical
> Fix For: 2.0.2
>
>
> For one of my project, compilation fails with the message "The command line is too long". As far as I can tell, it's listing each and every source file, one at a time, in the -sourcepath attribute. (?!?) Here's the log:
> [DEBUG] Source roots:
> [DEBUG] C:\continuum-1.0.2\apps\continuum\working-directory\26\src
> [DEBUG] Command line options:
> [DEBUG] -d C:\continuum-1.0.2\apps\continuum\working-directory\26\target\classes -classpath <DEPENDENCIES SNIPPED HERE> -sourcepath <ENORMOUSLY LONG LIST OF SOURCE FILES HERE> -g -nowarn -target 1.4 -source 1.4
> Compiling 167 source files to C:\continuum-1.0.2\apps\continuum\working-directory\26\target\classes
> [INFO] ----------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] ----------------------------------------------------------------------------
> [INFO] Compilation failure
> Failure executing javac, but could not parse the error:
> The command line is too long.
> [INFO] ----------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.BuildFailureException: Compilation failure
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:551)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139)
> 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:249)
> 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:429)
> at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:110)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:432)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:530)
> ... 16 more
--
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