shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Demers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SHIRO-641) shiro-*-core Jars define some of the same classes from their dependencies
Date Tue, 23 Jan 2018 14:39:00 GMT

    [ https://issues.apache.org/jira/browse/SHIRO-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335847#comment-16335847
] 

Brian Demers commented on SHIRO-641:
------------------------------------

[~rjn] We should move the conversation to SHIRO-632.  Can you include the details of your
environment? War file? Embedded Tomcat etc.

Also take a look at:  [https://github.com/apache/shiro/pull/75,] and let us know if that
fixes the issue you are seeing.

> 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
>            Priority: Major
>
> 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
(v7.6.3#76005)

Mime
View raw message