You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Robert Harper <ro...@oculusinfo.com> on 2006/11/17 15:04:32 UTC

Maven Java Compiler Output?

Hi all,

I'm sorry if this obvious question has been asked before.  I couldn't find
an answer in the mailing list.  

When I compile my maven project, I get the following output

...
Compiling 14 source files to C:\Research\Foundation\target\classes
[ERROR] mojo-execute : compiler:compile
Diagnosis: Compilation failure
FATAL ERROR: Error executing Maven for a project
[ERROR] project-execute : com.company:Foundation:jar:0.0.1-SNAPSHOT (
task-segment: [clean, install] )
Diagnosis: Compilation failure
FATAL ERROR: Error executing Maven for a project
org.apache.maven.BuildFailureException: Compilation failure
...

My question is how do I see what the compiler errors actually are?  Where is
the compiler output?  How can I enable it?

Thanks!
Rob


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


RE: Maven Java Compiler Output?

Posted by Robert Harper <ro...@oculusinfo.com>.
Sorry, I should have mentioned that I'm using Eclipse's maven plugin
(http://m2eclipse.codehaus.org/) to do the build.  I thought it was simply
spitting out the output from mvn.  Obviously not.

Maybe I should abandon this Eclipse integration and use the
http://maven.apache.org/guides/mini/guide-ide-eclipse.html method?

Thanks!
Rob


-----Original Message-----
From: Jeff Mutonho [mailto:ejbengine@gmail.com] 
Sent: Friday, November 17, 2006 9:36 AM
To: Maven Users List
Subject: Re: Maven Java Compiler Output?

On 11/17/06, Robert Harper <ro...@oculusinfo.com> wrote:
> Hi all,
>
> I'm sorry if this obvious question has been asked before.  I couldn't find
> an answer in the mailing list.
>
> When I compile my maven project, I get the following output
>
> ...
> Compiling 14 source files to C:\Research\Foundation\target\classes
> [ERROR] mojo-execute : compiler:compile
> Diagnosis: Compilation failure
> FATAL ERROR: Error executing Maven for a project
> [ERROR] project-execute : com.company:Foundation:jar:0.0.1-SNAPSHOT (
> task-segment: [clean, install] )
> Diagnosis: Compilation failure
> FATAL ERROR: Error executing Maven for a project
> org.apache.maven.BuildFailureException: Compilation failure
> ...
>
> My question is how do I see what the compiler errors actually are?  Where
is
> the compiler output?  How can I enable it?
>
> Thanks!
> Rob
>
>

I'm not sure I understand your question , but the compilation errors
should just appear in your output.In my example below , I took out the
commented out the spring jar file  and my build failed with the
following message:

DEBUG]  C:\telkom-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src
Compiling 392 source files to
C:\telkom-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\target\classes
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Compilation failure

C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src\za\co\p
ragmaticus\portal\controllers\ApplicationPDCRegistrationController.java:[8,3
9]
package org.springframework.web.servlet does not exist

C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src\za\co\p
ragmaticus\portal\controllers\ApplicationPDCRegistrationController.java:[10,
41]
package org.springframework.beans.factory does not exist


[INFO]
------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.BuildFailureException: Compilation failure
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife
cycleExecutor.java:555)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
(DefaultLifecycleExecutor.java:475)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifec
ycleExecutor.java:454)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail
ures(DefaultLifecycleExecutor.java:306)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa
ultLifecycleExecutor.java:273)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle
Executor.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.ja
va:505)
	at
org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:111)
	at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManage
r.java:412)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife
cycleExecutor.java:534)
	... 16 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 10 seconds
[INFO] Finished at: Tue Nov 14 11:30:05 CAT 2006
[INFO] Final Memory: 17M/508M
[INFO]
------------------------------------------------------------------------


Are you sure you're looking at all the output?What happens when you
run with the debug (mvn -X install) option?


Jeff  Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype        : ejbengine
Registered Linux user number 366042

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven Java Compiler Output?

Posted by Jeff Mutonho <ej...@gmail.com>.
On 11/17/06, Robert Harper <ro...@oculusinfo.com> wrote:
> Hi all,
>
> I'm sorry if this obvious question has been asked before.  I couldn't find
> an answer in the mailing list.
>
> When I compile my maven project, I get the following output
>
> ...
> Compiling 14 source files to C:\Research\Foundation\target\classes
> [ERROR] mojo-execute : compiler:compile
> Diagnosis: Compilation failure
> FATAL ERROR: Error executing Maven for a project
> [ERROR] project-execute : com.company:Foundation:jar:0.0.1-SNAPSHOT (
> task-segment: [clean, install] )
> Diagnosis: Compilation failure
> FATAL ERROR: Error executing Maven for a project
> org.apache.maven.BuildFailureException: Compilation failure
> ...
>
> My question is how do I see what the compiler errors actually are?  Where is
> the compiler output?  How can I enable it?
>
> Thanks!
> Rob
>
>

I'm not sure I understand your question , but the compilation errors
should just appear in your output.In my example below , I took out the
commented out the spring jar file  and my build failed with the
following message:

DEBUG]  C:\telkom-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src
Compiling 392 source files to
C:\telkom-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\target\classes
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src\za\co\pragmaticus\portal\controllers\ApplicationPDCRegistrationController.java:[8,39]
package org.springframework.web.servlet does not exist

C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src\za\co\pragmaticus\portal\controllers\ApplicationPDCRegistrationController.java:[10,41]
package org.springframework.beans.factory does not exist


[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
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10 seconds
[INFO] Finished at: Tue Nov 14 11:30:05 CAT 2006
[INFO] Final Memory: 17M/508M
[INFO] ------------------------------------------------------------------------


Are you sure you're looking at all the output?What happens when you
run with the debug (mvn -X install) option?


Jeff  Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype        : ejbengine
Registered Linux user number 366042

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org