Bug 1015596 - autogenerated test jar dependencies aren't satisfiable
Summary: autogenerated test jar dependencies aren't satisfiable
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xmvn
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mikolaj Izdebski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-04 14:55 UTC by Robert Rati
Modified: 2013-10-10 14:52 UTC (History)
6 users (show)

Fixed In Version: 1.1.0-2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-10 14:52:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Robert Rati 2013-10-04 14:55:12 UTC
Description of problem:
autogenerated dependencies for test jars seem to be created in to form:
mvn(org.apache.hadoop:hadoop-yarn-server-tests:test-jar:)

But the rpm with the test jars have provides like:
mvn(org.apache.hadoop:hadoop-yarn-server-tests) = 2.0.5-alpha
mvn(org.apache.hadoop:hadoop-yarn-server-tests::tests:) = 2.0.5-alpha

The result is the rpm, which has poms with test-jar dependencies, results in failed dependencies even though the dependencies are actually provided by the packaging saying it is lacking the dependency.  An example rpm with this problem:

http://koji.fedoraproject.org/koji/rpminfo?rpmID=4457348

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Mikolaj Izdebski 2013-10-07 09:47:21 UTC
I am unable to reproduce this.
Please attach a simple reproducer.

Comment 2 Mikolaj Izdebski 2013-10-07 11:38:33 UTC
I think I know where the bug is.

Comment 3 Mikolaj Izdebski 2013-10-07 18:20:46 UTC
Fixed in xmvn-1.1.0-2

Comment 4 Mikolaj Izdebski 2013-10-10 14:52:16 UTC
I believe that this bug is fixed in xmvn-1.1.0-2,
which is available in Fedora 20, so I am closing this bug now.

The build containing the fix can be found at Koji:
http://koji.fedoraproject.org/koji/buildinfo?buildID=469812


Note You need to log in before you can comment on or make changes to this bug.