You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-commits@incubator.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2007/05/21 13:26:20 UTC
[jira] Created: (IVY-513) ivy should stop telling me off twice for
ivyconf.xml files
ivy should stop telling me off twice for ivyconf.xml files
----------------------------------------------------------
Key: IVY-513
URL: https://issues.apache.org/jira/browse/IVY-513
Project: Ivy
Issue Type: Improvement
Reporter: Steve Loughran
Priority: Minor
If I run a build with ivy2.0.0 and only an ivyconf file isfound, I get told of first for the wrong filename, and then again for the wrong elements inside:
[ivy:configure] DEPRECATED: 'ivyconf' element is deprecated, use 'ivysettings' instead (file:/home/slo/Projects/SmartFrog/Forge/core/antbuild/ivy/ivyconf.xml)
[ivy:configure] DEPRECATED: 'conf' is deprecated, use 'settings' instead (file:/home/slo/Projects/SmartFrog/Forge/core/antbuild/ivy/ivyconf.xml)
but if I'm sticking with the old name for compatiblity, then I'm going to stick with the old element name too, arent I?
ivy should skip the second deprecation given the first has been printed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (IVY-513) ivy should stop telling me off twice for
ivyconf.xml files
Posted by "Gilles Scokart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gilles Scokart reassigned IVY-513:
----------------------------------
Assignee: Gilles Scokart
> ivy should stop telling me off twice for ivyconf.xml files
> ----------------------------------------------------------
>
> Key: IVY-513
> URL: https://issues.apache.org/jira/browse/IVY-513
> Project: Ivy
> Issue Type: Improvement
> Reporter: Steve Loughran
> Assigned To: Gilles Scokart
> Priority: Minor
>
> If I run a build with ivy2.0.0 and only an ivyconf file isfound, I get told of first for the wrong filename, and then again for the wrong elements inside:
> [ivy:configure] DEPRECATED: 'ivyconf' element is deprecated, use 'ivysettings' instead (file:/home/slo/Projects/SmartFrog/Forge/core/antbuild/ivy/ivyconf.xml)
> [ivy:configure] DEPRECATED: 'conf' is deprecated, use 'settings' instead (file:/home/slo/Projects/SmartFrog/Forge/core/antbuild/ivy/ivyconf.xml)
> but if I'm sticking with the old name for compatiblity, then I'm going to stick with the old element name too, arent I?
> ivy should skip the second deprecation given the first has been printed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVY-513) ivy should stop telling me off twice for
ivyconf.xml files
Posted by "Gilles Scokart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gilles Scokart resolved IVY-513.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0-alpha-2
> ivy should stop telling me off twice for ivyconf.xml files
> ----------------------------------------------------------
>
> Key: IVY-513
> URL: https://issues.apache.org/jira/browse/IVY-513
> Project: Ivy
> Issue Type: Improvement
> Reporter: Steve Loughran
> Assignee: Gilles Scokart
> Priority: Minor
> Fix For: 2.0.0-alpha-2
>
>
> If I run a build with ivy2.0.0 and only an ivyconf file isfound, I get told of first for the wrong filename, and then again for the wrong elements inside:
> [ivy:configure] DEPRECATED: 'ivyconf' element is deprecated, use 'ivysettings' instead (file:/home/slo/Projects/SmartFrog/Forge/core/antbuild/ivy/ivyconf.xml)
> [ivy:configure] DEPRECATED: 'conf' is deprecated, use 'settings' instead (file:/home/slo/Projects/SmartFrog/Forge/core/antbuild/ivy/ivyconf.xml)
> but if I'm sticking with the old name for compatiblity, then I'm going to stick with the old element name too, arent I?
> ivy should skip the second deprecation given the first has been printed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.