Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Sun, 12 Feb 2012 07:53:57 +0000 (UTC)
From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28Commented=29_=28JIRA=29?=
 <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: 
 <1835118266.29221.1329033237540.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <514140431.24316.1328884859339.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (KARAF-1198) Add Maven repository metadata in
 the system repository
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/KARAF-1198?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1320=
6368#comment-13206368 ]=20

Jean-Baptiste Onofr=C3=A9 commented on KARAF-1198:
---------------------------------------------

Now, for all SNAPSHOT artifact, the create-kar includes a maven-metadata-lo=
cal.xml file. For the install-kar goal, it does the same for features SNAPS=
HOT.

TODO: refactoring of the MvnUrlUtil class into a MavenUtil class to include=
 the maven-metadata-local.xml file generation and lookup (to avoid code dup=
lication).
               =20
> Add Maven repository metadata in the system repository
> ------------------------------------------------------
>
>                 Key: KARAF-1198
>                 URL: https://issues.apache.org/jira/browse/KARAF-1198
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>    Affects Versions: 3.0.0
>            Reporter: Jean-Baptiste Onofr=C3=A9
>            Assignee: Jean-Baptiste Onofr=C3=A9
>             Fix For: 3.0.0
>
>
> Currently,all Snapshots artifacts in the system repository are overwritte=
n by the remote ones.
> It's due to the fact that we don't provide any repository metadata in the=
 system folder (no maven-metadata-local.xml for instance), and that's why a=
ether always download the snapshot from the remote repositories.
> In order to avoid this behavior, we have to add at least the maven-metada=
ta-local.xml file in the system repository.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira