[
https://issues.apache.org/jira/browse/IVY-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471558
]
Barrett Snyder commented on IVY-404:
------------------------------------
This appears to be a hashCode related issue. Arround line 2226 of Ivy.java in
the deliver method (step 3) it is attempting to lookup revisions in a map that
uses a ModuleRevisionId as the key. I was able to see that the hashcodes for
what should be an identical ModuleRevisionId are different. One is constructed
via parsing of the module descriptor, while the other is constructed from the
cache properties. The string output of both is the same, but the hashcodes are
different. I have not yet been able to find where the difference is coming
from, construction differences, or the hashcode method itself. I'm thinking it
may be an issue with teh fact that the hashcode is initialized at creation, but
then never gets updated after that even if the values making up the hash change.
> Static revision replacement is not working when delivering an artifact with a
> dependency on a branch
> ----------------------------------------------------------------------------------------------------
>
> Key: IVY-404
> URL: https://issues.apache.org/jira/browse/IVY-404
> Project: Ivy
> Issue Type: Bug
> Components: Ant, Core
> Affects Versions: 1.4.1
> Reporter: Barrett Snyder
> Priority: Critical
>
> In trying to deliver an ivy.xml, using the ant <deliver> task, for an
> artifact which has a dependency on a "latest.release" revision of a specific
> branch the dynamic revision is not getting replaced with the static rev. Here
> is what the dependency looks like:
> <dependency name="my-framework" rev="latest.release"
> branch="fix_for_release"/>
> If I remove the branch indicator the latest HEAD revision gets used and the
> rev attribute gets updated correctly. If I add the branch attribute the
> correct dependent branch release jar gets used, but the dynamic revision of
> the published ivy stays "latest.release".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
