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 ~
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:
>
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
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
>>
>>
>
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
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
