[
https://issues.apache.org/jira/browse/WICKET-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907302#comment-13907302
]
Christoph Emmersberger commented on WICKET-5511:
------------------------------------------------
I did some more in depth analysis at which point the dependency actually comes
into place
(1) Installing the wicket feature from PAX-WICKET results in no dependency to
CGLib as expected by the feature definition
{code}
<feature name="wicket" version="${wicket.dependency.version}">
<feature>http</feature>
<bundle>mvn:org.apache.wicket/wicket-util/${wicket.dependency.version}</bundle>
<bundle>mvn:org.apache.wicket/wicket-request/${wicket.dependency.version}</bundle>
<bundle>mvn:org.apache.wicket/wicket-core/${wicket.dependency.version}</bundle>
<bundle>mvn:org.apache.wicket/wicket-auth-roles/${wicket.dependency.version}</bundle>
<bundle>mvn:org.apache.wicket/wicket-extensions/${wicket.dependency.version}</bundle>
</feature>
{code}
(2) Installing the pax-wicket feature from PAX-WICKET results again in no
dependency from wicket-core to CGLib but has a dependency itself (see feature
definition below)
{code}
<feature name="pax-wicket" version="${project.version}">
<feature>wicket</feature>
<feature>eventadmin</feature>
<bundle>mvn:org.ops4j.base/ops4j-base/${ops4j.base.version}</bundle>
<bundle>mvn:org.apache.geronimo.specs/geronimo-atinject_1.0_spec/${geronimo.inject.version}</bundle>
<bundle>mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.aopalliance/${aopalliance.version}</bundle>
<bundle>mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.cglib/${cglib.version}</bundle>
<bundle>mvn:org.ops4j.pax.wicket/org.ops4j.pax.wicket.service/${project.version}</bundle>
</feature>
{code}
(3) Installing the WebApp via BundleActivator causes the dependency resolution
with the conflict. Since CGLib is now being imported by wicket-core I thought
that the initial issue might come from the dependency resolution and the
attached patch actually resolved my issue. However, I do not really understand
the entire dependency chain at that stage. [~pieber] might have an answer to
the root cause. One of my assumptions is, that the issue might be caused by the
dynamic package import:
{code}
DynamicImport-Package = *
{code}
> 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)
