[ 
https://issues.apache.org/jira/browse/DIRSERVER-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722397#comment-13722397
 ] 

Pierre-Arnaud Marcelot commented on DIRSERVER-1877:
---------------------------------------------------

I took the example of the "apacheds-service" jar, which is the jar bundled with 
all our standalone distributions.

It explains why it bundles also Log4J, because we want a "façade" for SLF4J, to 
be able to log events.

Now, if you're to embed ApacheDS into your own code with your own requirements, 
of course, Log4J isn't mandatory and you're safe to decide whatever SLF4J 
façade you prefer.

On the Jetty part, is it "mandatory" because ApacheDS has a feature to launch 
an embedded HTTP server. The idea here, is to be able to provide things like a 
DSML gateway or a JSON access service for example.
If you don't plan to run the HTTP server in your embedded ApacheDS instance, 
you can forget it.
                
> No-dependency ditribution for apache ds should be made available
> ----------------------------------------------------------------
>
>                 Key: DIRSERVER-1877
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1877
>             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 
> version.

--
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: http://www.atlassian.com/software/jira

Reply via email to