[
https://issues.apache.org/jira/browse/SHIRO-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13545795#comment-13545795
]
Mladen Marev commented on SHIRO-389:
------------------------------------
Normally I'd agree with Chris, but...
Blueprint would work when you know your configuration upfront. How the user
changes "authenticationCachingEnabled" flag? Opens the bundle and modifies the
flag in the blueprint.xml? Or you would use another file to point if bean
should be instantiated or not.
What if you deliver a shiro.ini to be modified?
I do not agree with circular dependencies note also, because optional imported
packages has nothing to do with compilation. It is a conscious decision what to
be imported optionally.
Anyway. I think someone should decide how the situation will be handled
(optional imports or fragments) for all shiro delivered bundles. I personally
vote for optional imports. Fragments can not be used by other bundles.
> Fix OSGI Exports for shiro-ehcache
> ----------------------------------
>
> Key: SHIRO-389
> URL: https://issues.apache.org/jira/browse/SHIRO-389
> Project: Shiro
> Issue Type: Bug
> Components: Caching
> Affects Versions: 1.2.0, 1.2.1
> Reporter: Chris Geer
> Assignee: Les Hazlewood
> Fix For: 1.2.2, 1.3.0
>
> Attachments: SHIRO_389_core.patch, SHIRO-389.patch
>
>
> Currently the osgi-export in the pom file is org.apache.shiro.ehcache which
> isn't a valid package. It should be changed to org.apache.shiro.cache.ehcache
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
