[ http://jira.codehaus.org/browse/MCOMPILER-22?page=comments#action_84708 ] Chris Byrd commented on MCOMPILER-22: -------------------------------------
So this time I did step 1, then in step 2 I downloaded the source code from the maven-compiler-plugin-2.0.1 tag. That made things considerably easier. From what I can see on this page, it says the fix version is 2.0.2, I assume that is the version these fixes will be going into, eventually. >From that point I was able to apply Allan's patch >(maven-compiler-plugin-space-fix.patch) and install the new version of the >maven-compiler-plugin version 2.0.1 to my local repository. I went back to my original project and did another clean compile. This time I am back to the problem where there are spaces in the compiler options, so the compile fails. The error message is below. =========== [DEBUG] Command line options: [DEBUG] -d D:\Documents and Settings\xfxc104\My Documents\Dev\workspace\pw-qis\p w-qis-core\target\classes @D:\Documents and Settings\xfxc104\My Documents\Dev\wo rkspace\pw-qis\pw-qis-core\target\classes/options -classpath options; -g -nowarn -target 1.3 Compiling 1 source file to D:\Documents and Settings\xfxc104\My Documents\Dev\wo rkspace\pw-qis\pw-qis-core\target\classes [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Compilation failure Failure executing javac, but could not parse the error: javac: invalid argument: D:\Documents Usage: javac <options> <source files> =========== After all that I am back to the original question, what patches am I supposed to apply, and in what order do I apply them? Any help is greatly appreciated. > 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 > Issue Type: Bug > Reporter: Matthew Beermann > Assigned To: Carlos Sanchez > Priority: Critical > Fix For: 2.1 > > Attachments: maven-compiler-plugin-space-fix.patch, > maven-compiler-plugin.patch, MCOMPILER-22.patch, > MNG-MCCOMPILER-22-maven-compiler-plugin.patch, > MNG-MCCOMPILER-22-plexus-compilers-noformatting.patch, > MNG-MCCOMPILER-22-plexus-compilers.patch, plexus-compiler-javac-1.5.2.jar, > plexus-compiler-javac.patch > > > 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
