directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anshuman (JIRA)" <>
Subject [jira] [Commented] (DIRSERVER-1877) No-dependency ditribution for apache ds should be made available
Date Mon, 29 Jul 2013 10:27:51 GMT


Anshuman commented on DIRSERVER-1877:

Are jetty & servlet api now mandatory dependencies for ApacheDS ? This wasn't the case
in 1.5.x.
What kind of dependency is there on servlet API for an LDAP server? I am asking because when
we want to run this as an embedded LDAP server within a java application, the servlet api
shouldn't be there.

Also, when slf4j is there, log4j couldn't be a mandatory dependency.

Am I missing something here ? To be honest, a runtime/compile time dependency on javax.servlet
/log4j is completely confusing me here.

[INFO] Including org.mortbay.jetty:jetty:jar:6.1.14 in the shaded jar.
[INFO] Including org.mortbay.jetty:servlet-api-2.5:jar:6.1.14 in the shaded jar.
[INFO] Including org.mortbay.jetty:jetty-util:jar:6.1.14 in the shaded jar.
[INFO] Including log4j:log4j:jar:1.2.17 in the shaded jar.

> No-dependency ditribution for apache ds should be made available
> ----------------------------------------------------------------
>                 Key: DIRSERVER-1877
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 2.0.0-M13
>            Reporter: Anshuman
>              Labels: apacheds, distribution, nodep
> The ApacheDS currently ships as a single service jar. This however includes all the dependencies
bundled within it (ex: javax.servlet.*, mina, slf4j, etc). There should be option to download
just the ApacheDS code so that when working in an embedded environment, unwanted dependencies
can be avoided and for mandatory dependencies like mina, the application may chose a different

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message