ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 49891] Nested subant does not allow override of properties.
Date Wed, 25 Jun 2014 09:19:13 GMT

--- Comment #7 from Sjoerd van Leent <> ---
Recently, at our office (Realworld Systems) we experienced issues with the same
underlying problem. We usually use a file to override or
introduce properties. However, on our CI (Jenkins) we encode these properties
into the Jenkins environment.

This time, we had a certain property, which was altered with subant. On the
command-line, on the developer's box, this was alright. However, the behavior
of Ant inside the CI was quite different.

After experimenting a bit, we found out that these properies are set through
the command-line, creating the same problem as already described.

Aside from the change to addAlmostAll, we would like to be able to have a
tertiary property, indicating whether command-line properties should take
precedence, or at least a way to indicate which command-line properties should
be excluded from precedence.

To our understanding, the behavior, although documented, is illogical and
contradicts with the normal expectation of the properties to be reset.

You are receiving this mail because:
You are the assignee for the bug.

View raw message