[
https://issues.apache.org/jira/browse/KARAF-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14966219#comment-14966219
]
Dhiraj Bokde commented on KARAF-4029:
-------------------------------------
Hi [~ffang], see the karaf project at
https://github.com/fabric8io/ipaas-quickstarts/tree/master/quickstart/karaf/camel-log.
It basically has to run the *assembly* goal in *install* phase, and
maven-install-plugin has to be listed before karaf-maven-plugin to allow the
project's bundle to be installed in the OBR before the *assembly* goal.
Ideally, *assembly* should be able to add the project bundle to the karaf
assembly during the default *package* phase after the bundle is packaged in
target/ dir, along with other resources such as a broker.xml to be added to the
assembly.
> Karaf maven plugin assembly goal requires project artifact to be installed
> first
> --------------------------------------------------------------------------------
>
> Key: KARAF-4029
> URL: https://issues.apache.org/jira/browse/KARAF-4029
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
> Affects Versions: 4.0.1
> Reporter: Dhiraj Bokde
>
> The karaf maven plugin `assemble` goal is designed to run in the `package`
> phase, and the `archive` goal in the `install` phase.
> When using the plugin in a project that also packages the app as an OSGi
> bundle to be installed in the custom distro, it can't locate the app bundle,
> since it's only been packaged and not installed in the maven repo.
> The plugin should be modified, so that a flag can be used to install the
> application bundle in the custom distro, without having to install it in
> maven repo and local obr.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
