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:resolve in there for now just to get stuff released.
-----Original Message----- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 20, 2007 10:45 PM To: Maven Developers List Subject: Re: [vote] release maven 2.0.8 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 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 that didn't help. Anyone have a clue why javadoc is > hosing shade/uber jar? I'm betting it is messing with the dependency > scopes but not sure why. > > -----Original Message----- > From: Brian E. Fox [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 20, 2007 7:02 AM > To: Maven Developers List > Subject: RE: Re: [vote] release maven 2.0.8 > > 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: [email protected] > Subject: Re: [vote] release maven 2.0.8 > > 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: http >> > > The problem is with the packaging of the uber jar. It skipped the > wagon > > dependencies. > > jar tvf lib/maven-2.0.8-uber.jar | grep http -> should yield wagon > http > provider classes but they are not present. > > I had fixed it and tested against the 2.0.8 tag created yesterday, but > it seems to have re-appeared in the release. It may be down to the > release plugin artifact resolution. > > A quick workaround to get release out would be to branch off 2.0.8 > tag, > fix and release from it. > > In the mean time, I'll investigate the release process packaging. > > Cheers > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
