Return-Path: X-Original-To: apmail-karaf-dev-archive@minotaur.apache.org Delivered-To: apmail-karaf-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 61EAB1831A for ; Tue, 24 Nov 2015 17:39:06 +0000 (UTC) Received: (qmail 88422 invoked by uid 500); 24 Nov 2015 17:39:06 -0000 Delivered-To: apmail-karaf-dev-archive@karaf.apache.org Received: (qmail 88386 invoked by uid 500); 24 Nov 2015 17:39:06 -0000 Mailing-List: contact dev-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list dev@karaf.apache.org Delivered-To: moderator for dev@karaf.apache.org Received: (qmail 87687 invoked by uid 99); 24 Nov 2015 17:38:38 -0000 From: maggu2810 To: dev@karaf.apache.org Reply-To: dev@karaf.apache.org References: In-Reply-To: Subject: [GitHub] karaf pull request: KAR Mojo: fix metadata generation of artifacts Content-Type: text/plain Message-Id: <20151124173838.8C9D0E009E@git1-us-west.apache.org> Date: Tue, 24 Nov 2015 17:38:38 +0000 (UTC) GitHub user maggu2810 reopened a pull request: https://github.com/apache/karaf/pull/102 KAR Mojo: fix metadata generation of artifacts Problem description: * use the kmp to generate a kar that contains snapshot version * use the kmp to generate a custom distribution that fills the local repository of the distribution with the content of that kar * try to install the snapshot artifact (not using any other repository then the system directory * if your snapshots has been timestamped and a maven metadata XML does not exist on KAR creation the installation of the artifact will fail The KAR Mojo contains a workaround to use the base version of a snapshot instead of a timestamped one because it does not work in startup.properties. The metadata that is used for a snapshot artifact is generated (if not present) using the timestamped version. Also if there exists already a metadata, we can not use them without further checking for the version... Let's move the version fix in front of the metadata generation and generate the metadata for every snapshot. Signed-off-by: Markus Rathgeb You can merge this pull request into a Git repository by running: $ git pull https://github.com/maggu2810/karaf kmp-kar-snapshots Alternatively you can review and apply these changes as the patch at: https://github.com/apache/karaf/pull/102.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #102 ---- commit ed512fc72181f3ab3a9437dc1bb727c1465940c1 Author: Markus Rathgeb Date: 2015-11-24T16:28:14Z KAR Mojo: fix metadata generation of artifacts Problem description: * use the kmp to generate a kar that contains snapshot version * use the kmp to generate a custom distribution that fills the local repository of the distribution with the content of that kar * try to install the snapshot artifact (not using any other repository then the system directory * if your snapshots has been timestamped and a maven metadata XML does not exist on KAR creation the installation of the artifact will fail The KAR Mojo contains a workaround to use the base version of a snapshot instead of a timestamped one because it does not work in startup.properties. The metadata that is used for a snapshot artifact is generated (if not present) using the timestamped version. Also if there exists already a metadata, we can not use them without further checking for the version... Let's move the version fix in front of the metadata generation and generate the metadata for every snapshot. Signed-off-by: Markus Rathgeb ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---