You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@shiro.apache.org by "Brian Demers (JIRA)" <ji...@apache.org> on 2017/12/11 15:45:04 UTC

[jira] [Resolved] (SHIRO-641) shiro-*-core Jars define some of the same classes from their dependencies

     [ https://issues.apache.org/jira/browse/SHIRO-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Demers resolved SHIRO-641.
--------------------------------
    Resolution: Duplicate

> shiro-*-core Jars define some of the same classes from their dependencies
> -------------------------------------------------------------------------
>
>                 Key: SHIRO-641
>                 URL: https://issues.apache.org/jira/browse/SHIRO-641
>             Project: Shiro
>          Issue Type: Bug
>            Reporter: Buğra Gedik
>
> I've noticed that {{shiro-core.jar}} contains some of the same classes from its dependencies. For instance {{org.apache.shiro.cache.MemoryConstrainedCacheManager}} is present in {{shiro-core.jar}}, but also in {{shiro-cache.jar}}. There are at least a dozen other examples. Similar issue is present for {{shiro-crypto-core.jar}}, {{shiro-config-core.jar}}, etc. Is there a reason behind this?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)