, January 24, 2017 4:35 PM
To: ivy-user@ant.apache.org
Subject: AW: Performing a release of an IVY module
Thanks for the feedback and you experiences. As far as I understood, the
recommendation is to use both systems SCM and Artifactory/IVY to manage all
information for reproducible builds.
Preparing
[mailto:jonathan.ou...@intel.com]
Gesendet: Dienstag, 24. Januar 2017 13:57
An: ivy-user@ant.apache.org
Betreff: RE: Performing a release of an IVY module
We approach this problem from the other end, using Artifactory as the source of
truth instead of SVN.
Of course we use SVN to hold our source code, but we
--
From: Marc De Boeck [mailto:mdeb...@gmail.com]
Sent: Monday, January 23, 2017 9:09 PM
To: ivy-user@ant.apache.org
Subject: Re: Performing a release of an IVY module
Ivy is a flexible tool and also the release process can be tuned according to
your own needs.
Personally, I think that you sh
Ivy is a flexible tool and also the release process can be tuned according
to your own needs.
Personally, I think that you should not try to copy the "release process"
used in the maven world.
I believe more in a continuous build process where builds are promoted to
releases when they have been
We are searching for a best practice documentation about the release process of
an IVY module like described here [1]. For us it is quite important to produce
reproducible builds with all dependencies of the release build. For that, we
have to push the resolved IVY descriptor in the SCM system
