Question about artifact resolving in karaf-maven-plugin

[Achim Finke <ac...@googlemail.com>]

Hi,

when investigating the reason for KARAF-3347
<https://issues.apache.org/jira/browse/KARAF-3347>  I stumbled across how
Maven artifacts are resolved in karaf-maven-plugin. In most cases artifacts
are resolved using org.apache.maven.artifact.resolver.ArtifactResolver
(deprecated since Maven 3) although Grzegorz
<https://github.com/apache/karaf/pull/24> commited a Maven 3 aware solution
using Aether <https://github.com/apache/karaf/pull/24> early this year. Are
there any reasons why the resolving is not done via this approach all over
the project? A first shot on my local fork was quite successfull using the
provided DependencyHelper.

Greetings,
Achim

Re: Question about artifact resolving in karaf-maven-plugin

[Jean-Baptiste Onofré <jb...@nanthrax.net>]

Hi Achim,

I worked on the generate and install goals of the karaf-maven-plugin but 
not yet on the add-features-to-repo.

The generate and install goals already use Aether and the new dependency 
resolver.

I will review all goals to update to Aether resolution everywhere.

Regards
JB

On 11/05/2014 02:58 PM, Achim Finke wrote:
> Hi,
>
> when investigating the reason for KARAF-3347
> <https://issues.apache.org/jira/browse/KARAF-3347>  I stumbled across how
> Maven artifacts are resolved in karaf-maven-plugin. In most cases artifacts
> are resolved using org.apache.maven.artifact.resolver.ArtifactResolver
> (deprecated since Maven 3) although Grzegorz
> <https://github.com/apache/karaf/pull/24> commited a Maven 3 aware solution
> using Aether <https://github.com/apache/karaf/pull/24> early this year. Are
> there any reasons why the resolving is not done via this approach all over
> the project? A first shot on my local fork was quite successfull using the
> provided DependencyHelper.
>
> Greetings,
> Achim
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com