You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org> on 2011/03/09 19:52:59 UTC

[jira] Resolved: (DIRSHARED-100) Fix outstanding build issues

     [ https://issues.apache.org/jira/browse/DIRSHARED-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre-Arnaud Marcelot resolved DIRSHARED-100.
----------------------------------------------

    Resolution: Fixed
      Assignee: Pierre-Arnaud Marcelot

Fixed.

> Fix outstanding build issues
> ----------------------------
>
>                 Key: DIRSHARED-100
>                 URL: https://issues.apache.org/jira/browse/DIRSHARED-100
>             Project: Directory Shared
>          Issue Type: Task
>            Reporter: Stefan Seelmann
>            Assignee: Pierre-Arnaud Marcelot
>             Fix For: 1.0-M2
>
>
> Fix outstanding legal issues mentioned in http://markmail.org/thread/gpqgxs4iilpszlb5 
> It may be interesting to use the Felix Bundle Maven plugin to make the 'shared-all' a real OSGI-ready bundle (It's a simple jar ATM).
> It would be also interesting to bundle with the distribution the log4j dependency, just like we do for ApacheDS. I had to download this aside and add it to the build path to be able to work with the LDAP API. I understand that we're using a logging "façade" (SLF4J) to allow the user to choose the implementation he prefers, but I think most users of the API won't know and don't care about it. If we bundle log4j in the final distribution, the LDAP API can be used in one simple step and people willing to use their logger implementation of choice can easily remove the bundle log4j and add their own jar.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira