[
https://issues.apache.org/jira/browse/IVY-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649631#action_12649631
]
Maarten Coene commented on IVY-970:
-----------------------------------
I don't think the buildnumber task should check the correctness of existing
ivy.xml files.
So what I would expect is that after you change the ivy.xml on the repository,
the buildnumber task still works as if nothing has been changed.
But it's strange that you still get "1.0-dev-b1" as buildnumber after your
first publish.
I'll try to reproduce the problem...
> <ivy:buildnumber> wrong result when resolve fails
> -------------------------------------------------
>
> Key: IVY-970
> URL: https://issues.apache.org/jira/browse/IVY-970
> Project: Ivy
> Issue Type: Bug
> Components: Ant
> Affects Versions: 2.0-RC2
> Reporter: Michael Kebe
> Assignee: Maarten Coene
> Fix For: trunk
>
>
> After publishing an artifact to the repository. Ivy uploads an ivy.xml and
> generates related .md5 .sha1 files.
> With a cleaned ivy cache the buildnumber task gives the wrong result when the
> ivy.xml in the repository is changed without changing the hash files.
> This is ok, as there is at least a warning. But currently there is nothing.
> The ivy:buildnumber task runs without a message and returns the "possibly"
> wrong next revision.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
