Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
MIME-Version: 1.0
In-Reply-To: <SN1PR0601MB16305CD8618D1A899DE7B77FB8230@SN1PR0601MB1630.namprd06.prod.outlook.com>
References: <SN1PR0601MB16305CD8618D1A899DE7B77FB8230@SN1PR0601MB1630.namprd06.prod.outlook.com>
From: Marc De Boeck <mdeboec@gmail.com>
Date: Wed, 29 Jun 2016 22:16:25 +0200
Message-ID: <CAPMYPma2chNorK=C_zr3Rz85AZ3CCR2Kutgf9DUcTkN7YT4tqA@mail.gmail.com>
Subject: Re: Packaging attribute, unpack location
To: ivy-user@ant.apache.org
Content-Type: multipart/alternative; boundary=94eb2c08eeb0b74b750536706e35
archived-at: Wed, 29 Jun 2016 20:16:57 -0000

--94eb2c08eeb0b74b750536706e35
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Can you tell us the cache pattern that you have configured ?
Maybe you can also try to retrieve the same artifacts but with a module
descriptor (ivy-file) where the packaging attribute is not set.
This way, you could find out if it is related to the packaging attribute,
or related to something else.

Regards,
Marc

2016-06-29 21:22 GMT+02:00 Jeremie Faucher-Goulet <
Jeremie.Faucher-Goulet@trilliantinc.com>:

> Hello,
>
>
>
> I=E2=80=99m encountering an issue where, when using a different configura=
tion for
> the same artifact during a retrieve operation, the artifact is downloaded
> but the wrong artifact is copied in my project.
>
> Is it a limitation of the automatic unpacking (zip file in my case) not
> keeping the extra attributes? I=E2=80=99m new to Ivy so there might be a
> configuration option I haven=E2=80=99t found yet.
>
>
>
> For example, I=E2=80=99m using a custom pattern for the Ivy cache so I ca=
n get the
> different configuration downloaded and a similar custom pattern for the
> retrieve itself so I can get these different artifacts in my project.
> However, calling retrieve with a different configuration does create a ne=
w
> folder in my project (retrieve pattern), but it=E2=80=99s content is the =
same as
> with the previous configuration.
>
> Looking in the Ivy cache, I see that the download did create a new
> (proper) artifact in my cache according to my custom cache pattern, but t=
he
> same folder was used (and not overridden) for unpacking.
>
>
>
> It seems whatever pattern I set, the unpacking location will happen here
> in the cache: [organisation]/[module]/[revision]/[artifact]-[revision]/*
>
>
>
> My assumption currently, is that Ivy will find the same unpacking locatio=
n
> so will skip the unpacking step. Retrieve will then copy over a
> dirty/invalid version of what was unpacked. Are my assumptions correct?
>
>
>
> Is there a way to configure the unpacking location, if my understanding o=
f
> the issue is correct?
>
>
>
> P.S. I=E2=80=99m using configuration to differentiate different native C/=
C++
> builds (x86, arm, etc=E2=80=A6) Perhaps I=E2=80=99m not using the proper =
approach?
>
>
>
> Thank you,
>
>
>
> [image: Description: cid:image001.jpg@01C9B6D4.5B951A30]
>
> Jeremie Faucher-Goulet, Jr. Eng.
> Firmware Developer
> Trilliant Inc
> Tel: 450.375.0556 ext. 368
> jeremie.faucher-goulet@trilliantinc.com
>
> www.trilliantinc.com
>
>
>
>
>

--94eb2c08eeb0b74b750536706e35--