maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Vowles <rich...@bluetrainsoftware.com>
Subject Re: Plugin dependencies bug
Date Fri, 13 May 2011 21:13:26 GMT
On Sat, May 14, 2011 at 12:08 AM, Barrie Treloar <baerrach@gmail.com> wrote:

>

I can hack your pom to get it to work by forcing the dependency via:
>  <dependencyManagement>
>    <dependencies>
>      <dependency>
>        <groupId>org.codehaus.groovy</groupId>
>        <artifactId>groovy-all</artifactId>
>        <version>1.7.10</version>
>      </dependency>
>    </dependencies>
>  </dependencyManagement>
>

I have no problem with a hacked pom to workaround it.


>
> Maybe someone else can tell us why in the easyb jar a version of
>    <dependency>
>      <groupId>org.codehaus.groovy</groupId>
>      <artifactId>groovy-all</artifactId>
>      <version>[1.7.4,1.7.99)</version>
>    </dependency>
> fails to be resolved when you use it.
>
> Yes, thats the question. I can trace it through and can see why its failing
to be resolved, but I don't know why the repository that it is in (local and
remote) is thrown away simply because it is in a version range.


-- 
---
Richard Vowles,
Grails, Groovy, Java
Consistency is the last refuge of the unimaginative - Oscar Wilde
ph: +64275467747, linkedin, skype:rvowles
get 2Gb shared disk space in the cloud - Dropbox, its incredibly useful! -
http://tinyurl.com/cmcceh
podcast: http://www.illegalargument.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message