Return-Path: Delivered-To: apmail-felix-dev-archive@www.apache.org Received: (qmail 26733 invoked from network); 15 Apr 2009 08:36:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Apr 2009 08:36:38 -0000 Received: (qmail 59276 invoked by uid 500); 15 Apr 2009 08:36:36 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 59143 invoked by uid 500); 15 Apr 2009 08:36:36 -0000 Mailing-List: contact dev-help@felix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@felix.apache.org Delivered-To: mailing list dev@felix.apache.org Received: (qmail 59025 invoked by uid 99); 15 Apr 2009 08:36:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Apr 2009 08:36:35 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Apr 2009 08:36:35 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id E01FD234C003 for ; Wed, 15 Apr 2009 01:36:14 -0700 (PDT) Message-ID: <1630516122.1239784574906.JavaMail.jira@brutus> Date: Wed, 15 Apr 2009 01:36:14 -0700 (PDT) From: "Thomas Diesler (JIRA)" To: dev@felix.apache.org Subject: [jira] Created: (FELIX-1039) Inconsistency packaging vs. type MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Inconsistency packaging vs. type -------------------------------- Key: FELIX-1039 URL: https://issues.apache.org/jira/browse/FELIX-1039 Project: Felix Issue Type: Bug Components: Maven Bundle Plugin Affects Versions: maven-bundle-plugin-2.0.0 Environment: Maven-2.1.0 Reporter: Thomas Diesler The Maven Bundle Plugin uses bundle Scenario #1 - dependency uses type=bundle org.jboss.osgi jboss-osgi-common ${version} bundle with type=bundle the the dependency is resolved correctly from the the build reactor. 'mvn package' succeeds. Note, the artefact is not yet in the local repository. Scenario #2 - dependency uses unspecified type org.jboss.osgi jboss-osgi-common ${version} 'mvn package' fails if the artefact is not yet in the local repository 'mvn install' succeeds Scenario #3 - the dependent bundle is not part of the reactor build 'mvn package' or 'mvn install' will always fail when the dependency is declared with type=bundle Fazit: If you declare the dependency with type=bundle, the dependency cannot be resolved from the repository. If you don't declare a dependency type, the dependency can only be resolved from the repository. 'mvn package' will fail if the dependency is not in the repository. Workaround: Don't use type=bundle in the dependency and always install. i.e. 'mvn install' -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.