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 C07F810386 for ; Fri, 17 Jan 2014 13:46:31 +0000 (UTC) Received: (qmail 61130 invoked by uid 500); 17 Jan 2014 13:46:24 -0000 Delivered-To: apmail-karaf-issues-archive@karaf.apache.org Received: (qmail 60992 invoked by uid 500); 17 Jan 2014 13:46:21 -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 60946 invoked by uid 99); 17 Jan 2014 13:46:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jan 2014 13:46:20 +0000 Date: Fri, 17 Jan 2014 13:46:20 +0000 (UTC) From: "Robert Weiser (JIRA)" To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KARAF-1972) karaf-maven-plugin should respect scope MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KARAF-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874793#comment-13874793 ] Robert Weiser commented on KARAF-1972: -------------------------------------- Hey Christian, I have analyzed the issue and came to the following result: The {{mvn:org.apache.karaf.features:framework}} {{pom.xml}} has a bug concerning the dependency definitions ({{runtime}} should be switched {{provided}} ... due that the {{startup.properties}} had some artifact references prefixed with "wrap:" - neither the {{InstallKarMojo}} nor _Karaf_ (after fixing the {{InstallKarMojo}}) are able to handle the artifacts correctly. ...fixing the {{pom.xml}} of the {{mvn:org.apache.karaf.features:framework}} resolves the problem (please verify by comparing the {{feature.xml}} files generated before applying the patch and after applying the patch (and my notes above)) ...if you want me to I can provide you with a _GitHub_ _PullRequest_ (also incorporating your patch). Cheers, Robert > karaf-maven-plugin should respect scope > --------------------------------------- > > Key: KARAF-1972 > URL: https://issues.apache.org/jira/browse/KARAF-1972 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling > Affects Versions: 3.0.0.RC1 > Reporter: Andrei Pozolotin > Fix For: 3.0.1 > > Attachments: 0001-Fixing-the-scope-handling.patch, KARAF-1972.patch > > > PROBLEM: > currently, in project with dependencies such as these: > {code} > > org.osgi > org.osgi.core > provided > > > org.osgi > org.osgi.compendium > provided > > {code} > karaf-maven-plugin with invocation like this: > {code} > > > > org.apache.karaf.tooling > karaf-maven-plugin > 3.0.0-SNAPSHOT > > > generate-descriptor > package > > features-generate-descriptor > > > auto > 90 > ./target/${project.artifactId}-${project.version}-features.xml > > > > > > > {code} > will produce features.xml with entries: > {code} > mvn:org.osgi/org.osgi.core/4.3.0 > mvn:org.osgi/org.osgi.compendium/4.2.0 > {code} > which is not as expected. scope==provided should not show up there. > SOLUTION: > instead, karaf-maven-plugin should respect scope; > I suggest to add karaf-maven-plugin config parameters such as: > {code} > > compile > > {code} > or > {code} > > provided > runtime > test > > {code} > IMPACT: > current plugin behavior forces to create a separate maven > project to generate features.xml, since scope==provided > is in fact excluded from transitive dependencies in that case. -- This message was sent by Atlassian JIRA (v6.1.5#6160)