[
https://issues.apache.org/activemq/browse/SM-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tammo van Lessen reopened SM-1267:
----------------------------------
Bruce, sorry for reopening this again but I missed another spot in my patch.
It's better to include these jar also in the jbi.xml ;)
I've created an additional path which fixes the issue completely (hopefully).
IMO its sufficient to fix this only for the component-class path and leave the
bootstrap-class path as it is, but I'm not really sure. So it's up to you to
decide ;)
Thanks for your fast response and for applying the patch.
Cheers,
Tammo
> maven-jbi-plugin refuses to include jbi-component jars into SE packages
> -----------------------------------------------------------------------
>
> Key: SM-1267
> URL: https://issues.apache.org/activemq/browse/SM-1267
> Project: ServiceMix
> Issue Type: Bug
> Components: tooling
> Affects Versions: 3.2.1
> Environment: winxp, mvn 2.0.8
> Reporter: Tammo van Lessen
> Assignee: Bruce Snyder
> Fix For: 3.2.2, 3.3
>
> Attachments: SM-wrong-se-packaging-part2.diff,
> SM-wrong-se-packaging.diff
>
>
> I need to include servicemix-jsr181-x.x.x.jar as a dependency in my SE.
> Simply adding it as a dependency to the pom does not help at all, transitive
> dependencies are included in the install package but not the component jar
> itself. Even changing the dependency scope did not help.
> I tracked it down to GenerateComponentDescriptorMojo and
> GenerateComponentMojo which include only dependencies that have been packaged
> as "jar" or as "bundle" and thereby ignore the jar above as its packaged as
> 'jbi-component'.
> Please find attached a patch which fixes this issue for 'jbi-component's,
> this issue may apply for other packaging types to, so I suggest to change the
> mechanism from white listing to black listing.
> Cheers,
> Tammo
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
