[
https://issues.apache.org/jira/browse/SHIRO-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143465#comment-16143465
]
Tuomas Kiviaho commented on SHIRO-624:
--------------------------------------
I ran maven to shiro-core and noticed that reason why core fills up with
classes from shiro-config is actually quite trivial.
{{Use Import/Export Package directive
-split-package:=(merge-first|merge-last|error|first) to get rid of this
warning}}
This indicates that there is a clash in packages between shiro-core and
shiro-config because shiro-core still contains deprecated classes that you've
not been able to move to shiro-config thus the BND by default will merge the
classes from shiro-config to shiro-core (which in some scenarios makes
perfectly sense but not here). I'd just exclude the {{org.apache.shiro.config}}
from shiro-core {{Export Package}} directive.
> OSGI: commons configuration import should be optional
> -----------------------------------------------------
>
> Key: SHIRO-624
> URL: https://issues.apache.org/jira/browse/SHIRO-624
> Project: Shiro
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Moritz Bechler
> Priority: Minor
>
> shiro-core OSGI manifest currently declares the
> org.apache.commons.configuration2.interpol import as required.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
