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-809) Using ivy:settings with the "id" attribute not behaving as expected.
Date Fri, 25 Apr 2008 14:31:59 GMT

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

Maarten Coene commented on IVY-809:
-----------------------------------

I think this is a duplicate of IVY-771 which is fixed in SVN trunk.
Could you give it a try and see if you still have that the same problem?

> Using ivy:settings with the "id" attribute not behaving as expected.
> --------------------------------------------------------------------
>
>                 Key: IVY-809
>                 URL: https://issues.apache.org/jira/browse/IVY-809
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>    Affects Versions: 2.0.0-beta-2
>         Environment: Fedora 9
> ANT 1.6.5 / Ant 1.7.0
>            Reporter: Matt Inger
>         Attachments: build.xml, ivysettings.properties, ivysettings.xml
>
>
> Using the attached build file, I have encountered 2 issues:
> 1.  When using ivy:settings with the "id" attribute, i get an immediate failure if I
do not use the "override"
>      flag:
> Buildfile: build.xml
> foo:
> BUILD FAILED
> /home/minger/build.xml:5: overriding a previous definition of ivy:settings with the id
'settings1' is not allowed when using override='notallowed'.
> Total time: 0 seconds
> 2.  If i enable the override flag (as done in the "bar" target), it seems to be constructing
the deafult ivy instance
> when i execute a resolve or post-resolve task with a "settingsRef" defined.  It seems
to still pick up on the
> reference it's given.  However, it should not need to create the default "ivy.settings"
instance if you give it
> a reference.  In fact, it's very confusing and misleading to the user.  Not to mention
the "[null]" task name
> it's outputting in that case.  it also seems that the default ivy instance is using deprecated
elements and/or
> properties.
> Buildfile: build.xml
> bar:
> :: Ivy 2.0.0-beta2 - 20080225093827 :: http://ant.apache.org/ivy/ ::
> [ivy:settings] :: loading settings :: file = /home/minger/ivysettings.xml
> No ivy:settings found for the default reference 'ivy.instance'.  A default instance will
be used
>      [null] DEPRECATED: 'ivy.conf.file' is deprecated, use 'ivy.settings.file' instead
>      [null] :: loading settings :: file = /home/minger/ivysettings.xml
> [ivy:cachepath] :: resolving dependencies :: apache#commons-lang-caller;working
> [ivy:cachepath] 	confs: [default]
> [ivy:cachepath] 	found apache#commons-lang;2.3 in master-http
> [ivy:cachepath] :: resolution report :: resolve 118ms :: artifacts dl 5ms
> 	---------------------------------------------------------------------
> 	|                  |            modules            ||   artifacts   |
> 	|       conf       | number| search|dwnlded|evicted|| number|dwnlded|
> 	---------------------------------------------------------------------
> 	|      default     |   1   |   0   |   0   |   0   ||   1   |   0   |
> 	---------------------------------------------------------------------
> BUILD SUCCESSFUL
> Total time: 1 second

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