[
https://issues.apache.org/jira/browse/FELIX-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567809#comment-13567809
]
Richard S. Hall commented on FELIX-3845:
----------------------------------------
I've create a bundle with a long symbolic name with Maven Bundle Plugin and it
installs fine for me:
g! lb -s log
START LEVEL 1
ID|State |Level|Symbolic name
5|Installed |
1|org.apache.felix_org.apache.felix.log_org.apache.felix_org.apache.felix.log_org.apache.felix_org.apache.felix.log_org.apache.felix_org.apache.felix.log_org.apache.felix_org.apache.felix.log_org.apache.felix_org.apache.felix.log_org.apache.felix_org.apache.felix.log
(1.1.0.SNAPSHOT)
Tried against trunk and 4.0.0 and both worked. So, it sounds like there was
another issue in your manifest. If you cannot supply an example, then we'll
have to close this bug since there isn't enough information to resolve it.
> Bundles with long Bundle-SymbolicName would fail to be installed
> ----------------------------------------------------------------
>
> Key: FELIX-3845
> URL: https://issues.apache.org/jira/browse/FELIX-3845
> Project: Felix
> Issue Type: Bug
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: framework-4.2.0
>
>
> See fuse forum
> http://fusesource.com/forums/thread.jspa?threadID=4540&tstart=0
> The issue is that the person uses maven felix bundle plugin to bundle his
> project as an OSGi bundle. And if the name of the bundle becomes too long it
> gets wrapped in the MANIFEST.MF file and then Felix fails to install the
> bundle.
> More details in that link
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
