[
https://issues.apache.org/jira/browse/SHIRO-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Les Hazlewood resolved SHIRO-390.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.3.0
1.2.2
I resolved this by fixing the Import-Package statement in the web module's
pom.xml (1.2.x branch and trunk):
<Import-Package>
org.apache.shiro*;version="${shiro.osgi.importRange}",
javax.servlet.jsp*;resolution:=optional,
*
</Import-Package>
If you see any problems, please let us know.
(JSP support will likely be a separate module in Shiro 2.x). Thanks for the
issue!
> OSGi Import for JSP (javax.servlet.jsp) should be declared optional
> -------------------------------------------------------------------
>
> Key: SHIRO-390
> URL: https://issues.apache.org/jira/browse/SHIRO-390
> Project: Shiro
> Issue Type: Bug
> Affects Versions: 1.2.1
> Environment: Eclipse Equinox
> Reporter: Jan Stamer
> Priority: Minor
> Fix For: 1.2.2, 1.3.0
>
> Attachments: MANIFEST.MF
>
>
> I am using Shiro with OSGi (Equinox) in a web application. Yet I do not use
> JSP pages. Therefore I use the shiro web bundle without requiring the package
> *.tags.
> So actually I do not need the jsp bundles as I don't use the tags. To avoid
> having to include the jsp bundles the import should be declared optional. I
> hacked up the manifest to suit my needs and it works just fine.
> Another option would be to create a separate package like "shiro.web.jsp"
> which contains the code for using shiro with JSPs.
--
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
