buildr-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Assaf Arkin" <ar...@intalio.com>
Subject Re: problem with how poms are located
Date Wed, 28 Nov 2007 08:26:15 GMT
Indeed.  I just fixed this in the trunk.

Assaf

On 11/27/07, Tommy@ke4kug.net <Tommy@ke4kug.net> wrote:
>
> It appears to me that there is a bug in how an artifact's POM is
> located (maven coordinates).
> Using the Maven central repo's testng jars as an example, when an
> artifact has a classifier, the classifier shouldn't be used to locate
> the corresponding POM.
> So,
> org.testng:testng:jar:jdk15:5.1
> but,
> org.testng:testng:pom:5.1
>
> I'm seeing a case where (while trying to add transitive dependencies
> to a 'runtime' tarball) buildr is apparently trying to download
> org.testng:testng:pom:jdk15:5.1 and this causes an error since there
> is no such POM in the central repo.
>
> Thanks,
> Tommy
>



-- 
CTO, Intalio
http://www.intalio.com

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