Brett Porter wrote:
On 16/08/2007, at 8:42 AM, Kenney Westerhof wrote:
Or is there something that we can do in doxia to fix it? Should we
update to a version of plexus-velocity that uses the latest
plexus-container-default?
That would work; or add a depMgt section specifying p-c-d and p-c-a as
scope provided
in the doxia poms. Possibly just an exclude on the plexus-velocity dep
for p-c-d/p-c-a,
but we need to come up with a more general solution.
Yeah, I think addressing this in doxia with exclusions is the right way
to go. I might also look at special casing this in surefire if it's
appropriate.
I tried adding exclusions in the plexus-velocity dependency, but p-c-a
is being dragged in from other places as well. I haven't spent much time
analyzing dependency graphs in Maven, so I'm going to leave this as it
is for now. The problem only occurs when I use surefire-2.3.1-SNAPSHOT.
First having one archive,
then 2, then one again, that's asking for problems ;)
+1 :)
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
