Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1049998

Summary: maven-plugin-bundle does not Require felix-parent/mvn(org.apache.felix:felix-parent)
Product: Red Hat Enterprise Linux 7 Reporter: jcpunk
Component: maven-plugin-bundleAssignee: Java maintainers <java-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Jan Kepler <jkejda>
Severity: unspecified Docs Contact:
Priority: low    
Version: 7.0CC: csieh, jcpunk, jkejda, misterbonnie, mizdebsk, riehecky
Target Milestone: rcKeywords: Unconfirmed
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-22 05:01:58 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:
Attachments:
Description Flags
mock config for replication none

Description jcpunk 2014-01-08 15:30:53 UTC
Created attachment 847206 [details]
mock config for replication

Description of problem: My understanding of the maven-local package is that it then pulls in all the dependencies for building maven packages.  Through a chain of dependencies maven-plugin-bundle is pulled in.  In Fedora (19 & 20) maven-plugin-bundle Requires: felix-parent.  However, in RHEL7 it does not.

I believe this missing Require is incorrect.  Several packages using maven cannot be rebuilt on RHEL 7 as a result.  args4j is one example

Version-Release number of selected component (if applicable):maven-plugin-bundle-2.3.7-11.el7.noarch.rpm


How reproducible: 100%


Steps to Reproduce:
1. rebuild args4j-2.0.16-11.el7.src.rpm on RHEL 7
2. note it does not, due to missing deps that Fedora provides from maven-plugin-bundle

Actual results:
maven-local does not provide the full maven environment due to missing felix-parent from maven-plugin-bundle

Expected results:
similar use of maven-local as in Fedora

Additional info:
I've attached a mock config for RHEL 7 to replicate

Comment 3 Mikolaj Izdebski 2014-01-08 16:04:39 UTC
maven-plugin-bundle in RHEL 7 works fine without felix-parent, so absence of felix-parent Requires is correct.  maven-local doesn't need felix-parent either.

I suppose there's missing dependency somewhere else, but not in maven-plugin-bundle.  I'll investigate this.

Comment 4 Mikolaj Izdebski 2014-01-08 19:43:57 UTC
I am not able to reproduce this.

I downloaded args4j from [1] and built in mock (config simillar to attached).  First I got a build failure:

[ERROR]  Plugin org.apache.maven.plugins:maven-install-plugin:2.3.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-install-plugin:jar:2.3.1: The repository system is offline but the artifact org.apache.maven.plugins:maven-install-plugin:pom:2.3.1 is not available in the local repository. -> [Help 1] 

After manually installing maven-install-plugin in mock args4j was built successfully.  felix-parent was not installed in mock chroot.

Without additional information I am unable to resolve this.
Please at least attach full build logs from mock.

[1] ftp://ftp.redhat.com/redhat/rhel/beta/7/source/SRPMS/args4j-2.0.16-11.el7.src.rpm

Comment 5 jcpunk 2014-01-09 17:46:18 UTC
I fear I'm running into my complete lack of understanding on maven.

Basically I found the build error and traced it back to a dependency difference between maven-plugin-bundle in Fedora and in RHEL7.

I've no idea how to test/evaluate/approach/etc the maven world.

I know that the args4j package expects some things in the buildroot based on maven-local.  I couldn't tell you why or what they are for or really how those expetations were decided.

Basically all I do know, is that the assumptions about what maven-local does in Fedora are shared in RHEL7.  The point of difference I've located is here on maven-plugin-bundle.

If it is supposed to be this way, then that is the way it is.  I've got a fair mess of srpms in RHEL7 that use the Fedora assumptions.  So I aimed here....

I'm going to clear the needinfo, as this is really aimed at this difference between Fedora and RHEL7.  If I'm wrong to clear it let me know and I'll get more info in here.

This bug may not be filed in the right place..... I fear my no knowledge of the maven world is showing greatly.

Comment 6 RHEL Program Management 2014-03-22 06:16:28 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 7 Mikolaj Izdebski 2016-07-22 05:01:58 UTC
As described above, I'm not able to reproduce problem described in this bug report, which has been inactive for an extended period of time. I am going to close it due to inactivity. If you would like to pursue this matter feel free to reopen this bug and provide information required to reproduce the problem.

If this issue is critical or in any way time sensitive, please raise a ticket through the regular Red Hat support channels to ensure it receives the proper attention and prioritization to assure a timely resolution.