Bug 1109385 - Maven rpms to be included in EPEL repos
Summary: Maven rpms to be included in EPEL repos
Keywords:
Status: CLOSED DUPLICATE of bug 1011115
Alias: None
Product: Fedora
Classification: Fedora
Component: maven
Version: rawhide
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: 2014-06-13 18:58 UTC by Salim Badakhchani
Modified: 2016-04-18 06:04 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-13 05:24:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Salim Badakhchani 2014-06-13 18:58:08 UTC
Description of problem:

There seems to be no maven rpms in epel repos.  They exist for Fedora and and Red Hat via Brew but I was hoping to use maven for CentOS.  Can we make the version in Brew avaiable in EPEL?

Additional info:

Comment 1 Scott Williams 2014-06-13 23:38:50 UTC
I don't think this should be too much trouble.  I've been using the mvn3 apache tarball here in el6 without issue.

I'll add my +1 this request.

Scott

Comment 2 Mattias Ellert 2014-06-14 06:23:23 UTC
This bugreport is marked "el6". Was this intentional? Or did you in fact intend to mark it "epel7"?

The EPEL 7 branch for maven-patch-plugin has been created a long time ago. However, it is not yet buildable since one of its build dependencies, maven-docck-plugin is not yet built in EPEL 7.

I'm all for providing the maven-patch-plugin in EPEL 7 - which is why I requested the branch - I need it as a build dependency for one of the packages I maintain. And I intend to do the build once the missing dependency is available.

Please note that maven-patch-plugin is the only maven package I maintain in Fedora. I am not involved in the packaging of any other maven related packages. So if by filing this bug you intended to reach someone that can influence the Fedora Java packagers to embrace EPEL 7 I'm afraid I am not it. My own, admittedly minor, efforts to make this happen has not been successful.

I hope you are successful in your efforts to persuade the Java maintainers to build their packages for EPEL 7 - especially the missing parts of the maven tool chain that is blocking the builds for maintainers of other packages. For this particular maven plugin - which is the only one I maintain - I myself am blocked from building it in EPEL 7 due to other missing maven packages.

I appreciate your request and would like to comply to it, but I am not capable to do so at this time for the reasons stated above.

Comment 3 Salim Badakhchani 2014-06-15 17:35:25 UTC
This is meant for el6.  I was really referning to maven itself and not the maven-patch-plugin...Apologies for using this component to raise the bug but I didn't see one for maven.

I'm happy chase this with however is concerned.  This is going to be quite important from an rcm middleware aspect as now that we have CentOS onboard we are in the process of utilising it for a numnber of projects.

Comment 4 Salim Badakhchani 2014-09-16 06:23:07 UTC
Hi, I was wondering if there has been any progress regarding this?

Comment 5 Mattias Ellert 2014-10-12 17:44:26 UTC
Reassigning to maven - since the original reporter in comment 3 says "I was really referning to maven itself and not the maven-patch-plugin".

Comment 6 Mikolaj Izdebski 2014-10-13 05:24:21 UTC
Maven consists of about 200 packages (if counnting dependencies), most of which are not included in RHEL 6 or EPEL.  We would need to add a signifficant number of packages to EPEL and maintain them.

While it would definitely be possible to add Maven to EPEL 6, we don't have enough manpower to do that, so that's not going to happen unless someone volounteers to maintain over 100 new packages in EPEL.

*** This bug has been marked as a duplicate of bug 1011115 ***


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