You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Sanjay Choudhary <ch...@gmail.com> on 2006/03/11 05:27:37 UTC
mvn COMPILE FAILING!! for modules (FORK=true) AND NUMBER of .JAVA FILES ARE OVER 30
If I try to use the following setting for maven compiler plugin
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.3</source>
<target>1.3</target>
<showDeprecation>true</showDeprecation>
<showWarnings>true</showWarnings>
<fork>true</fork>
<compilerArguments>
<bootclasspath>C:/Program
Files/IBM/Rational/SDP/6.0/runtimes/base_v5/java/jre/lib/rt.jar</
bootclasspath>
</compilerArguments>
</configuration>
<inherited>true</inherited>
</plugin>
It works fine with 30 java files but after that it fails to compile.
Compiling 110 source files to
c:\rad6\security\kpusersecurityutil\target\classes
[INFO]
----------------------------------------------------------------------------
[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
:551)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
(DefaultLifecycleE
xecutor.java:472)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (
DefaultLifecycleExecutor.java:
451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecy
cleExecutor.java:303)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecut
or.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:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAcc essorImpl.invoke(
DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
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)
... 17 more
[INFO]
----------------------------------------------------------------------------
[INFO] Total time: 8 seconds
[INFO] Finished at: Fri Mar 10 18:25:17 PST 2006
[INFO] Final Memory: 6M/19M
[INFO]
----------------------------------------------------------------------------
It will be nice if someone can help us resolve it.
cheers,
Sanjay
Re: mvn COMPILE FAILING!! for modules (FORK=true) AND NUMBER of .JAVA FILES ARE OVER 30
Posted by Sanjay Choudhary <ch...@gmail.com>.
I looked at the maven and plexus compiler code and captured the cli
output from the debug details
When I ran it on the command line, it got line too long.
Debug error is below. This is the output from maven.
I have NO issues compiling my code outside of maven and with fork=false.
Issues only come up when I try to fork it with 1.3
[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
> :551)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
> (DefaultLifecycleE
> xecutor.java:472)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
> DefaultLifecycleExecutor.java:
> 451)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
> (DefaultLifecy
> cleExecutor.java:303)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments
(DefaultLifecycleExecut
> or.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:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:58)
> at sun.reflect.DelegatingMethodAcc essorImpl.invoke(
> DelegatingMethodAccessorImpl.java:60)
> at java.lang.reflect.Method.invoke(Method.java:391)
> 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)
> ... 17 more
> [INFO]
>
----------------------------------------------------------------------------
> [INFO] Total time: 8 seconds
> [INFO] Finished at: Fri Mar 10 18:25:17 PST 2006
> [INFO] Final Memory: 6M/19M
> [INFO]
>
----------------------------------------------------------------------------
Sanjay
On 3/10/06, Wayne Fay <wa...@gmail.com> wrote:
>
> You're going to have to get us more error/debug/info details before we
> can provide much assistance, I think...
>
> > [INFO] Compilation failure
> >
> > Failure executing javac, but could not parse the error:
>
> That's just not giving us anything we can work with!!
>
> Can't think of any obvious reasons why it would work for 30 but not 31
> source files, perhaps there is something in your 31st file that is
> causing the compiler to have issues? Can you try changing the set of
> 31 files (ie, first set is files 1-31, second is 32-63, third is
> 64-95) and confirm that it always blows up on the 31st file, no matter
> what 31 files you are working on?
>
> Can you compile your project using the JDK 1.3 with standard javac
> commands? If you haven't tried this, go do that right away and confirm
> no issues compiling your full 110 source files.
>
> Wayne
>
>
> On 3/10/06, Sanjay Choudhary <ch...@gmail.com> wrote:
> > If I try to use the following setting for maven compiler plugin
> >
> >
> > <plugin>
> >
> > <groupId>org.apache.maven.plugins</groupId>
> >
> > <artifactId>maven-compiler-plugin</artifactId>
> >
> > <configuration>
> >
> > <source>1.3</source>
> >
> > <target>1.3</target>
> >
> > <showDeprecation>true</showDeprecation>
> >
> > <showWarnings>true</showWarnings>
> >
> > <fork>true</fork>
> >
> > <compilerArguments>
> >
> > <bootclasspath>C:/Program
> > Files/IBM/Rational/SDP/6.0/runtimes/base_v5/java/jre/lib/rt.jar</
> > bootclasspath>
> >
> > </compilerArguments>
> >
> > </configuration>
> >
> > <inherited>true</inherited>
> >
> > </plugin>
> >
> > It works fine with 30 java files but after that it fails to compile.
> >
> > Compiling 110 source files to
> > c:\rad6\security\kpusersecurityutil\target\classes
> > [INFO]
> >
> ----------------------------------------------------------------------------
> > [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
> > :551)
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
> > (DefaultLifecycleE
> > xecutor.java:472)
> > at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (
> > DefaultLifecycleExecutor.java:
> > 451)
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
> > (DefaultLifecy
> > cleExecutor.java:303)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments
> (DefaultLifecycleExecut
> > or.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:85)
> > at sun.reflect.NativeMethodAccessorImpl.invoke(
> > NativeMethodAccessorImpl.java:58)
> > at sun.reflect.DelegatingMethodAcc essorImpl.invoke(
> > DelegatingMethodAccessorImpl.java:60)
> > at java.lang.reflect.Method.invoke(Method.java:391)
> > 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)
> > ... 17 more
> > [INFO]
> >
> ----------------------------------------------------------------------------
> > [INFO] Total time: 8 seconds
> > [INFO] Finished at: Fri Mar 10 18:25:17 PST 2006
> > [INFO] Final Memory: 6M/19M
> > [INFO]
> >
> ----------------------------------------------------------------------------
> >
> > It will be nice if someone can help us resolve it.
> >
> > cheers,
> >
> > Sanjay
> >
> >
>
Re: mvn COMPILE FAILING!! for modules (FORK=true) AND NUMBER of .JAVA FILES ARE OVER 30
Posted by Wayne Fay <wa...@gmail.com>.
You're going to have to get us more error/debug/info details before we
can provide much assistance, I think...
> [INFO] Compilation failure
>
> Failure executing javac, but could not parse the error:
That's just not giving us anything we can work with!!
Can't think of any obvious reasons why it would work for 30 but not 31
source files, perhaps there is something in your 31st file that is
causing the compiler to have issues? Can you try changing the set of
31 files (ie, first set is files 1-31, second is 32-63, third is
64-95) and confirm that it always blows up on the 31st file, no matter
what 31 files you are working on?
Can you compile your project using the JDK 1.3 with standard javac
commands? If you haven't tried this, go do that right away and confirm
no issues compiling your full 110 source files.
Wayne
On 3/10/06, Sanjay Choudhary <ch...@gmail.com> wrote:
> If I try to use the following setting for maven compiler plugin
>
>
> <plugin>
>
> <groupId>org.apache.maven.plugins</groupId>
>
> <artifactId>maven-compiler-plugin</artifactId>
>
> <configuration>
>
> <source>1.3</source>
>
> <target>1.3</target>
>
> <showDeprecation>true</showDeprecation>
>
> <showWarnings>true</showWarnings>
>
> <fork>true</fork>
>
> <compilerArguments>
>
> <bootclasspath>C:/Program
> Files/IBM/Rational/SDP/6.0/runtimes/base_v5/java/jre/lib/rt.jar</
> bootclasspath>
>
> </compilerArguments>
>
> </configuration>
>
> <inherited>true</inherited>
>
> </plugin>
>
> It works fine with 30 java files but after that it fails to compile.
>
> Compiling 110 source files to
> c:\rad6\security\kpusersecurityutil\target\classes
> [INFO]
> ----------------------------------------------------------------------------
> [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
> :551)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
> (DefaultLifecycleE
> xecutor.java:472)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (
> DefaultLifecycleExecutor.java:
> 451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
> (DefaultLifecy
> cleExecutor.java:303)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecut
> or.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:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:58)
> at sun.reflect.DelegatingMethodAcc essorImpl.invoke(
> DelegatingMethodAccessorImpl.java:60)
> at java.lang.reflect.Method.invoke(Method.java:391)
> 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)
> ... 17 more
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] Total time: 8 seconds
> [INFO] Finished at: Fri Mar 10 18:25:17 PST 2006
> [INFO] Final Memory: 6M/19M
> [INFO]
> ----------------------------------------------------------------------------
>
> It will be nice if someone can help us resolve it.
>
> cheers,
>
> Sanjay
>
>