We have the same error message... which seems a logical error since
we're building plugins that use those plugins during the build.
[EMAIL PROTECTED] wrote:
Hi
When I try to build the plugins, I get the following:
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] The projects in the reactor contain a cyclic reference: Edge between 'Ver
tex{label='org.apache.maven.plugins:maven-jxr-plugin'}' and 'Vertex{label='org.a
pache.maven.plugins:maven-javadoc-plugin'}' introduces to cycle in the graph org
.apache.maven.plugins:maven-javadoc-plugin --> org.apache.maven.plugins:maven-jx
r-plugin --> org.apache.maven.plugins:maven-javadoc-plugin
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
Hermod
-----Original Message-----
From: Trygve Laugstøl [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 13, 2006 11:55 AM
To: Maven Developers List
Subject: Re: Plugins can't be built!
Dennis Lundberg wrote:
Brett Porter wrote:
This shouldn't have broken - needs investigation.
A while back, we agreed to add a feature to 2.0.5 (the implementation
attribute).
The plugin plugin was updated to use the new tools and such. However,
it also has a prereq of maven 2.0.5, so maven 2.0.4 and below which
give this error should use the previous version of the plugin.
Are you saying that I need to use Maven 2.0.5 SNAPSHOT to build all
plugins from now on?
I prefer to stay on the released version of Maven as long as possible,
to make sure that I have the same environment as most users do. But I
see the chicken-and-egg problem here.
If the plugin plugin has a prereq on Maven 2.0.5 shouldn't it give some > sort of
understandable error message to the user if he/she tries to run > it with Maven
2.0.4, instead of just a stack trace?
What about using profiles for this?
I wonder if we should add the building of the plugins using the
different releases of Maven to make sure that they keep the backwards
compatability (Sorry, I do not have time to fix it :( ).
--
Trygve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
This email with attachments is solely for the use of the individual or
entity to whom it is addressed. Please also be aware that the DnB NOR Group
cannot accept any payment orders or other legally binding correspondence with
customers as a part of an email.
This email message has been virus checked by the anti virus programs used
in the DnB NOR Group.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
