The maven3 requirement was requried because surefire now uses a previous version of itself to build itself (for isolation). Maven 2.2.1 does not understand that a dependency on a different version of the same artifact is in fact not a cycle.

I asked some time ago on the ml if the currently released site plugin was "good enough" for a plugin release and the silence was resouding, which I interpret as "no". I did not try it out, so I have no specific gripes ;)

Kristian




Den 11.04.2011 10:09, skrev Olivier Lamy:
2011/4/10 Kristian Rosenvold<[email protected]>:
You need to build with maven3, we fixed the build by changing to m3.
Unfortunately we still need to deploy site (for releases) with 2.2.1.
Maybe there's some way to add such an enforcer rule ? Personally I've
just put on the blindfold, hoping for a 3.x site plugin release ;)
Ohhh !!! :-)
what is breaking ??

I've added some developer docs in the apt file
"developingSurefire.apt" (which is currently not
linked into the site), and I should probably add some notes on this
situation there too.

Kristian



sø., 10.04.2011 kl. 11.44 +0200, skrev Stefan Birkner:
Hello,
I checked out surefire's trunk, but I'm not able to build it. I get

The projects in the reactor contain a cyclic reference: Edge between
'Vertex{label='org.apache.maven.surefire:surefire-api'}' and
'Vertex{label='org.apache.maven.surefire:surefire-shadefire'}'
introduces to cycle in the graph
org.apache.maven.surefire:surefire-shadefire -->
org.apache.maven.surefire:surefire-api -->
org.apache.maven.surefire:surefire-shadefire

On March 13th there was the same problem on hudson, but I didn't find
out how it was solved.
(http://maven.40175.n5.nabble.com/Build-failed-in-Hudson-surefire-java-5x-windows-261-td3555445.html)
 Does anybody know?

Best Regards,
stefan


---------------------------------------------------------------------
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]






---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to