[
https://issues.apache.org/jira/browse/WICKET-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913047#comment-13913047
]
Christoph Emmersberger edited comment on WICKET-5511 at 2/26/14 3:52 PM:
-------------------------------------------------------------------------
Hi [~martin-g],
I guess, the issue is rather related to Wicket and exists already for quite a
long time.
Please find a very good explanation on what needs to be changed in here by
[~hwellmann]: https://code.google.com/p/osgi-enterprise/wiki/WicketAndOsgi
Best,
Christoph
was (Author: cemmersb):
Hi [~martin-g],
I guess, the issue is rather related to Wicket and exists already for quite a
long time.
Please find a very good explanation on what needs to be changed in this
explanation by [~hwellmann]:
https://code.google.com/p/osgi-enterprise/wiki/WicketAndOsgi
Best,
Christoph
> 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)
