[
https://issues.apache.org/jira/browse/WICKET-6402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055342#comment-16055342
]
Christoph Läubrich commented on WICKET-6402:
--------------------------------------------
This looks fine (y) ... any idea why the files on central is missing the
information? I would suggest then to change
{code:java}
<Import-Package>org.apache.wicket*</Import-Package>
{code}
to
{code:java}
<Import-Package>org.apache.wicket*,*;resolution:=optional</Import-Package>
{code}
that would list all packages known in advance to be listed at least as
optional. In addition, as mentioned in WICKET-6401 required packages should be
marked as those in the indivual sub modules.
> OSGi-Manifest: wicket does not declare BSN
> ------------------------------------------
>
> Key: WICKET-6402
> URL: https://issues.apache.org/jira/browse/WICKET-6402
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 8.0.0-M6
> Reporter: Christoph Läubrich
>
> I try to upgrade a project to OSGi and encountered the issue that the current
> 8.0.0-M6 build seem to have no valid (OSGi-) Manifest
> [org.apache.wicket/wicket-util/8.0.0-M6] is not a valid bundle
> (bundleSymbolicName and bundleName are null)
> It seems that OSGi-Manifest information is lost on all jar files.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
