History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: MAVEN-1712
Type: Task Task
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Arnaud Heritier
Reporter: Arnaud Heritier
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Maven 1

Unify dependencies

Created: 11/Oct/05 04:13 AM   Updated: 08/Mar/06 10:47 PM
Component/s: None
Affects Version/s: 1.1-beta-2, 1.1-beta-1
Fix Version/s: None

Time Tracking:
Not Specified


 Description  « Hide
In maven 1.X, we use only two classloaders :
  • root : where are loaded : ant, commons-logging , log4j and the jdk tools
  • root.maven : maven and all other dependencies loaded for the plugins.

In m1 I (we) don't want to do some big refactoring, because we have already m2 for this.
What I propose is to try to update all dependencies to unify them between the core and the plugins :
ant=1.6.5
ant-junit=1.6.5
ant-launcher=1.6.5
ant-trax=1.6.5
commons-beanutils=1.7.0
commons-cli=1.0-beta-2
commons-collections=3.0
commons-httpclient=2.0.2
commons-io=1.0
commons-jelly=1.0
commons-jelly-tags-ant=1.1
commons-jelly-tags-define=1.0
commons-jelly-tags-util=1.1.1
commons-jelly-tags-xml=1.1
commons-jexl=1.0
commons-lang=2.0
commons-logging=1.0.3
dom4j=1.4
forehead=1.0-beta-5
log4j=1.2.8
maven-model=3.0.1
plexus-utils=1.0-alpha-3
wagon-file=1.0-alpha-3
wagon-http=1.0-alpha-3
wagon-provider-api=1.0-alpha-3

I will also add a paragraph on the page "writing a plugin" (http://maven.apache.org/using/developing-plugins.html) to incite plugins
developpers to use the same releases of the libraries defined in maven's core and in maven's plugins bundled with the core.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Arnaud Heritier - 13/Oct/05 05:46 PM
Finally I'm using these releases :

maven.jar.commons-beanutils=1.6.1
maven.jar.plexus-utils=1.0.3
maven.jar.wagon-file=1.0-alpha-4


Arnaud Heritier - 17/Oct/05 12:27 AM
Done. All dependencies are unified (except for maven 1.1 used in artifact plugin) and the jar override is activated in plugin-parent to be sure that all our plugins use these releases !
If you want to update a dependency, you should try to do it in each plugin which use it (and in the core if necessary).