ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mitch Gitman <>
Subject Re: How to specify latest.any status correctly?
Date Mon, 24 Aug 2009 16:22:47 GMT
And I realize that one could make the argument that you don't need something
like "latest" or "latest.*" because, if you know your set of statuses, then
something like "latest.integration" gives you every status from integration
on up.

For my money, explicitly supporting something like "latest" or "latest.*"
would still be a nice shortcut. And there may be cases where you don't know
your full set of statuses so you don't know if "latest.integration" is your
"lowest" status.

On Mon, Aug 24, 2009 at 9:06 AM, Mitch Gitman <> wrote:

> Echoing Martin here. Tom, thanks for clarifying this.
> I feel stupid now (and it's not the first time) for reading "[any status]"
> as a special flag rather than just a text placeholder in the documentation.
> But then do I understand correctly that there is no deliberate way with Ivy
> (short of exploiting this bug) to say, "Give me the latest revision
> regardless of status?" This goes back to what Martin wrote: "I consider that
> being a feature, not a bug."
> I believe that asking for the latest revision regardless of status is not
> such an uncommon or invalid thing to do and that there ought to be some more
> straightforward way to specify it short of exploiting the fact that Ivy
> doesn't check the requested revision against the known set of statuses.
> I think either "latest" or "latest.*" would be a reasonable syntax. Or
> better yet, both.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message