You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Carlton Brown (JIRA)" <ji...@apache.org> on 2008/03/13 20:32:24 UTC
[jira] Updated: (IVY-771) ivy:settings fails when override is not
set to 'true'
[ https://issues.apache.org/jira/browse/IVY-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlton Brown updated IVY-771:
------------------------------
Attachment: build-wrapper.xml
This is the build file. Run it without override specified, then with override specified to false. Run both these tests on both targets bootstrap-ivy and resolve-dependencies, the failures are different
> ivy:settings fails when override is not set to 'true'
> -----------------------------------------------------
>
> Key: IVY-771
> URL: https://issues.apache.org/jira/browse/IVY-771
> Project: Ivy
> Issue Type: Bug
> Components: Ant
> Affects Versions: 2.0.0-beta-2
> Environment: Windows XP
> Reporter: Carlton Brown
> Priority: Minor
> Attachments: build-wrapper.xml
>
>
> Call to <ivy:settings> results in different errors if override is not explicitly set to 'true'. The failure behavior depends whether override is set to false or not set at all.
> These tests both call the target "resolve-dependencies" which depends on a target "bootstrap-ivy". The <ivy:settings> only gets called from "bootstrap-ivy".
> If override is not set at all, this is the error:
> C:\allworkspaces\ivy-poc\hellorm\hello-A\src\build-wrapper.xml:47: overriding a previous definition of ivy:settings with the id 'module-settings' is not allowed when using override='notallowed'.
> at org.apache.ivy.ant.IvyAntSettings.execute(IvyAntSettings.java:262)
> If override is set to 'false', I get this error:
> C:\allworkspaces\ivy-poc\hellorm\hello-A\src\build-wrapper.xml:47: java.lang.NullPointerException
> at org.apache.tools.ant.Task.perform(Task.java:357)
> at org.apache.ivy.ant.IvyAntSettings.getConfiguredIvyInstance(IvyAntSettings.java:249).
> This test calls the target "bootstrap-ivy" directly. The behavior is same as above if I don't set override. However, if I set override to false, I don't get the NPE anymore, I get a warning about the settings already being defined:
> [ivy:settings] a settings definition is already available for module-settings: skipping
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.