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
I just committed a fix in the mojo sandbox for the shade plugin:
instead of removing the dependencies, it marks them provided.
That should make sure all versions line up if a transitive
dep brings in a 'removed' artifact.
I'm not sure where the removal of provided scoped deps takes place;
Thanks for looking into this Kenney.
Are you saying that that the problem is really in maven itself, and
version 2.0.7 in particular as it uses the shading thingy?
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
Dennis Lundberg wrote:
Thanks for looking into this Kenney.
Are you saying that that the problem is really in maven itself, and
version 2.0.7 in particular as it uses the shading thingy?
Yes, the problem is in maven itself. It uses a shaded embedder but that's okay.
2.0.7 uses
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
Hi,
I added a sleep to the test and quickly copied /tmp/surefire*tmp
to examine them.
The following 2 entries in the surefire tmp file are the cause:
Westerhof [mailto:[EMAIL PROTECTED]
Sent: Tue 8/14/2007 9:34 AM
To: Maven Developers List
Subject: Re: Plexus container 1/2 artifact problems [was: Bad links on plugin
index page]
Hi,
I added a sleep to the test and quickly copied /tmp/surefire*tmp
to examine them.
The following 2 entries
