I looked into the jar files, and both shiro-lang-1.4.0 and shiro-core-1.4.0 contain the same classes for example in org.apache.shiro.codec. To be sure I scanned the output of mvn dependency:tree and there is only ever version 1.4.0 occurring. AFAICT nothing else should have a dependency on Shiro.
> Am 19.07.2017 um 15:43 schrieb Brian Demers <[email protected]>: > > It is possible you have an explicit dependency for shiro-lang and shiro-core. > And shiro-core version is getting set to an earlier version by something > during dependency resolution. > You should be able to figure it out by running 'mvn dependency:tree'. > > On Wed, Jul 19, 2017 at 6:53 AM, Emond Papegaaij <[email protected]> > wrote: > On woensdag 19 juli 2017 11:07:28 CEST Joerg Schoenfisch wrote: > > I encountered that Eclipse is not showing me the sources for classes that > > now reside in the 'lang' module. This is due to those classes being both in > > the core.jar and the lang.jar, however, only the lang-sources.jar contains > > the sources for it. Unfortunately, Eclipse picks the class files from the > > core.jar, leaving me without documentation. > > > > Is it intended to duplicate those classes? Is it possible to then also > > duplicate the sources? > > We ran into this as well. Our maven projects are all verified with the maven- > enforcer-plugin with banDuplicateClasses. This is to prevent conflicting > classes on the classpath with larger applications. We had to exclude all shiro > packages from this check. Please remove the classes from shiro-core and rely > on maven's transitive dependencies. > > Best regards, > Emond Papegaaij >
signature.asc
Description: Message signed with OpenPGP
