It's the same with 2.2 and 2.3 so it's not the forking. I added
dependency:resolve to the release profile just so I could see the scopes
after javadoc...and that causes shade to work ok. Javadoc is definitely
doing something hokey. I'll look more in the morning but I may just
leave dependency:resol
I think a more recent version of javadoc started forking a lifecycle
- but I'm not quite sure why. I was wondering that myself as it seems
to be problematic.
- Brett
On 21/11/2007, at 10:55 AM, Brian E. Fox wrote:
The javadoc plugin is screwing up the uber jar. If you run mvn package
from
The javadoc plugin is screwing up the uber jar. If you run mvn package
from mvn-core, everything is fine. Mvn package -Prelease and the uber
jar is missing a ton of stuff. I poked around a bit and found that
removing javadoc from the release profile fixes it. I tried bumping it
to version 2.3 and t
Ok, we'll respin the release when this is fixed.
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Mauro Talevi
Sent: Tuesday, November 20, 2007 4:24 AM
To: dev@maven.apache.org
Subject: Re: [vote] release maven 2.0.8
olivier lamy wrote:
> Hi,
> I have an issue :
>
> [
I just updated http://jira.codehaus.org/browse/MRM-594 to attach a new
patch. This one fully solves the issue by providing storage of the
configuration in archvia XML configuration and a management Web UI.
Nico.
olivier lamy wrote:
Hi,
I have an issue :
[WARNING] repository metadata for: 'artifact
org.apache.maven.plugins:maven-clean-plugin' could not be retrieved from
repository: rec-ap2-m2-plugins due to an error: Unsupported Protocol:
'http': Cannot find wagon which supports the requested protocol: h
Hi,
I have an issue :
[WARNING] repository metadata for: 'artifact
org.apache.maven.plugins:maven-clean-plugin' could not be retrieved from
repository: rec-ap2-m2-plugins due to an error: Unsupported Protocol:
'http': Cannot find wagon which supports the requested protocol: http
deploying
[INFO]
