Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Wed, 17 Feb 2016 16:11:18 +0000 (UTC)
From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28JIRA=29?= <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12933071.1453384262000.72688.1455725478559@Atlassian.JIRA>
In-Reply-To: <JIRA.12933071.1453384262000@Atlassian.JIRA>
References: <JIRA.12933071.1453384262000@Atlassian.JIRA>
 <JIRA.12933071.1453384262777@arcas>
Subject: [jira] [Updated] (KARAF-4288) karaf-maven-plugin doesn't pass
 custom settings.xml option onto pax-url-aether
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/KARAF-4288?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofr=C3=A9 updated KARAF-4288:
----------------------------------------
    Fix Version/s: 4.0.5
                   4.1.0

> karaf-maven-plugin doesn't pass custom settings.xml option onto pax-url-a=
ether
> -------------------------------------------------------------------------=
-----
>
>                 Key: KARAF-4288
>                 URL: https://issues.apache.org/jira/browse/KARAF-4288
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-tooling
>    Affects Versions: 4.0.4
>            Reporter: Stuart McCulloch
>            Assignee: Jean-Baptiste Onofr=C3=A9
>             Fix For: 4.1.0, 4.0.5
>
>         Attachments: KARAF-4288.patch
>
>
> When adding features to a custom distribution karaf-maven-plugin uses pax=
-url-aether to fetch artifacts which don't yet exist in the local maven rep=
ository.
> pax-url-aether has logic to discover the local repository and settings.xm=
l file, but this relies on defaults plus a few heuristics. If a Maven build=
 uses a custom settings.xml file which contains auth details, ie. when runn=
ing on CI, then this is not picked up by pax-url-aether and it cannot fetch=
 down additional content.
> The current user settings file is accessible from the MavenSession which =
is already available in Karaf's MojoSupport:
>    MavenSession->getRequest->getUserSettingsFile
> All that needs to be done is to pass this path to pax-url-aether by setti=
ng the "org.ops4j.pax.url.mvn.settings" system property. Note the custom us=
er settings file may be null or may not exist, in which case pax-url-aether=
 should use the global settings. Since it already has code to discover the =
global settings using known locations we don't need to pass this on, so we =
just avoid setting "org.ops4j.pax.url.mvn.settings" in this case.
> (I'll attach a patch that implements this suggested solution)


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)