ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mitch Gitman (JIRA)" <>
Subject [jira] Created: (IVY-978) buildnumber Ant task ignoring prefix attribute
Date Tue, 25 Nov 2008 17:55:44 GMT
buildnumber Ant task ignoring prefix attribute

                 Key: IVY-978
             Project: Ivy
          Issue Type: Bug
          Components: Ant
    Affects Versions: 2.0-RC2
         Environment: JDK 1.6.0_07 on Windows Vista
            Reporter: Mitch Gitman

I'm setting the prefix attribute on the buildnumber Ant task:
    <ivy:buildnumber organisation="${ivy.organisation}"
      default="${ivy.default.revision}" prefix="repo" />

But when I go to manually output the properties that are set, I see:
     [echo] ivy:buildnumber output:
     [echo] ivy.revision=1.1
     [echo] repo.revision=${repo.revision}

You see that the default ivy.revision property gets set; the repo.revision property does not.

Here's what the buildnumber documentation has to say about the prefix attribute:
"the prefix to use for the property names set (will be prefix.revision,,

Addendum: There's another, possibly related issue with the buildnumber task. My understanding
is that the ivy.revision property is supposed to behave as a variable. As long as the user
hasn't manually set it at any point, an Ant task can set it to one value, and then another
Ant task can come along and set it to another value.

I've run into a situation where I might run a task like ivy:info and then subsequently run
ivy:buildnumber. According to info, which reads the ivy.xml, the revision is, say 1.1.200.
According to buildnumber, which scans the repository, the revision SHOULD BE working@machinename.
(Set aside the fact that the ivy.xml and repository are themselves inconsistent; I'm trying
to catch and deal with the situation where they are.) The buildnumber invocation shows revision
as 1.1.200 rather than working@machinename. In other words, it fails to find the main thing
it's supposed to be finding.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message