Karaf maven plugin package vs install

[Raman Gupta <ro...@gmail.com>]

My project builds assembly modules and then in another module runs the
karaf-maven-plugin.

This works fine when using the "install" goal. However, when using the
"package" goal it does not: package does not install the assemblies
into the local maven repo, and karaf-maven-plugin fails with a
resolution error (or even worse, it works but pulls in an older
snapshot version of the features from ~/.m2).

Should the karaf-maven-plugin be looking at the reactor artifacts
(target/whatever of the dependent modules) rather than the the
installed artifacts (.m2/repository/whatever of the dependent modules)?

Regards,
Raman

Re: Karaf maven plugin package vs install

[Markus Rathgeb <ma...@gmail.com>]

I ran into the same problem some time ago using the release plugin.
To use the release plugin the preparation goal have to be set to
execute the "install" phase.

2016-03-11 20:29 GMT+01:00 Raman Gupta <ro...@gmail.com>:
> My project builds assembly modules and then in another module runs the
> karaf-maven-plugin.
>
> This works fine when using the "install" goal. However, when using the
> "package" goal it does not: package does not install the assemblies
> into the local maven repo, and karaf-maven-plugin fails with a
> resolution error (or even worse, it works but pulls in an older
> snapshot version of the features from ~/.m2).
>
> Should the karaf-maven-plugin be looking at the reactor artifacts
> (target/whatever of the dependent modules) rather than the the
> installed artifacts (.m2/repository/whatever of the dependent modules)?
>
> Regards,
> Raman