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
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 provi
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 plexus-cont
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
p
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;
probabl
enney 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 entri
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:
surefire45886tmp:classPathUrl.30=/home/forge/.m2/repository/org/codehaus/plexus/plexus-component-api/1.0-alpha-20/plexus-component-api-1.0-alpha-
On 12/08/2007, at 6:56 PM, Jason van Zyl wrote:
Looks like a bad plexus snapshot on my end, since it's fine on the
zone too.
testRender
(org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest)
Time elapsed: 0.275 sec <<< ERROR!
java.lang.NoSuchMethodError:
org.codehaus.plexus.c
On 12 Aug 07, at 5:11 AM 12 Aug 07, Brett Porter wrote:
On 12/08/2007, at 5:07 AM, Dennis Lundberg wrote:
Brett Porter wrote:
Using the latest of everything doesn't correct the problem -
seems like there's still a bug.
OK, we need to track this down ASAP.
Cool, thanks for taking care o
On 12/08/2007, at 5:07 AM, Dennis Lundberg wrote:
Brett Porter wrote:
Using the latest of everything doesn't correct the problem - seems
like there's still a bug.
OK, we need to track this down ASAP.
Cool, thanks for taking care of it.
I also had to skip the tests in the doxia-sitetool
Dennis Lundberg wrote:
Brett Porter wrote:
Using the latest of everything doesn't correct the problem - seems
like there's still a bug.
OK, we need to track this down ASAP.
I have committed a (temporary) fix for this problem. To get a better
solution I have started a thread about this on [E
Brett Porter wrote:
Using the latest of everything doesn't correct the problem - seems like
there's still a bug.
OK, we need to track this down ASAP.
I also had to skip the tests in the doxia-sitetools
to get it to build.
What error did you get? Tests run fine for me on Windows.
I reverted
Using the latest of everything doesn't correct the problem - seems
like there's still a bug. I also had to skip the tests in the doxia-
sitetools to get it to build.
I reverted to 2.0-beta-5, which works but skips the two pages
(index.xml.vm and download.apt.vm). All should be ok once synced
My fault, I published it, assuming whatever would be in the repo
would be correct.
I'll try building the latest of everything and do it again.
- Brett
On 11/08/2007, at 2:52 AM, Dennis Lundberg wrote:
Wendy Smoak wrote:
Any idea what happened to the plugin index page? It was published
tod
Wendy Smoak wrote:
Any idea what happened to the plugin index page? It was published
today (Aug 10) and all the links are to anchors on the index page
rather than to the plugin site. For example:
http://maven.apache.org/plugins/index.html#maven-compiler-plugin/
instead of http://maven.apache.o
Any idea what happened to the plugin index page? It was published
today (Aug 10) and all the links are to anchors on the index page
rather than to the plugin site. For example:
http://maven.apache.org/plugins/index.html#maven-compiler-plugin/
instead of http://maven.apache.org/plugins/maven-comp
16 matches
Mail list logo
