[
https://issues.apache.org/jira/browse/KARAF-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970576#comment-14970576
]
Freeman Fang commented on KARAF-4029:
-------------------------------------
Just notice that the AssemblyMojo default phase is PROCESS_RESOURCES, change it
to the PACKAGE so that it can refer the artifacts which is built by the
project itself locally like
{code}
<bundle>file://${project.basedir}/target/my.jar</bundle>
{code}
http://git-wip-us.apache.org/repos/asf/karaf/commit/de25865c
> 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
> Assignee: Freeman Fang
> Fix For: 4.0.3
>
>
> 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)
