[fedora-java] xmvn/jp-tools bug?

Mikolaj Izdebski mizdebsk at redhat.com
Mon Jun 23 06:16:47 UTC 2014


On 06/21/2014 04:26 AM, Peter MacKinnon wrote:
> After updating to jline-2.10-14.fc21.noarch, I found this:
> 
> $ repoquery -f 'mvn(jline:jline)'
> jline-0:2.10-14.fc21.noarch
> $ repoquery -f 'mvn(jline:jline:1)'
> jline1-0:1.0-7.fc21.noarch
> $ repoquery -f 'mvn(jline:jline:1.0)'
> jline1-0:1.0-7.fc21.noarch

This all seems to be correct. I assume you showed it only for reference.

> $ xmvn-resolve jline:jline:1.0
> /usr/share/java/jline/jline.jar
> $ xmvn-resolve jline:jline:1
> /usr/share/java/jline/jline.jar
> $ rpm -qf /usr/share/java/jline/jline.jar
> jline-2.10-14.fc21.noarch

jline uses new metadata while jline1 still uses legacy depmaps because
it failed to build during mass rebuild (rhbz#1106951).  Depmaps are used
as a fallback - only if resolution using metadata fails. That's the
reason jline "wins".

The solution is to fix rhbz#1106951, i.e rebuild jline1 so that it uses
new metadada format.

-- 
Mikolaj Izdebski
Software Engineer, Red Hat
IRC: mizdebsk


More information about the java-devel mailing list