Created a JIRA bug for this: https://issues.apache.org/jira/browse/IVY-978
I added to the description sort of a corollary bug with buildnumber, where the ivy.revision property appears to be behaving as a traditional Ant property, where it's immutable, rather than behaving like a variable. I can attest that I have not manually set ivy.revision anywhere up to that point. On Sun, Nov 23, 2008 at 2:54 PM, Maarten Coene <[EMAIL PROTECTED]>wrote: > Seems like a bug to me. > I did a quick look at the buildnumber Ant task source-code and didn't see > the problem, so please create a JIRA ticket including your build.xml and Ant > console output illustrating the problem. > > Maarten > > > > ----- Original Message ---- > From: Mitch Gitman <[EMAIL PROTECTED]> > To: [email protected] > Sent: Sunday, November 23, 2008 12:23:08 AM > Subject: buildnumber Ant task ignoring prefix attribute > > Please forgive the prolific posting lately. I'm setting the prefix > attribute > on the *buildnumber *Ant task: > <ivy:buildnumber organisation="${ivy.organisation}" > module="${ivy.module}" > default="${ivy.default.revision}" *prefix="repo" */> > > But when I go to manually output the properties that are set, I see: > ivy-buildnumber: > [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<http://ant.apache.org/ivy/history/trunk/use/buildnumber.html > >has > to say about the prefix > attribute: > "the prefix to use for the property names set (will be *prefix*.revision, * > prefix*.new.revision, ...)" > > Am I missing something or is this a bug? > > > > >
