[
https://issues.apache.org/jira/browse/WICKET-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905382#comment-13905382
]
Martin Grigorov commented on WICKET-5511:
-----------------------------------------
Hi,
Wicket uses org.apache.felix:maven-bundle-plugin to manage OSGi stuff -
https://github.com/apache/wicket/blob/master/pom.xml#L853
wicket-core itself doesn't depend on CGLib so it doesn't need anything in its
MANIFEST.MF.
wicket-ioc (used by wicket-spring and wicket-guice) has dependency to CGLib.
Wicket 6 uses CGLib 2.2 and we cannot upgrade it because this may break
applications in production.
Wicket 7 uses CGLib 3.1.0.
Please provide a patch and we will consider it.
I see Christoph Läubrich complains that Wicket is not very friendly to OSGi -
none of the Wicket devs use OSGi so we don't know what problems there are.
> 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
>
> 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)
