[
https://issues.apache.org/jira/browse/WICKET-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914061#comment-13914061
]
Andreas Pieber commented on WICKET-5511:
----------------------------------------
No problem on your behalf Martin. The "fault" is the "intelligent"
import-extension-mechanism of pax-wicket. Bascially it had been developed to
avoid that users need to add a patch of dependencies manually. But for a reason
I still need to nail down those imports also get appended to wicket itself,
which will lead to exactly the results you're encountering. I'll try to get
this fixed ASAP in pax-wicket.
> Import cglib dependencies in Manifest with version numbers
> ----------------------------------------------------------
>
> Key: WICKET-5511
> URL: https://issues.apache.org/jira/browse/WICKET-5511
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 6.7.0, 6.8.0, 6.9.0, 6.9.1, 6.10.0, 6.11.0, 6.12.0,
> 6.13.0, 7.0.0
> Reporter: Christoph Emmersberger
> Attachments: WICKET-5511.patch
>
>
> I have recently encountered an issue when using Wicket in an OSGI environment
> since the CGLIB version is not imported with the appropriate version number.
> A full description about that issue has been filed in the PAX-WICKET JIRA:
> https://ops4j1.jira.com/browse/PAXWICKET-455
> It would be really helpful to add the import statement with correct version
> number since this resolves the issue of OSGi bundle resolution.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
