directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <>
Subject [jira] Resolved: (DIREVE-134) Avoid merging third-party binaries in the main jar
Date Thu, 24 Mar 2005 01:06:23 GMT
     [ ]
Alex Karasulu resolved DIREVE-134:

    Resolution: Won't Fix

Thinking about this I realized that the big main based Jar we distribute is not what someone
should use for embedding ApacheDS.  The 3rd party jars and ApacheDS jars are consolidated
in there to allow one to download and fire up the server using a single Jar.  

If you want to embed the server just make sure you add all the jars 3rd party and APacheDS
jars as dependencies in the application you're embedding. 

> Avoid merging third-party binaries in the main jar
> --------------------------------------------------
>          Key: DIREVE-134
>          URL:
>      Project: Directory Server
>         Type: Improvement
>     Versions: 0.8, 0.8.1
>     Reporter: Stephane Bailliez
>     Assignee: Alex Karasulu
>      Fix For: 0.9

> I would highly recommend modifying the packaging strategy.
> Merging all dependencies into the main jar will be extremely painful for users, especially
those who need to embed it will more than certainly conflict with their version of antlr,
commons-collections, commons-lang, commons-logging, regexp, oro, aspectj.
> If you want to merge, you need also to modify the packages so that there could be no
conflict.. which is worth it for a product like Weblogic. Certainly not for ApacheDS
> I think it would be better to use the Class-Path in the manifest to indicates clearly
your dependencies and also name the jar appropriately to figure out the version at first sight
(since the manifest versioning is often not used)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message