You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Christoph Läubrich (JIRA)" <ji...@apache.org> on 2017/10/04 06:58:00 UTC

[jira] [Closed] (WICKET-6402) OSGi-Manifest: wicket does not declare BSN

     [ https://issues.apache.org/jira/browse/WICKET-6402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christoph Läubrich closed WICKET-6402.
--------------------------------------

Manifest-Infos are now back in Wicket, Thanks for fixing this.

> 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
>            Assignee: Martin Grigorov
>             Fix For: 8.0.0-M7
>
>
> 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)