directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSHARED-100) Fix outstanding build issues
Date Wed, 09 Mar 2011 18:52:59 GMT

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

Pierre-Arnaud Marcelot commented on DIRSHARED-100:
--------------------------------------------------

Having thought about the idea of having a common 'shared-all' artifact as a bundle, I think
it's a pretty bad idea.
We're going to run into several bad issues. Especially if we shade other bundles that have
an activator.

I can find any solution to fix a case where we shaded two bundles, each one having an activator.

What do we do for activation in the resulting bundle ? We can't have more than one bundle
assigned to a bundle...

Although it works great in the case of a simple plain jar, I really think it goes against
OSGI principles to have a shaded bundle of all shared artifacts.

> 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
>             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

Mime
View raw message