[ 
https://issues.apache.org/jira/browse/IVY-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Hurne updated IVY-1346:
----------------------------

    Attachment: IVY-1346.zip

An example project that produces the warning is attached (IVY-1346.zip).  This 
project assumes that you have the Ivy JAR in ANT_HOME/lib.  Simply run {{ant}} 
from the directory containing the {{build.xml}}, and you should see the 
following output:

{noformat}

C:\Documents and Settings\mhurne\Desktop\IVY-1346>ant
Buildfile: build.xml

default:
[ivy:resolve] :: Ivy 2.2.0 - 20100923230623 :: http://ant.apache.org/ivy/ ::
[ivy:resolve] :: loading settings :: file = C:\Documents and 
Settings\mhurne\Desktop\IVY-1346\ivysettings.xml
[ivy:resolve] :: resolving dependencies :: foo#child;1.0
[ivy:resolve]   confs: [default]
[ivy:resolve] :: resolution report :: resolve 31ms :: artifacts dl 0ms
        ---------------------------------------------------------------------
        |                  |            modules            ||   artifacts   |
        |       conf       | number| search|dwnlded|evicted|| number|dwnlded|
        ---------------------------------------------------------------------
        |      default     |   0   |   0   |   0   |   0   ||   0   |   0   |
        ---------------------------------------------------------------------
[ivy:resolve]
[ivy:resolve] :: problems summary ::
[ivy:resolve] :::: WARNINGS
[ivy:resolve]   Unable to parse included ivy file ../ivy.xml: C:\Documents and 
Settings\mhurne\Desktop\ivy.xml (The system cannot find the file specified) in 
file:/C:/Documents%20and%20Settings/mhurne/Desktop/ivy.xml
[ivy:resolve]
[ivy:resolve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS

BUILD SUCCESSFUL
Total time: 0 seconds{noformat}
                
> Unnecessary warning when parent ivy.xml is located using resolvers rather 
> than a location attribute on the extends element
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IVY-1346
>                 URL: https://issues.apache.org/jira/browse/IVY-1346
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.2.0, 2.3.0-RC1
>            Reporter: Matt Hurne
>            Priority: Minor
>         Attachments: IVY-1346.patch, IVY-1346.zip
>
>
> When using an {{<extends>}} element without a {{location}} attribute an 
> unnecessary warning is output stating that {{../ivy.xml}} could not be parsed 
> (unless there is in fact a file {{../ivy.xml}} relative to the {{ivy.xml}} 
> that contains the {{<extends>}}).
> For example:
> {noformat}
> ...
>     <info organisation="foo" module="bar" revision="1.0" status="integration">
>         <extends organisation="foo" module="parent" revision="1.0.0" />
>     </info>
> ...
> {noformat}
> {noformat}
> [ivy:resolve] Unable to parse included ivy file ../ivy.xml: 
> D:\project\component\ivy.xml
> (The system cannot find the file specified) in 
> file:/D:/project/component/ivy.xml
> {noformat}
> {{XmlModuleDescriptorParser.extendsStarted()}} is the source of the warning.  
> If no {{location}} was specified on the {{<extends>}} it uses a default 
> location of {{../ivy.xml}}.  It then attempts to find and use the 
> {{../ivy.xml}} location, and only falls back to resolving the parent 
> descriptor if {{../ivy.xml}} doesn't exist or if its {{ModuleId}} is not what 
> is expected.
> The behavior is sensible and I do not suggest that it be changed.  However, 
> it would be nice if the warning that {{../ivy.xml}} could not be parsed were 
> suppressed when that file is being used as a default.  The warning would 
> still be appropriate if {{location="../ivy.xml"}} were explicitly included in 
> the {{<extends>}} element.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to