Vincent, the uber jar when run in release mode was missing the http wagons and actually a bunch of other stuff too. I think I've figured it out, shade doesn't declare @requiresDependencyResolution and javadoc only wants compile so then shade gets the leftovers. It explains why dependency:resolve fixes it again because I need the test scope, thus putting everything back for the plugin.
I think to detect this sooner in the future, maven should not provide any dependencies if they are not asked for, leaving the things from the last mojo is too non-deterministic. -----Original Message----- From: Vincent Siveton [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 21, 2007 7:19 AM To: Maven Developers List Subject: Re: Re: [vote] release maven 2.0.8 Hi Brian, 2007/11/20, Brian E. Fox <[EMAIL PROTECTED]>: > 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 What kind of stuff? I tried it and the uber jar sounds correct to me. Cheers, Vincent > 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] > > --------------------------------------------------------------------- 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]
