Return-Path: 
 <ivy-user-return-3966-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: (qmail 90089 invoked from network); 23 Sep 2008 22:22:05 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 23 Sep 2008 22:22:05 -0000
Received: (qmail 99041 invoked by uid 500); 23 Sep 2008 22:22:02 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 99025 invoked by uid 500); 23 Sep 2008 22:22:02 -0000
Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@ant.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@ant.apache.org>
List-Post: <mailto:ivy-user@ant.apache.org>
List-Id: <ivy-user.ant.apache.org>
Reply-To: ivy-user@ant.apache.org
Delivered-To: mailing list ivy-user@ant.apache.org
Received: (qmail 99014 invoked by uid 99); 23 Sep 2008 22:22:02 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Sep 2008 15:22:02 -0700
X-ASF-Spam-Status: No, hits=0.2 required=10.0
	tests=SPF_PASS,WHOIS_MYPRIVREG
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: local policy)
Received: from [69.36.245.73] (HELO bachelor.silverspringnet.com)
 (69.36.245.73)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Sep 2008 22:21:01 +0000
Received: from SILVERSTAR.silverspringnet.com ([10.200.1.12])
	by bachelor.silverspringnet.com (8.14.1/8.13.8) with ESMTP id m8NMLoaX025962
	for <ivy-user@ant.apache.org>; Tue, 23 Sep 2008 15:21:50 -0700 (PDT)
Received: from bdamm-workhorse.local ([10.90.129.69]) by
 SILVERSTAR.silverspringnet.com with Microsoft SMTPSVC(6.0.3790.3959);
	 Tue, 23 Sep 2008 15:20:33 -0700
From: Benjamin Damm <bdamm@silverspringnet.com>
Organization: Silver Spring Networks
To: ivy-user@ant.apache.org
Subject: Re: Depending on bouncycastle
Date: Tue, 23 Sep 2008 15:20:52 -0700
User-Agent: KMail/1.9.9
References: <200809231038.42094.bdamm@silverspringnet.com>
 <48D95C86.1010500@pagesmiths.com>
In-Reply-To: <48D95C86.1010500@pagesmiths.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200809231520.52169.bdamm@silverspringnet.com>
X-OriginalArrivalTime: 23 Sep 2008 22:20:33.0907 (UTC)
 FILETIME=[98B07430:01C91DCA]
X-Virus-Checked: Checked by ClamAV on apache.org

Your suggestion got me started, but I veered off into linking the ant properties to the file names.  That got me thinking; why do I even need the 
classifier?  Can't this just be done with properties alone?  So here's what I ended up with:

${repository.dir}/bouncycastle/140/ivy.xml:
<?xml version="1.0" encoding="UTF-8"?>
<ivy-module version="2.0">
    <info organisation="bouncycastle" module="bouncycastle" revision="140" />
    <publications>
        <artifact name="bcprov-${base.jdk.version}" type="jar" ext="jar" conf="default"/>
    </publications>
</ivy-module>

${ivysettings.dir}/ivysettings.xml:
...
        <filesystem name="ivycontrib">
            <artifact pattern="${ivycontrib.dir}/[module]/[revision]/[artifact]-[revision].[ext]" />
            <artifact pattern="${ivycontrib.dir}/[module]/[revision]/[artifact]-${base.jdk.version}-[revision].[ext]" />
            <ivy pattern="${ivycontrib.dir}/[module]/[revision]/ivy.xml" />
        </filesystem>
...

Which actually sort of works... except that both jars end up in the classpath.  This is strange.  So my classpath ends up looking like:
...:${ivy.cache.dir}/bouncycastle/bouncycastle/jars/bcprov-jdk15-140.jar:${ivy.cache.dir}bouncycastle/bouncycastle/jars/bcprov-jdk16-140.jar:...

Creating a different module doesn't quite solve the problem, because somehow I have to still select the right one.  Unless, I suppose, I could put a 
variable such as ${ivy.jdk.version} into my project's ivy.xml.

-Ben



On Tuesday 23 September 2008 02:15:50 pm Jim White wrote:
> I think it is best to think of those as two different modules (because,
> after all, they are).
>
> Maven added the "classifier" field to deal with that (the issue being
> that folks don't want to use different module names for JDK version
> dependency) and Ivy supports that now too.
>
> http://www.nabble.com/Re%3A-Classifier-frustration-p16740537.html
>
> https://issues.apache.org/jira/browse/IVY-803
>
> You can define an Ant property in your build to supply the right "jdk15"
> or "jdk16" value for the classifier.
>
> Jim
>
> Benjamin Damm wrote:
> > Hi ivy users,
> >
> >   I've started to integrate ivy with our build process, and it is
> > fantastic. There's something I'm having trouble with, though, and that's
> > understanding how to depend on bouncycastle.  It comes in at least two
> > flavors; one for jdk15 and one for jdk16.  We have developers on both and
> > previously had our build scripts pick the right one depending on what
> > version of java ant was run under.
> >
> > How to do this with ivy?  Ivy doesn't appear to have any conditional
> > dependency abilities, so I can't choose one artifact or another based on
> > what version of java I'm running.  I suppose I could generate an
> > ivy.xml "just-in-time" but I'd prefer not to.  Anyone surpassed this
> > little hurdle?
> >
> > Thank you,
> > -Ben



-- 
Benjamin Damm
Silver Spring Networks
650-298-4200 x201