You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Bastiaan Bakker (JIRA)" <ji...@apache.org> on 2006/09/25 13:41:51 UTC

[jira] Commented: (DIRSERVER-750) update commons-lang from 2.0 to 2.1

    [ http://issues.apache.org/jira/browse/DIRSERVER-750?page=comments#action_12437524 ] 
            
Bastiaan Bakker commented on DIRSERVER-750:
-------------------------------------------

hmm, I see I created this issue with priority 'major', should be 'minor' I guess. Looks like I can't modify the priority however....

Anyway, apacheds-shared-ldap, has a build dep on commons-lang in its pom, but doesn't actually use commons-lang. So the whole dep can be removed. 
For apacheds server,  it recompiles fine with commons-lang 2.1.
I do see usage of comons-lang in  server-jndi/src/main/java/org/apache/directory/server/jndi/ServerContextFactory.java and
core/src/test/java/org/apache/directory/server/core/jndi/LdapJndiPropertiesTest.java without a commons-lang dep in the correspondind poms. Do they rely on a transitive dep?




> update commons-lang from 2.0 to 2.1
> -----------------------------------
>
>                 Key: DIRSERVER-750
>                 URL: http://issues.apache.org/jira/browse/DIRSERVER-750
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>    Affects Versions: 1.0-RC4
>            Reporter: Bastiaan Bakker
>
> ApacheDS currently uses jakarta commons-lang 2.0, which is over three years old and incompatible with JDK1.5 (enum keyword conflict). comons-lang-2.1 (the latest released version) is backwards compatible with 2.0 (with one exception that doesn't affect ApacheDS) and contains several bugfixes and improvements. It's also required by spring-ldap, a package that can be useful in partition backend code. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira