[
https://issues.apache.org/jira/browse/KARAF-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167570#comment-13167570
]
Guillaume Nodet commented on KARAF-1093:
----------------------------------------
There's a downside in turning this jar into bundle. Having utility classes
into their own bundles means that they are much more likely to change than
interfaces, and having a bundle used by lots of other bundles means that a
refresh may be very disruptive in the osgi runtime. That's the reason why
granularity is a choice (see the discussion we had on shell/console). Small
jars aren't always better and having bundles being logically self-contained is
a good thing imho.
> Make org.apache.karaf.util a bundle
> -----------------------------------
>
> Key: KARAF-1093
> URL: https://issues.apache.org/jira/browse/KARAF-1093
> Project: Karaf
> Issue Type: Improvement
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 3.0.0
>
>
> Currently org.apache.karaf.util is no bundle. The classes are needed in many
> karaf projects and are currently included in each of these bundles.
> This leads to a lot of duplication and requires that the util package is
> marked as private in each consuming bundles, so the bundle plugin includes it
> into the jar.
> I propose to make org.apache.karaf.util a normal bundle and remove the
> private package statements from all consuming bundles.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
