From Fedora Project Wiki

(Created page with '= Maven for EPEL = This page hosts information about the current attempt to bring maven2 into the EPEL space. At the current time, the latest version that appears to be able to b...')
 
No edit summary
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Maven for EPEL =
= Maven for EPEL =
This page hosts information about the current attempt to bring maven2 into the EPEL space. At the current time, the latest version that appears to be able to be built for EL5 is maven 2.0.4
This page hosts information about the current attempt to bring maven2 into the EPEL space. At the current time, the latest version that appears to be able to be built for EL5 is maven 2.0.4
== Source ==
Current dependency tree: http://www.shsu.edu/~ajm023/maven2-el5-srpm/
NOTE: Building many of these components depends on EPEL.


== Progress ==
== Progress ==
Line 10: Line 16:
|Track down all dependencies and get a successful build of maven2 to run on EL5|| [[User:maxamillion  | Adam Miller]] || '''<span style="color:green">Done</span> '''
|Track down all dependencies and get a successful build of maven2 to run on EL5|| [[User:maxamillion  | Adam Miller]] || '''<span style="color:green">Done</span> '''
|-
|-
|Map out and document the dependencies needed so that they can be branched for EPEL  || [[User:maxamillion  | Adam Miller]] || '''<span style="color:green">In progress</span> '''
|Map out and document the dependencies needed so that they can be branched for EPEL  || [[User:maxamillion  | Adam Miller]] || '''<span style="color:orange">In progress</span> '''
|-
|-
|}
|}
Line 16: Line 22:
== Dependency Info ==
== Dependency Info ==
Preliminary build has yielded some data about packages and their dependencies. I will be working towards making a complete list along with requirements such that we can successfully branch and maintain maven2 in EPEL.
Preliminary build has yielded some data about packages and their dependencies. I will be working towards making a complete list along with requirements such that we can successfully branch and maintain maven2 in EPEL.
NOTE: The dependency tree listed here are only packages not currently in EPEL.


{|
{|
! Package !! Parent Package (dep satisfied) !! Required Version !! Status (For now)
! Package !! Parent Package (dep satisfied) !! Required Version !! Build Status (For now)
|-
|-
| maven2
| maven2
Line 24: Line 32:
| 2.0.4
| 2.0.4
| <span style="color:green">OK</span>
| <span style="color:green">OK</span>
|-
| pmd
| maven2
| >=3.6
| <span style="color:green">OK</span>
|-
| jaxen
| pmd
|
| <span style="color:green">OK</span>
|-
| dom4j
| jaxen
|
| <span style="color:green">OK</span>
|}


|}
== Workflow ==
So far this has been my workflow, the image quality is horrible because I snapped it with my cellphone here at the office but it gives a little insight into what's going on and what's been done. The dependency tree is only populated with the packages that are not currently in EPEL EL5.
 
[[File:Maven2_el5_workflow.jpg]]

Latest revision as of 14:29, 22 February 2010

Maven for EPEL

This page hosts information about the current attempt to bring maven2 into the EPEL space. At the current time, the latest version that appears to be able to be built for EL5 is maven 2.0.4

Source

Current dependency tree: http://www.shsu.edu/~ajm023/maven2-el5-srpm/

NOTE: Building many of these components depends on EPEL.


Progress

There is currently a successful and known working (only works with OpenJDK, Sun Java causes classpath errors) build located for el5-i386 here.

Item Owner Status
Track down all dependencies and get a successful build of maven2 to run on EL5 Adam Miller Done
Map out and document the dependencies needed so that they can be branched for EPEL Adam Miller In progress

Dependency Info

Preliminary build has yielded some data about packages and their dependencies. I will be working towards making a complete list along with requirements such that we can successfully branch and maintain maven2 in EPEL.

NOTE: The dependency tree listed here are only packages not currently in EPEL.

Package Parent Package (dep satisfied) Required Version Build Status (For now)
maven2 n/a 2.0.4 OK
pmd maven2 >=3.6 OK
jaxen pmd OK
dom4j jaxen OK

Workflow

So far this has been my workflow, the image quality is horrible because I snapped it with my cellphone here at the office but it gives a little insight into what's going on and what's been done. The dependency tree is only populated with the packages that are not currently in EPEL EL5.