directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot (JIRA)" <>
Subject [jira] [Commented] (DIRSERVER-1877) No-dependency ditribution for apache ds should be made available
Date Wed, 31 Jul 2013 09:35:50 GMT


Pierre-Arnaud Marcelot commented on DIRSERVER-1877:

Of course, I understand and agree too. But in the real world, the situation is a bit more
complicated than that.

Most of our users are using Maven or Ant (+ Ivy) and we already build and deliver 14 different
packages for each release, which need to be maintained and tested.

I'm absolutely not against a "no-dependency" distribution, It would be a great thing to have.
But it's always a (difficult) matter of finding the good balance between the time spent building
and maintaining it and how much benefit it brings to the community.
The Apache Directory Team is small and does not have infinite amount of time to work on the
project, which forces us to makes choices.

We're sorry about the inconvenience and I hope that, at least, you managed to find what you
wanted with our indications.

That's how Open Source works. Contributions are greatly welcomed. ;)
> 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