Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (nike.apache.org: domain of
 prvs=5679bf37c6=shawn.castrianni@halliburton.com designates 34.254.247.11 as
 permitted sender)
From: Shawn Castrianni <Shawn.Castrianni@halliburton.com>
To: "ivy-user@ant.apache.org" <ivy-user@ant.apache.org>
Date: Thu, 4 Mar 2010 15:57:01 -0600
Subject: RE: advanced ivy retrieve syntax
Thread-Topic: advanced ivy retrieve syntax
Thread-Index: Acq74rKk4Rhq0ETRSvayyZlOJouSKgAApDjQ
Message-ID: 
 <FC28BDC007C04141969BD4EAAFEC60F128673238A3@NP1EXMB012.corp.halliburton.com>
References: <27750721.post@talk.nabble.com> <27784758.post@talk.nabble.com>
 <27784895.post@talk.nabble.com> <27786891.post@talk.nabble.com>
In-Reply-To: <27786891.post@talk.nabble.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

If I am understanding your question correctly, this is already supported by=
 IVY with the addition of configuration intersection.  I requested this fea=
ture last year and Xavier added it last year.  You specify multiple configu=
rations for each "dimension" or "axis" and you can intersect those "dimensi=
ons" to only get the artifact that belong in both of the intersected config=
urations.

If you search the user forum with nabble or something and look for configur=
ation intersection, you can probably find my posts.  The IVY documentation =
has information on this feature.

---
Shawn Castrianni

-----Original Message-----
From: dek577 [mailto:dek577@gmail.com]=20
Sent: Thursday, March 04, 2010 3:35 PM
To: ivy-user@ant.apache.org
Subject: Re: advanced ivy retrieve syntax


The following is also on my wishlist. Declare an artifact such as:

<artifact name=3D"libzlib" type=3D"lib" ext=3D"lib" conf=3D"compile,release"
e:linkage=3D"static"/>
<artifact name=3D"zlib" type=3D"lib" ext=3D"lib" conf=3D"compile,release"
e:linkage=3D"dynamic"/>

and be able to do a resolve or a cachefileset with syntax similar to the
following:

<ivy:cachefileset setid=3D"library.fileset" type=3D"lib" conf=3D"compile">
 <filter linkage=3D"static"/>
</cachefileset>


Juha Ranta wrote:
>=20
>=20
>=20
> Juha Ranta wrote:
>>=20
>>=20
>>=20
>> dek577 wrote:
>>>=20
>>> Does the ivy:retrieve ant task support more advanced configuration
>>> specifications similar to the configuration mappings, intersections, and
>>> negations described here:
>>> http://ant.apache.org/ivy/history/latest-milestone/ivyfile/dependency.h=
tml
>>>=20
>>> I'm interested in doing a retrieve similar to the following:
>>>=20
>>> <task name=3D"retrieve">
>>> <ivy:retriive conf=3D"runtime+release"
>>> pattern=3D"${staging.dir}/[module]-[revision]/[artifact](.[ext])"/>
>>> </task>
>>>=20
>>> that grabs a subset of the dependencies.
>>>=20
>>=20
>> I've run to a similar need with my confs. The problem seems to arise when
>> I have confs in two or more "dimensions". For instance, while
>> constructing my server platform, I need to put some jars in classpath,
>> other jars as Bea shared libraries, others in mbeantypes directory, etc.
>> Fine, I can use confs to tell whether I want to put the jar in classpath
>> or the mbeantypes directory. However, at the same time, I may need to
>> insert some jars only in the developer's classpath and some only in the
>> runtime classpath.=20
>>=20
>> Thus, it would be useful to be able to retrieve, say,
>> "developer+mbeantypes".=20
>>=20
>> I looked at the current options in Ivy but didn't find anything that
>> worked well in this situation.
>>=20
>> Juha Ranta
>>=20
>=20
> Now that I thought of it, I'd like it if I could do something like this:
>=20
> <dependency org=3D"xxx" module=3D"dom4j" conf=3D"runtime->default"
> e:localdir=3D"mbeantypes"/>
>=20
> and then use the localdir or whatever extra attribute I defined in the
> dependency in my retrieve task.=20
>=20
> I don't think it's always a good idea to expect that a single jar should
> know whether it is placed in war, ear, APP-INF/lib, classpath, as a BEA
> shared library, in the mbeantypes directory, in the classpath, or
> whatever, and publish all the confs that the user may need.=20
>=20
>=20
>=20

--=20
View this message in context: http://old.nabble.com/advanced-ivy-retrieve-s=
yntax-tp27750721p27786891.html
Sent from the ivy-user mailing list archive at Nabble.com.

----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and pri=
vileged information for the sole use of the intended recipient.  Any review=
, use, distribution, or disclosure by others is strictly prohibited.  If yo=
u are not the intended recipient (or authorized to receive information for =
the intended recipient), please contact the sender by reply e-mail and dele=
te all copies of this message.