[
https://issues.apache.org/jira/browse/KARAF-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14966388#comment-14966388
]
Freeman Fang commented on KARAF-4029:
-------------------------------------
Hi Dhiraj,
You needn't explicitly add the maven-install-plugin, just specify the assembly
phase as "install" you should be all set.
Or you can keep the assembly goal phase as "package" and refer the
target/quickstart-karaf-camel-log.jar with file URL like
{code}
<startupBundles>
-
<bundle>mvn:${project.groupId}/${project.artifactId}/${project.version}</bundle>
+
<bundle>file://${project.basedir}/target/quickstart-karaf-camel-log.jar</bundle>
</startupBundles>
{code}
then the karaf-maven-plugin won't try to download it through maven and just use
the local one and generate the startup.properties like
{code}
reference\:file\:generated/file_Users_ffang_project_ipaas-quickstarts_quickstart_karaf_camel-log_target_quickstart-karaf-camel-log.jar
= 50
{code}
accordingly, note the file\:generated/..., it's not the maven pattern.
Freeman
> 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)
