Good point Igo, closing the mojo project in my workspace, helped.
BTW, now I go to new errors, around JSPC plugin.
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error
in the plugin manager executing goal
'org.codehaus.mojo:jspc-maven-plugin:1.4.6:compile': Mojo execution
failed.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:505)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
at
org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
at
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
at
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
at
org.maven.ide.eclipse.internal.builder.MavenBuilder$1.execute(MavenBuilder.java:123)
at
org.maven.ide.eclipse.internal.project.MavenProjectManagerImpl.execute(MavenProjectManagerImpl.java:986)
at
org.maven.ide.eclipse.internal.project.MavenProjectFacade.execute(MavenProjectFacade.java:319)
at
org.maven.ide.eclipse.internal.builder.MavenBuilder.executePostBuild(MavenBuilder.java:109)
at
org.maven.ide.eclipse.internal.builder.MavenBuilder.build(MavenBuilder.java:95)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:633)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
at
org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.apache.maven.plugin.PluginExecutionException: Mojo
execution failed.
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:601)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
... 26 more
Caused by: org.apache.maven.plugin.MojoExecutionException: JSPC Error
at org.codehaus.mojo.jspc.AbstractJspcMojo.execute(AbstractJspcMojo.java:265)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579)
... 27 more
Caused by: org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: 427 in the jsp file: /jsp/amDetailLien.jsp
Generated servlet error:
The method equals(Object) in the type String is not applicable for the
arguments (int)
at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84)
at
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:328)
at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:409)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:297)
at org.apache.jasper.JspC.processFile(JspC.java:986)
at org.apache.jasper.JspC.execute(JspC.java:1135)
at org.codehaus.mojo.jspc.AbstractJspcMojo.execute(AbstractJspcMojo.java:248)
... 28 more
2009/3/13 Henri Gomez <henri.go...@gmail.com>:
>> I think this is a different problem. Do you have
>> fr.slib.mojo:translator-maven-plugin in your workspace, by any chance? If
>> you do, can you remove/close it and try building the war again?
>
> Hehe, you're right, I've got it in my workspace
>
>> FYI, 0.9.7 resolves maven plugins from workspace during Eclipse build now.
>
> Could be a reason.
> I'll check that, thanks for the clue
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
