:-)
I have used it recently for the SCM release.
So personnaly I consider it's fine :-) .
2011/4/11 Kristian Rosenvold :
> 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 depe
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 re
2011/4/10 Kristian Rosenvold :
> 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 pl
On 10/04/2011, at 8:19 PM, Kristian Rosenvold wrote:
> 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 ?
Putting one in the validate phase shouldn't
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 ;)
I've added some develo
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 gra
