ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maarten Coene (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVY-970) <ivy:buildnumber> wrong result when resolve fails
Date Sun, 23 Nov 2008 22:47:44 GMT

    [ https://issues.apache.org/jira/browse/IVY-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650068#action_12650068
] 

Maarten Coene commented on IVY-970:
-----------------------------------

I think I've found the problem and committed a fix into svn trunk.
Could you please give it another try?

Even if we check the validity of the ivy.xml in the repository, your evil guy can still mess
up things when he:
- also updates the checksum files after changing the ivy.xml file to make sure they are ok
- or he could add completely new revisions by creating new directories and adding valid ivy.xml
files in there

I just don't think it's the responsability of the buildnumber task to check this, but we could
probably add a flag to the buildnumber task indicating that the found revision must be checked
for validity. If you really want something like this, could you add a new JIRA improvement
request?

> <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.


Mime
View raw message