aspectj problem

4 views
Skip to first unread message

yottzumm

unread,
Mar 3, 2008, 9:15:08 PM3/3/08
to Q for Eclipse users list
I have a problem working with aspectj and Q4Eclipse. When I run clean
as a goal, I get the following:

Errors during Maven execution
Failed to construct build plan for: gov.llnl.nif:vssar:war:1.0.0.7-
SNAPSHOT ( task-segment: [clean] ). Reason:

No lifecycle phase binding can be found for goal: compile,
specified as a part of the execution: default
in plugin: org.codehaus.mojo:aspectj-maven-plugin

This plugin could not be resolved, so use of the default lifecycle
phase binding
(if there is one) is impossible.

Please ensure that the plugin: org.codehaus.mojo:aspectj-maven-plugin
can be resolved by Maven,
then try re-running this build with the -U option
(to ensure that all plugin metadata is refreshed).


I don't know how to run with -U inside eclipse.

The build outside of eclipse works fine.

Carlos Sanchez

unread,
Mar 3, 2008, 11:31:31 PM3/3/08
to q4e-...@googlegroups.com
we'd need you to chcek the instructions in
http://code.google.com/p/q4e/wiki/ReportingBugs
I think it may be a Maven bug, not Q4E's

--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride

yottzumm

unread,
Mar 4, 2008, 12:46:32 PM3/4/08
to Q for Eclipse users list
Hmm. Maven 2.1 doesn't build. Can you provide a Maven installation
zip that works?

Carlos Sanchez

unread,
Mar 4, 2008, 12:54:45 PM3/4/08
to q4e-...@googlegroups.com
wdym by doesnt work? the one in
http://q4e.googlecode.com/files/apache-maven-2.1.0-620417-bin.zip ?


On Tue, Mar 4, 2008 at 9:46 AM, yottzumm <yott...@gmail.com> wrote:
>
> Hmm. Maven 2.1 doesn't build. Can you provide a Maven installation
> zip that works?
>
>
> >
>

--

yottzumm

unread,
Mar 4, 2008, 1:32:44 PM3/4/08
to Q for Eclipse users list

Sorry, I thought you were pointing me at the version of the plugin.
So you're saying the zip is the maven2.1 installation. Okay.
I tried downloading from svn, and the svn doesn't work (searched for
Maven 2.1 on the web).

John

On Mar 4, 9:54 am, "Carlos Sanchez" <car...@apache.org> wrote:
> wdym by doesnt work? the one inhttp://q4e.googlecode.com/files/apache-maven-2.1.0-620417-bin.zip?
>

yottzumm

unread,
Mar 4, 2008, 1:52:34 PM3/4/08
to Q for Eclipse users list
Yes, it appears to be a maven bug. Here is the stack trace from the
mvn clean command

java.lang.IllegalStateException: The PluginDescriptor for the plugin
org.codehaus.mojo:aspectj-maven-plugin was not found. Should have been
in realm: ClassRealm
[/plugins/org.codehaus.mojo:aspectj-maven-plugin:1.0-
beta-4-20080124.150437-6@48, parent: null]
at
org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:
393)
at
org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:
232)
at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:
181)
at
org.apache.maven.plugin.loader.DefaultPluginLoader.loadPlugin(DefaultPluginLoader.java:
198)
at
org.apache.maven.lifecycle.binding.DefaultLifecycleBindingManager.getProjectCustomBindings(DefaultLifecycleBindingManager.java:
208)
at
org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan(DefaultBuildPlanner.java:
55)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getLifecycleBindings(DefaultLifecycleExecutor.java:
422)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:
303)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:
147)
at
org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:
219)
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_aroundBody4(MavenEmbedder.java:
816)
at
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody5$advice(MavenEmbedder.java:
304)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:178)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
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:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:
289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:
229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:
408)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
351)-

Carlos Sanchez

unread,
Mar 4, 2008, 4:36:14 PM3/4/08
to q4e-...@googlegroups.com
Then you should report it in http://jira.codehaus.org/browse/MNG with
all the information possible so somebody can take a look at it

--

Abel Muiño

unread,
Mar 5, 2008, 3:41:07 AM3/5/08
to q4e-...@googlegroups.com
Please also reply to this thread with the URL of the issue, for reference.
--
Abel Muiño - http://ramblingabout.wordpress.com/
Reply all
Reply to author
Forward
0 new messages