This would be pointless - the version in /lib is used, so depending on a
newer version of maven-project won't help the clover plugin on 2.0.
I'd say do it properly in maven-artifact/project, and put the hackish
solution in clover plugin.
- Brett
John Casey wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The real problem is that the clover plugin depends on resolution of a
bug in the 2.0 release...there's not a way around that, unless you want
to get an instance of the ArtifactFactory inside the clover mojo and
clone the project artifact by force. Otherwise, we'll have to make the
clover plugin depend on some sort of beyond-2.0 version of maven-project
(and maybe maven-artifact, depending on how we approach it).
I can roll back the changes I made to maven-artifact, and do a more
hackish solution inside MavenProject for the time being. This would keep
that copy of MavenProject compatible with 2.0, but it still means
releasing a 2.0-1 or something for maven-project. I'm not opposed to
this, but I'm not sure whether this fix warrants it or not.
What do you all think?
- -john
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
