[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [papyrus-rt-dev] Failing builds
|
Indeed. The non-lazy mode is critically important for reproducibility of builds, especially for release builds in which the dependencies are all also releases and so permanently available. It might also make sense for stable milestone builds, but we don't really do those. At least, not yet.
Christian
On November 8, 2016 at 07:55:48, Philip Langer (planger@xxxxxxxxxxxxxxxxx) wrote:
Hi,
the "lazy" keyword is equivalent to version 0.0.0 in the
target file, which means that the most current version will be
selected at _resolution time_. If the "lazy" keyword is _not_ used,
the version will be fixed to a specific version, which is the most
current version at the time at which the target file is
generated.
The latter is more conservative and fine for release streams,
as there won't be any surprises regarding the versions we consume.
But we definitely should use the "lazy" keyword for nightly builds,
because otherwise the build may fail in the future, when a specific
version is not available anymore. I think, we should also use lazy
for integration builds, as we typically want to test the
integration with all the latest other plug-ins within the defined
range rather than with a specific version.
Hope that helps!
Best wishes,
Philip
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev