Re: Plugin dependencies bug

2011-07-01 Thread Mark Derricutt
After having to disable my maven mirror for one reason or another awhile ago I now seem to be getting hit with this rather annoying bug on quite a few projects now that my ~/.m2/repository has a mix of artifacts downloaded via a mirror, and others direct. rm'ing the _maven.repositories file from ~

Re: Plugin dependencies bug

2011-05-24 Thread Richard Vowles
I've pulled all the version ranges out of the artefacts and I still can't release the plugin. I'm just firing up maven in debug again. But yeah, being able to have maven users use the latest version of easyb would really be nice. Richard On Tue, May 24, 2011 at 7:07 PM, Mark Derricutt wrote: >

Re: Plugin dependencies bug

2011-05-24 Thread Mark Derricutt
Has there been any movement on this at all?Beyond the few messages here and only Richards comments on the JIRA ticket it doesn't look like anyways had a chance to look further into this. >From memory there's less than a handful of folk who know how the dependency resolution works, more so now

Re: Plugin dependencies bug

2011-05-14 Thread Barrie Treloar
On Sat, May 14, 2011 at 6:43 AM, Richard Vowles wrote: > On Sat, May 14, 2011 at 12:08 AM, Barrie Treloar wrote: > >> > > I can hack your pom to get it to work by forcing the dependency via: >>   >>     >>       >>        org.codehaus.groovy >>        groovy-all >>        1.7.10 >>       >>     >

Re: Plugin dependencies bug

2011-05-13 Thread Richard Vowles
On Sat, May 14, 2011 at 12:08 AM, Barrie Treloar wrote: > I can hack your pom to get it to work by forcing the dependency via: > > > >org.codehaus.groovy >groovy-all >1.7.10 > > > > I have no problem with a hacked pom to workaround it. > > Maybe

Re: Plugin dependencies bug

2011-05-13 Thread Barrie Treloar
I can't see where your problem is, I never do version ranges. I can hack your pom to get it to work by forcing the dependency via: org.codehaus.groovy groovy-all 1.7.10 Maybe someone else can tell us why in the easyb jar a version of

Re: Plugin dependencies and suspected cyclic references

2008-12-01 Thread Brett Porter
On 01/12/2008, at 4:58 AM, jallen wrote: Should this be detected by mvn and prevented? Yes (I'm surprised it isn't, I thought plugin dependencies were in the reactor ordering). So bottom line question, what is the specified behaviour for what I'm doing? Does maven try and do anything cl

RE: plugin dependencies

2004-07-07 Thread Vincent Massol
> -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: mercredi 7 juillet 2004 01:59 > To: Maven Developers List > Subject: RE: plugin dependencies > > Thanks Vincent, > > I was more referring to adding a DEPRECATION message inside the

RE: plugin dependencies

2004-07-06 Thread Brett Porter
Thanks Vincent, I was more referring to adding a DEPRECATION message inside the cactus:dependency-handle tag, for example, so no new code uses it. - Brett Quoting Vincent Massol <[EMAIL PROTECTED]>: > > > > -Original Message- > > From: Brett Porter [mailto:[EMAIL PROTECTED] > > Sent:

RE: plugin dependencies

2004-07-06 Thread Vincent Massol
> -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: mardi 6 juillet 2004 14:30 > To: Maven Developers List > Subject: plugin dependencies > > Hi, > > After dIon prompted me to take a look yesterday afternoon I figured a way > to > load the plugin contexts on the

Re: plugin dependencies

2003-08-14 Thread Nathan Coast
Worked out that if I add maven.repo.remote=http://www.ibiblio.org/maven/,http://www.codeczar.com/maven/ to the drivers.properties file within maven.jar. Is there some other way of changing this value without having to modify the maven.jar? cheers Nathan Nathan Coast wrote: Hi, Is it possible