You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Ceki Gulcu (JIRA)" <ji...@apache.org> on 2007/08/23 11:06:31 UTC
[jira] Commented: (DIRSERVER-1028) Upgrading dependencies and maven
plugins
[ https://issues.apache.org/jira/browse/DIRSERVER-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522069 ]
Ceki Gulcu commented on DIRSERVER-1028:
---------------------------------------
Hello,
Nlog4j is no longer being maintained. Nlog4j 1.2.25 has not followed
the changes in the SLF4J project structure and is likely to fail when
used in conjunction with SLF4J version 1.3.0 and later. Note that
SLF4J 1.3.0 was released on February 25th of this year.
I would recommend that you switch to log4j 1.2.14 by dropping the
nlog4j dependency and adding a dependency on slf4j-api, slf4j-log4j12
and log4j. Since you are using Maven, adding slf4j-log4j12 as a
dependency will transitively pull-in log4j 1.2.14 as well as slf4j-api.
The following entry is all you need:
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
<version>1.4.3</version>
</dependency>
As long as ApacheDS is the end-application, the above is
fine. However, for shared libraries, I'd recommend a slighlty more
refined approach of separation between the dependency on the SLF4J API
and on a binding (say slf4j-log4j12) for testing.
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>1.4.3</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
<version>1.4.3</version>
<scope>test</scope>
</dependency>
The general logic is also discussed at:
http://slf4j.org/faq.html#maven2
I hope this helps,
> 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
> 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.