Bug 913079

Summary:	Knowledge about Fedora maven repo not passed on to maven-invoker-plugin
Product:	[Fedora] Fedora	Reporter:	Mattias Ellert <mattias.ellert>
Component:	xmvn	Assignee:	Mikolaj Izdebski <mizdebsk>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	19	CC:	akurtako, java-sig-commits, mizdebsk, msrb, sochotni, tradej
Target Milestone:	---	Keywords:	Upstream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	0.4.0-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-15 15:52:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	914607

Description Mattias Ellert 2013-02-20 10:19:23 UTC

Description of problem:

I must start with saying that I don't know if I should report this problem to maven, xmvn, maven-invoker-plugin or javapackages-tools. So please reassign as you see fit.

The new mvn command in Fedora 19 does not by default know about the Fedora maven repositories in /usr/share/maven-fragments and /usr/share/maven-poms. Normally this is not so much of a problem for building Fedora packages since the mvn-rpmbuild script still knowns about them.

The problem arises when the maven project you are building using mvn-rpmbuild is in turn using the maven-invoker-plugin to invoke additional maven runs. These runs are invoked by calling mvn and therefore does not find the necessary dependencies even though they are installed.

For an example see the failed build in koji:

https://koji.fedoraproject.org/koji/buildinfo?buildID=389524

The compilation and creation of the jar works fine, but then during the running of the unit tests that are run using invoker:run the tests fail because the same dependencies that were found during the build, are no longer found when mvn is called from the maven-invoker-plugin.

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

maven.noarch 0:3.0.4-32.fc19
maven-invoker-plugin.noarch 0:1.8-4.fc19
javapackages-tools.noarch 0:0.12.1-1.fc19
xmvn.noarch 0:0.3.1-1.fc19

How reproducible:

Try building a package that uses maven-invoker-plugin to run unit test, like e.g. maven-patch-plugin. The build of the package works on F18 but fails on F19.

Comment 1 Mikolaj Izdebski 2013-02-20 13:10:42 UTC

Thank you a lot for the report.

This is related to bug #911365 (with aopalliance and cglib), but not exactly the same

The problem is in importing packages between Plexus class realms. I'll work on a fix.

Comment 2 Mattias Ellert 2013-03-11 15:52:00 UTC

Hi again!

Do you have any estimate whether this will be fixed soon.
If a solution will take a long time I can resolve the FTBFS in maven-patch-plugin (bug #914607) by temporarily disabling the unit tests until this issue is fixed. If it will happen soon I could wait and rebuild maven-patch-plugin with the unit test still enabled after this issue has been fixed.

Comment 3 Mikolaj Izdebski 2013-03-11 16:26:52 UTC

This will be fixed when xmvn-0.4.0 comes out.

Currently 0.4.0-SNAPSHOT is build for f19-java and we're testing it and fixing any bugs. If everything goes according to the plan then xmvn-0.4.0 will be released and built for f19 by the end of next week.

Comment 4 Mikolaj Izdebski 2013-03-13 08:57:19 UTC

Fedora 19 was branched, moving fo F19.

Comment 5 Mikolaj Izdebski 2013-03-13 08:59:12 UTC

Fixed in upstream.

Comment 6 Mikolaj Izdebski 2013-03-13 11:18:05 UTC

Fixed in xmvn-0.4.0-0.4

Comment 7 Mikolaj Izdebski 2013-03-15 15:52:21 UTC

I believe that this bug is fixed in xmvn-0.4.0-1,
which is available in Fedora 19, so I am closing this bug now.
Thank you for reporting it.  You are welcome to submit any further reports.

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