ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Siponen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IVY-732) install task dependent on defaultResolver instead of from attribute
Date Wed, 04 Dec 2013 20:16:37 GMT

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

Joe Siponen commented on IVY-732:
---------------------------------

I ran into this exact problem today in ivy 2.3.0 using the ivy:install task in ant. The ivy:install
ignores the from-attribute when resolving and instead resolves with the defaulResolver from
the ivysettings-files.

> install task dependent on defaultResolver instead of from attribute
> -------------------------------------------------------------------
>
>                 Key: IVY-732
>                 URL: https://issues.apache.org/jira/browse/IVY-732
>             Project: Ivy
>          Issue Type: Bug
>            Reporter: Shawn Castrianni
>
> I am using the install task to copy builds of my modules from one resolver to another,
which is what it was designed to do.  However, I have noticed that it appears to be dependent
on the defaultResolver in the settings file.  I think this is a bug since the install task
takes as attributes the from and to resolver.  The from resolver should be used to find the
module instance to copy from (not the defaultResolver) and the to resolver should be used
to locate the destination of where to copy the module instance to.  Therefore, if I specify
the revision of "latest.testing" in my install task and a from resolver of "testing", it should
find the latest revision of my testing modules in the testing resolver.  However, it is not
finding the latest one.  I changed my defaultResolver in my settings file to be "testing"
and then it started to work properly.  I changed it back and it failed again.  That tells
me that the install task is using the value of defaultResolver somehow.  Am I understanding
things correctly?  By the way, if I change my revision spec in the install task to be a specific
revision number in the "latest" resolver, it works fine.  The bug is only when I use the latest.XXXX
method.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message