You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2007/08/24 09:38:30 UTC

[jira] Closed: (DIRSERVER-1028) Upgrading dependencies and maven plugins

     [ https://issues.apache.org/jira/browse/DIRSERVER-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks closed DIRSERVER-1028.
-----------------------------------

    Resolution: Fixed
      Assignee: David Jencks

I think all the version changes that can be applied have been.  Plugin version are being handled in DIRSERVER-1032.

The comments about oro and logback are from a post I found commenting on velocity-deps unavailability in recent versions.  Looking at the latest velocity pom I see that jdom, log4j, servlet spec 2.3, logkit, ant 1.6, and werken-xpath are all marked with scope provided.  I have no idea what is going on inside velocity but suspect you can use either log4j or logback.  In any case velocify is only used in the SchemaToolMojo which is used during the build so I think that we are unlikely to run into dependency problems.

> Upgrading dependencies and maven plugins
> ----------------------------------------
>
>                 Key: DIRSERVER-1028
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1028
>             Project: Directory ApacheDS
>          Issue Type: Task
>    Affects Versions: 1.5.0
>            Reporter: Emmanuel Lecharny
>            Assignee: David Jencks
>             Fix For: 1.5.1
>
>
> Here is a list of dependencies and maven plugins version we are using compared to the current version (first number is the last version, second number is the version we are using). We should consider upgrading the versions of all those dependencies.
> apacheds			
> 	mina-core	1.1.2	1.0.3
> 	mina-filter-ssl	1.1.2	1.0.3
> 	commons-io	1.3.2	1.3.1
> 	commons-collections	3.2	3.2
> 	commons-daemon	1.0.1	1.0.1
> 	commons-lang	2.3	2.3
> 	commons-cli	1.1	1.0
> 	commons-dbcp	1.2.2	1.2.2
> 	commons-pool	1.3	1.3
> 	jcl104-over-slf4j	1.4.3	1.4.0
> 	slf4j-api	1.4.3	1.4.0
> 	nlog4j	1.2.25	1.2.25
> 	jdbm	1.0	1.0
> 	velocity-dep	1.5	1.4.0
> 	antlr	2.7.7	2.7.7
> 	junit	4.4	3.8.1
> 	quartz	1.6.0	1.5.1
> 	jug-asl	2.0.0	2.0.0
> 	derby	10.3.1.4	10.2.2.0
> 	spring-core	2.0.6	1.2.9
> 	spring-beans	2.0.6	1.2.9
> 	spring-context	2.0.6	1.2.9
> 	maven-plugin-api	2.0.7	2.0.6
> 	maven-project	2.0.7	2.0.6
> 	maven-archiver	2.2	2.0.5
> 	plexus-utils	1.4.5	1.4.2
> 	maven-artifact	2.0.7	2.0.6
> 	ldapsdk	4.17	4.1
> 	dependency-maven-plugin	1.0	1.0
> 			
> 	maven-surefire-plugin	2.3	2.3
> 	maven-compiler-plugin	2.0.2	2.0.2
> 	maven-eclipse-plugin	2.4	2.3
> 	maven-antlr-plugin	2.0-beta-1	2.0-beta-1
> 	maven-remote-resources-plugin	1.0-alpha-5	1.0-alpha-5
> 	maven-jar-plugin	2.1	2.1
> 	maven-assembly-plugin	2.2-beta-1	2.1
> 	maven-javadoc-plugin	2.3	2.3
> 			
> 			
> 			
> 			
> shared			
> 	commons-collections	3.2	3.2
> 	commons-lang	2.3	2.3
> 	slf4j-api	1.4.3	1.4.0
> 	nlog4j	1.2.25	1.2.25
> 	antlr	2.7.7	2.7.7
> 	mina-core	1.1.2	1.0.3
> 	junit	4.4	3.8.1
> 			
> 	maven-surefire-plugin	2.3	2.3
> 	maven-compiler-plugin	2.0.2	2.0.2
> 	maven-antrun-plugin	1.1	1.1
> 	maven-antlr-plugin	2.0-beta-1	2.0-beta-1
> 	maven-remote-resources-plugin	1.0-alpha-5	1.0-alpha-5
> 	maven-javadoc-plugin	2.3	2.3
> 			
> daemon			
> 	slf4j-api	1.4.3	1.4.0
> 	nlog4j	1.2.25	1.2.25
> 	commons-daemon	1.0.1	1.0.1
> 	junit	4.4	3.8.1
> 	wrapper	2.3.2	2.3.2
> 	maven-surefire-plugin	2.3	2.3
> 	maven-remote-resources-plugin	1.0-alpha-5	1.0-alpha-5
> 	maven-jar-plugin	2.1	2.1
> 	maven-compiler-plugin	2.0.2	2.0.2
> 	maven-install-plugin	2.2	2.2
> 	maven-javadoc-plugin	2.3	2.3

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.