[
https://issues.apache.org/activemq/browse/AMQ-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47766#action_47766
]
Jon Brisbin commented on AMQ-2018:
----------------------------------
I compiled 5.2 from source, omitting META-INF from the Import and
Export-Package manifest entries by editing the pom.xml file for activemq-core
and activemq-camel and changing it to a Private-Package let me copy it into the
pickup directory and the console is now listing it as deployed. I haven't tried
to use it yet, though.
> ActiveMQ not deployable in spec-compliant OSGi container
> --------------------------------------------------------
>
> Key: AMQ-2018
> URL: https://issues.apache.org/activemq/browse/AMQ-2018
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.2.0
> Environment: SpringSource dm Server 1.0
> Reporter: Jon Brisbin
>
> The SpringSource dm Server manifest parser is strictly OSGi spec-compliant
> and fails to deploy ActiveMQ jar files because the default manifest
> references a package name starting with META-INF. The xbean schema property
> files aren't even usable in dm server anyway, so there's no reason to include
> META-INF in the classpath. The OSGi spec prohibits this apparently.
> I've created an issue with SpringSource to have ActiveMQ 5.2 added to their
> bundle repository, but it would better if the standard AMQ jars were
> distributable as bundles in dm Server as easily as they are in a runtime like
> Apache Felix. This would just require patching the build to not include
> META-INF in either export or import package.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
