[SHIRO-679] Shiro modules have split packages

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.0
• Fix Version/s: 2.0.0-alpha
• Labels: modules
• Assignee: Francois Papon
• Reporter: Timothy James Ward
• Created: 08/Mar/19 12:42
• Updated: 02/Dec/22 00:56
• Resolved: 02/Dec/22 00:56

Description

The Shiro project is split into a number of "modules" which provide OSGi metadata, and will likely provide JPMS Module descriptors at some point in the future. Both of these module platforms play very badly with "split packages" specifically packages that are present with different content across more than one module.

JPMS completely forbids packages from being present in more than one module. OSGi is somewhat more permissive than JPMS, in that split packages are only problematic if they are "exported" and have different content, however in Shiro's case there are no internal packages (all packages are exported).

 

Shiro contains several such packages, for example `org.apache.shiro` and `org.apache.shiro.util` are split with different content across the shiro-core and shiro-lang modules. This must be fixed, with each package (in its entirety) being hosted in a single module if Shiro is going to be usable in a modular Java world.

Issue Links

• fixes: SHIRO-537 Class load issue in OSGI in ClassUtils
• fixes: SHIRO-632 org.apache.felix:maven-bundle-plugin causing duplicate class problems between core and lang
• fixes: SHIRO-654 Multiple shiro OSGi bundles export the same packages
• is duplicated by: SHIRO-654 Multiple shiro OSGi bundles export the same packages
• links to: GitHub Pull Request #556