[
https://issues.apache.org/jira/browse/SLING-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642471#comment-14642471
]
Carsten Ziegeler commented on SLING-4906:
-----------------------------------------
I think it would make sense to trim down the list to the bare minimum needed.
If there is no downside in removing javax.mail, we should do it.
However, most of the stuff comes from the system bundle anyway, so we should be
fine now
> Reduce (transitive) package dependencies
> ----------------------------------------
>
> Key: SLING-4906
> URL: https://issues.apache.org/jira/browse/SLING-4906
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Reporter: Carsten Ziegeler
> Assignee: Chetan Mehrotra
> Fix For: Commons Log 4.0.4
>
>
> It seems that updating innocent looking bundles cause the whole system to
> restart. We now had a case where a bundle containing some package was
> updated. This package was imported by the groovy bundle and the groovy bundle
> was imported by the commons.log bundle.
> Unfortunately, the log4j.api bundle - which is imported by nearly almost
> every bundle - imports the impl package which is exported by the commons.log
> bundle.
> Obviously the best solution would be if the log4j.api bundle would not import
> packages, but I guess that's not feasible the way log4j works.
> Therefore we should have a look at our commons.log bundle to see whether we
> can reduce the imports, or the effect of other bundles being updated
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
