Thank you for your help Marc. I understand much better now how Ivy is
intended to be used.
-Vincent
On Tue, Oct 4, 2016 at 2:19 AM, Marc De Boeck wrote:
> Actually, I never had to publish to separate directories per configuration.
> And also the documentation doesn't mention that it's possible
Actually, I never had to publish to separate directories per configuration.
And also the documentation doesn't mention that it's possible.
Typically in Ivy, each artifact is published only once per revision. The
"published" module descriptor (ivy-file) tells you which artifacts are part
of every c
Thanks for your reply Marc.
I have updated my settings as described (shown below) but am still
observing that my jar is published to a single conf of "default" rather
than to my two confs of "publicRuntime" and "publicTest". Note that I
tried it with and without a "conf" attribute in the ant publ
The publications section of the ivy-file (module descriptor) of your module
specifies for which configuration you publish the artifact(s) which are
part of your module:
Normally the ivy-file is checked-in in your source control system, and
during the build you will create a "resolved" ivy-fi
