directory-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kiran Ayyagari <>
Subject Re: unshaded maven dependencies
Date Fri, 04 Sep 2015 09:11:13 GMT
On Fri, Sep 4, 2015 at 4:27 PM, Jan Van Besien <> wrote:

> I'd like to integrate an embedded apacheds LDAP server in my java
> project using the apacheds LdapServer from the apacheds-service
> artifact.
LdapServer is from apacheds-protocol-ldap artifact
the apacheds-service module is for standalone execution of the server.

In embedded mode you need to pick the dependencies and add to your project
take a look at the below pom.xml to see the required dependencies
(they are all in commented section)

> However, I noticed that apacheds-service is a mvn shaded jar, which
> includes its dependencies. This is a real problem because some of its
> dependencies (e.g. bcprov) clash with dependencies I already have in
> my project. Essentially by using a shaded jar, normal mvn dependency
> resolution is no longer possible.
> Assuming there are good reasons for the shaded jar, wouldn't it be
> better to provide both a shaded and normal jar (e.g. the shaded
> version with a different classifier)?
> I assume the shaded jar might make sense in standalone use cases. But
> for inclusion in other java projects, I don't think it is a good idea.
> Thanks
> Jan

Kiran Ayyagari

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message