[
https://issues.apache.org/jira/browse/SHIRO-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13541941#comment-13541941
]
Les Hazlewood edited comment on SHIRO-389 at 1/1/13 11:18 PM:
--------------------------------------------------------------
I have a question:
It feels odd to me to have the following line in core's pom.xml OSGi statements:
<code>org.apache.shiro.cache.ehcache;version="${shiro.osgi.importRange}";resolution:=optional,</code>
shiro-core has no dependencies whatsoever on ehcache - why then would this be
included in the core's pom file?
was (Author: lhazlewood):
I have a question:
It feels odd to me to have the following line in core's pom.xml OSGi statements:
{{org.apache.shiro.cache.ehcache;version="${shiro.osgi.importRange}";resolution:=optional,}}
shiro-core has no dependencies whatsoever on ehcache - why then would this be
included in the core's pom file?
> 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.1, 1.3.0
> Reporter: Chris Geer
> 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
