[
http://issues.ops4j.org/jira/browse/PAXLOGGING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11445
]
Jens Borrmann commented on PAXLOGGING-31:
-----------------------------------------
Spring Security 2.0.3 depends on jasic 3.1.3, which is not yet (publicly)
available as an OSGi bundle. So unfortunately a quick and reliable test is not
possible.
> Pax Logging unusable with SpringSecurity 2.0.2.A
> ------------------------------------------------
>
> Key: PAXLOGGING-31
> URL: http://issues.ops4j.org/jira/browse/PAXLOGGING-31
> Project: Pax Logging
> Issue Type: Bug
> Affects Versions: 1.1.1
> Reporter: Jens Borrmann
> Assignee: Niclas Hedhman
>
> Spring Security 2.0.2.A requires log4j version 1.2.15. Therefore it is not
> interoperable with pax logging.
> Our first hack was just modifying the exported version in the manifest of the
> api bundle, which did not work since there are some new classes in log4j.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
