You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2017/06/19 19:31:00 UTC
[jira] [Comment Edited] (WICKET-6402) OSGi-Manifest: wicket does
not declare BSN
[ https://issues.apache.org/jira/browse/WICKET-6402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16054636#comment-16054636 ]
Martin Grigorov edited comment on WICKET-6402 at 6/19/17 7:30 PM:
------------------------------------------------------------------
wicket-util's META-INF/MANIFEST.MF contains "Bundle-SymbolicName: org.apache.wicket.util"
hat exactly is wrong with it ? And how to fix it ?
No one from us uses OSGi, so please suggest what changes have to be applied to improve the OSGi experience!
was (Author: mgrigorov):
wicket-util's META-INF/MANIFEST.MF contains "Bundle-SymbolicName: org.apache.wicket.util"
hat exactly is wrong with it ? And how to fix it ?
No one from us use OSGi, so please suggest what changes have to be applied to improve the OSGi experience!
> 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)