Return-Path: X-Original-To: apmail-ant-ivy-user-archive@www.apache.org Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9D760C154 for ; Fri, 18 May 2012 04:11:25 +0000 (UTC) Received: (qmail 42487 invoked by uid 500); 18 May 2012 04:11:25 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 42264 invoked by uid 500); 18 May 2012 04:11:21 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Delivered-To: moderator for ivy-user@ant.apache.org Received: (qmail 17218 invoked by uid 99); 17 May 2012 07:43:01 -0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of b.kapukaranov@gmail.com designates 209.85.210.45 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=I3K7NwVccRcW7urL/re+u5EnfF9wfLzD5KMGVcEcnHM=; b=cxXvTLNIfbWdmoCGQVkfDFHMqhxjBw+0rksGfKYAfNM/4BJmrWO0Sp+bbd12f3i3lk 8kAjW0fzvHZdUsDuD0Y1F9+11so5aTdkTRsKnDF5wLDNDGV87zbD0ZY000F8TIQJRl4p m97jiROIsXC/E6d0axxivWLFEBWTLxOvBx15sESafuvtiZfBvFBj80kkAMma6ss6phz2 S8cDRx9JPiiUw6DXrWtGs1+eVSoy3p348SihQzNMphipkUJfFokTOVI/rdOaf6eYYCWk aq5EpOpNcWnhvjbJBFgyOKKYPPqhX+slcq+9bsgmJFUIdMxwRaiDrPTICrBDiTcFmNYf 218Q== MIME-Version: 1.0 In-Reply-To: References: Date: Thu, 17 May 2012 10:42:31 +0300 Message-ID: Subject: Re: OSGi feature and ivy configurations From: Borislav Kapukaranov To: ivy-user@ant.apache.org Content-Type: multipart/alternative; boundary=e89a8ff1c4ce1269ce04c03694c2 --e89a8ff1c4ce1269ce04c03694c2 Content-Type: text/plain; charset=ISO-8859-1 >Ivy configurations are quite liberal, there is no predefined Ivy configuration. In Maven >there >are predefined configurations, that's why the rule you use work, as I guess you are >resolving >against a Maven repo. Then in the OSGi environment, there is some notion of >configuration, >but they completely different from the Maven ones [1]. >I guess that if you want a configuration in the OSGi world that would look like the >Maven >one "compile", it would be the configuration "default". > >Nicolas > >[1] http://ant.apache.org/ivy/history/latest-milestone/osgi/osgi-mapping.html Hi Nicolas I'm resolving against an Ivy repo, not a Maven one. But I control this Ivy repo and have published dependencies there with the configurations I need. However I don't control the p2 repo. If I use the 'default' configuration Ivy says it is unknown and can't be extended. I tries extending it to match my current configuration definitions. Is the default configuration always available for dependencies pulled from p2 repos? Best Regards Borislav On Wed, May 16, 2012 at 2:31 PM, Borislav Kapukaranov < b.kapukaranov@gmail.com> wrote: > Hello Ivy team, > > I have a question about pulled down from p2 repositories dependencies and > ivy configurations. > I have an established build with Ant and Ivy which is set up against Ivy > repositories. I have configured a set of ivy configurations for my > dependencies and have published them in the repositories with these > configurations. > > Now I saw the updatesite Ivy plugin and wanted to use it to pull > dependencies from p2 repositories. The trouble is these dependencies from > the p2 repositories came without Ivy configurations so I can't use them in > my current setup. I have a compile conf that makes sure I compile my > bundles only against dependencies marked with this compile configuration > therefore my p2 dependencies are ignored. > > I wanted to ask how are dependencies from p2 repos meant to work with Ivy > configurations? > > Best Regards, > Bobby > --e89a8ff1c4ce1269ce04c03694c2--