Hello,

I'm encountering an issue where, when using a different configuration 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'm new to Ivy so there might be a configuration option I 
haven't found yet.

For example, I'm using a custom pattern for the Ivy cache so I can 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 new folder in my 
project (retrieve pattern), but it's 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 the 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 location 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 of the 
issue is correct?

P.S. I'm using configuration to differentiate different native C/C++ builds 
(x86, arm, etc...) Perhaps I'm not using the proper approach?

Thank you,

[Description: cid:image001.jpg@01C9B6D4.5B951A30]

Jeremie Faucher-Goulet, Jr. Eng.
Firmware Developer
Trilliant Inc
Tel: 450.375.0556 ext. 368
jeremie.faucher-gou...@trilliantinc.com<mailto:jeremie.faucher-gou...@trilliantinc.com>
www.trilliantinc.com<http://www.trilliantinc.com/>



Reply via email to