Return-Path: 
 <dev-return-6809-apmail-felix-dev-archive=felix.apache.org@felix.apache.org>
Delivered-To: apmail-felix-dev-archive@www.apache.org
Received: (qmail 6526 invoked from network); 6 Aug 2007 13:34:20 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 6 Aug 2007 13:34:20 -0000
Received: (qmail 61531 invoked by uid 500); 6 Aug 2007 13:34:20 -0000
Delivered-To: apmail-felix-dev-archive@felix.apache.org
Received: (qmail 61319 invoked by uid 500); 6 Aug 2007 13:34:19 -0000
Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@felix.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@felix.apache.org>
List-Post: <mailto:dev@felix.apache.org>
List-Id: <dev.felix.apache.org>
Reply-To: dev@felix.apache.org
Delivered-To: mailing list dev@felix.apache.org
Received: (qmail 61310 invoked by uid 99); 6 Aug 2007 13:34:19 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Aug 2007 06:34:19 -0700
X-ASF-Spam-Status: No, hits=-100.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Aug 2007 13:34:19 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 4C9BF71413F
	for <dev@felix.apache.org>; Mon,  6 Aug 2007 06:33:59 -0700 (PDT)
Message-ID: <14767224.1186407239300.JavaMail.jira@brutus>
Date: Mon, 6 Aug 2007 06:33:59 -0700 (PDT)
From: "Stuart McCulloch (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Commented: (FELIX-308) Add support for embedding dependency
 JAR files to bundle plugin
In-Reply-To: <15268851.1182343345859.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/FELIX-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517927 ] 

Stuart McCulloch commented on FELIX-308:
----------------------------------------

BTW, if you want to add a dependency to your pom (ie. for embedding purposes) but don't want
users of your bundle picking up that dependency then you can mark it as optional, for example
updating the framework/pom.xml to use:

    <dependency>
      <groupId>${pom.groupId}</groupId>
      <artifactId>org.osgi.core</artifactId>
      <version>1.1.0-SNAPSHOT</version>
      <optional>true</optional>                          //   <--- ie. not required by users of this artifact
    </dependency>

would (hopefully) solve Craig's question about bundle dependencies (FWIW, it works in my tests)

> Add support for embedding dependency JAR files to bundle plugin
> ---------------------------------------------------------------
>
>                 Key: FELIX-308
>                 URL: https://issues.apache.org/jira/browse/FELIX-308
>             Project: Felix
>          Issue Type: New Feature
>          Components: Maven Bundle Plugin
>            Reporter: Richard S. Hall
>         Attachments: FELIX_308_EMBED_SUPPORT_20070803.txt, FELIX_308_EMBED_SUPPORT_20070806.txt
>
>
> The following is a proposal for how to support embedding dependency JAR files in the bundle plugin. The general approach is a slightly modified version of a proposal by Peter Kriens. The idea is to add a mechanism to deal with embedding JARs that is very similar to how the old maven plugin worked, but doing it in a slightly more generic way than the old plugin by adding the following instruction:
>     embed-dependency        ::= clause ( ',' clause ) *
>     clause                  ::= MATCH ( ';' attr '=' MATCH )
>     attr                    ::= 'groupId' | 'artifactId' | 'version' | 'scope'
>     MATCH                   ::= <globbed regular expressions>
> This instruction would be used to match the specified Maven dependencies for embedding. Any matching dependency would have its JAR file embedded onto the resulting bundle JAR file and it would be appended to the Bundle-ClassPath header after ".".
> This would allow people to easily achieve the same behavior as the old plugin by simply doing:
>     <embed-dependency>*;scope=compile|runtime</embed-dependency>
> Thus, this instruction would automatically embed any maven dependencies that were of scope "compile" or "runtime" and append them to the bundle class path.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.