g. by using the e:classifier
attribute).
Regards,
Marc
2016-07-04 21:37 GMT+02:00 Jeremie Faucher-Goulet <
jeremie.faucher-gou...@trilliantinc.com>:
> Thanks for your feedback Hugh,
>
> Interesting concept of having a unpack cache to reuse across projects,
> I'll keep that in
s email. Furthermore, the company does not
warrant a proper and complete transmission of this information, nor does it
accept liability for any delays. If you have received this message in error,
please contact the sender and delete the message.
-Original Message-
From: Jeremie Faucher-Goulet [ma
ot;publications/artifact" XML element introduced in ivy 2.4.0. Is there an
updated version of the XSD published somewhere else?
Thanks,
[Description: cid:image001.jpg@01C9B6D4.5B951A30]
Jeremie Faucher-Goulet, Jr. Eng.
Firmware Developer
Trilliant Inc
Tel: 450.375.0556 ext. 368
d to avoid it.
But even with this little annoyance, I prefer it to unpacking manually as it
looks tidier and reduce the amount of scripting and duplication of
configuration variables/settings.
Best regards,
Jérémie
-Original Message-
From: Jeremie Faucher-Goulet [mailto:jeremie.faucher-gou...
-attribute in our environment and see if I can reproduce your problem.
Regards,
Marc
2016-06-29 22:50 GMT+02:00 Jeremie Faucher-Goulet <
jeremie.faucher-gou...@trilliantinc.com>:
> Other useful tidbits
>
> Here is my retrieve task in build.xml:
>
>
>
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
ute, or
related to something else.
Regards,
Marc
2016-06-29 21:22 GMT+02:00 Jeremie Faucher-Goulet <
jeremie.faucher-gou...@trilliantinc.com>:
> Hello,
>
>
>
> I’m encountering an issue where, when using a different configuration
> for the same artifact during a retri
