Return-Path: X-Original-To: apmail-karaf-issues-archive@minotaur.apache.org Delivered-To: apmail-karaf-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2234E9308 for ; Thu, 18 Dec 2014 08:29:14 +0000 (UTC) Received: (qmail 40381 invoked by uid 500); 18 Dec 2014 08:29:14 -0000 Delivered-To: apmail-karaf-issues-archive@karaf.apache.org Received: (qmail 40351 invoked by uid 500); 18 Dec 2014 08:29:14 -0000 Mailing-List: contact issues-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 issues@karaf.apache.org Received: (qmail 40339 invoked by uid 99); 18 Dec 2014 08:29:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Dec 2014 08:29:13 +0000 Date: Thu, 18 Dec 2014 08:29:13 +0000 (UTC) From: "ArthurVaisse-Lesteven (JIRA)" To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (KARAF-3019) karaf-maven-plugin cannot handle all types of mvn urls MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KARAF-3019?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1425= 1375#comment-14251375 ]=20 ArthurVaisse-Lesteven edited comment on KARAF-3019 at 12/18/14 8:29 AM: ------------------------------------------------------------------------ Same problem with Camel 2.14.0/2.14.1. It's a little blocking as Karaf 2 is= also incompatible with Camel jetty 2.14.X, that enforce to upgrade Karaf t= o resolve the dependency conflict, and lead to another dependency conflict.= .. For now I cannot use Camel with karaf. was (Author: avl): Same problem with Camel 2.14.0/2.14.1. It's a little blocking as Karaf 2 is= also incompatible with Camel jetty 2.14.X, that enforce to upgrade Karaf t= o resolve the dependency conflict, and lead to another dependency conflict.= .. > karaf-maven-plugin cannot handle all types of mvn urls > ------------------------------------------------------ > > Key: KARAF-3019 > URL: https://issues.apache.org/jira/browse/KARAF-3019 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling > Affects Versions: 3.0.1 > Reporter: Kai Reichert > Assignee: Jean-Baptiste Onofr=C3=A9 > Priority: Minor > Labels: karaf-maven-plugin > Attachments: pom.xml > > > Some feature files list bundle references with maven repository urls. > For example the apache-camel-2.13.1 feature file contains: > {code:language=3Dxml} > > mvn:http://scriptengines.googlecode.com/svn/m2-repo/!com.goog= le.code.scriptengines/scriptengines-groovy/1.1 > =E2=80=A6 > {code} > There is no problem if you install such a feature from the karaf shell. I= think karaf uses the pax url handler internally (see [https://ops4j1.jira.= com/wiki/display/paxurl/Mvn+Protocol]) which handles repository urls, too. > But if you try to provision a new karaf distribution with maven and the {= {karaf-assembly}} packaging type, those urls cannot be resolved.=20 > Just try to include the bootFeature {{camel-script-groovy}} and you get t= he following error: > {noformat} > [ERROR] Failed to execute goal org.apache.karaf.tooling:karaf-maven-plugi= n:3.0.1:install-kars (default-install-kars) on project karaf3-distribution:= Couldn't resolve artifact mvn:http://scriptengines.googlecode.com/svn/m2-r= epo/!com.google.code.scriptengines/scriptengines-groovy/1.1: Could not find= artifact mvn:http:jar://scriptengines.googlecode.com/svn/m2-repo/!com.goog= le.code.scriptengines/scriptengines-groovy/1.1 in central (http://repo1.mav= en.org/maven2) -> [Help 1] > {noformat} > If the plugin cannot or even should not try to include the maven reposito= ry it could just ignore it in the resolution process (strip of the reposito= ry information from the url) and report the repo url as a warning. > The missing reference to the repository can then be included in the {{pom= .xml}} file.=20 > I removed the repository information in the feature file inside my local = maven repository for testing purposes, included the missing repository in t= he {{pom.xml}} file and the karaf-plugin was able to install the feature.= =20 -- This message was sent by Atlassian JIRA (v6.3.4#6332)