Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 nicolas.lalevee@hibnet.org does not designate 216.86.168.182 as permitted
 sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: IvyDE & source variations (was: workaround to consume legacy Ivy
 modules)
From: =?iso-8859-1?Q?Nicolas_Lalev=E9e?= <nicolas.lalevee@hibnet.org>
In-Reply-To: 
 <CAEJc6MWUD4=2JNO3tBtBg0-M8=+ab9hit0p9utOY6uuFxfwgFA@mail.gmail.com>
Date: Tue, 18 Oct 2011 23:21:42 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9B13BD18-C7BA-44EA-BCEA-868E03B3272E@hibnet.org>
References: 
 <CAEJc6MWUD4=2JNO3tBtBg0-M8=+ab9hit0p9utOY6uuFxfwgFA@mail.gmail.com>
To: ivy-user@ant.apache.org


Le 18 oct. 2011 =E0 23:00, Mitch Gitman a =E9crit :

> Archie, thanks for the alternate approach. In case I still want to =
consider
> the original approach--if anyone else knows about the particular place =
in
> the code that I want to override, I'd love to hear.
> Correction. I believe I meant ${ivy.module.name}.
>=20
> Actually, this raises another question. How would I configure IvyDE to
> recognize foo.src.zip as the source for foo.jar?
>=20
> The "Sources suffixes" configuration has default values like:
> -source,-sources,-src
>=20
> I could change this value to the following:
> .src
>=20
> Still, the presumption seems to be that the extension is always .jar. =
It
> doesn't appear to accommodate .zip.

IvyDE doesn't care about the extension. It only compares the artifact =
names and artifacts types declared in the ivy.xml to find out which is =
source of the other.

Nicolas

> On Tue, Oct 18, 2011 at 11:00 AM, Archie Cobbs <archie@dellroad.org> =
wrote:
>=20
>> Just a thought... maybe instead you could write a resolver that =
contains a
>> nested, normal resolver, and applies a configured XLST stylesheet to =
all of
>> the ivy.xml files it downloads. Then what you want to do would be an =
easy
>> specific case.
>>=20
>> -Archie
>>=20
>> On Tue, Oct 18, 2011 at 12:27 PM, Mitch Gitman <mgitman@gmail.com> =
wrote:
>>=20
>>> It looks like I'm going to have to write a custom Ivy resolver. I =
want to
>>> consume modules that contain both a *.jar file and a *.src.zip file =
but
>>> where the ivy.xml doesn't specify any publications. Unfortunately, =
these
>>> modules are already published to a shared location and I can't just =
go
>> and
>>> blow them away. I understand that Ivy's default behavior is to treat =
the
>>> lack of a publications element as if it were the following:
>>> <publications>
>>>   <artifact name=3D"${module.name} />
>>> </publications>
>>>=20
>>> I forget if the property is module.name or something else. For the
>>> artifact
>>> element, the default type and ext of "jar" kick in.
>>>=20
>>> So I want to get the resolver to interpret this absence of =
publications
>>> instead as:
>>> <publications>
>>>   <artifact name=3D"${module.name} />
>>>   <artifact name=3D"${module.name} type=3D"zip" ext=3D"src.zip" />
>>> </publications>
>>>=20
>>> Would anyone happen to know the bit of resolver code that defaults =
the
>>> absence of publications so that I might override it?
>>>=20
>>=20
>>=20
>>=20
>> --
>> Archie L. Cobbs
>>=20