Ok, but I'm still thinking that would be better if the [revision] token in
ivy pattern and ${ivy.revision} should have the same value.
Thanks for your suggestion, anyway I've found another workaround using <ivy:
buildnumber />. The property ${ivy.new.revision) will provide a valid
number, when the revision is missing also.
Thanks, Paolo
On 1/12/07, Gilles Scokart <[EMAIL PROTECTED]> wrote:
You don't need to fill the attribute revision in your ivy file. You can
set
it in the attribute pubrevision of your publish task. By doing so, you
will
have the value of the revision in your script that publish because you
define it yourself (for example using the ant tstamp task.
I hope it answer your question?
Gilles
> -----Original Message-----
> From: Paolo Di Tommaso [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 12, 2007 3:29 PM
> To: [email protected]
> Subject: Revision attribute
>
> In my module ivy file I don't set the attribute "revision".
>
> Making so the [revision] token in the ivy pattern will be
> replaced with the current timestamp, but the ${ivy.revision}
> property will report "
> [EMAIL PROTECTED]".
>
> From a novice point of view it appears a little strange. But
> above all I'm not unable to access to that number as and ANT
> property, that is required to work with file names.
>
>
>
> Is there any workaround to that?
>
>
> Thank, Paolo
>
