ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mitch Gitman (JIRA)" <>
Subject [jira] [Commented] (IVY-1359) ivy.xml extends feature complains about Windows filesystem path
Date Tue, 10 Jul 2012 23:39:35 GMT


Mitch Gitman commented on IVY-1359:

I've submitted a patch for another bug I'd reported, issue IVY-1364: "buildlist task chokes
on absolute path to parent Ivy module."

I've verified that that fix also fixes this bug. Both these bugs have their root in XmlModuleDescriptorParser.checkParentModuleOnFilesystem
not up to now accounting for an absolute path.
> ivy.xml extends feature complains about Windows filesystem path
> ---------------------------------------------------------------
>                 Key: IVY-1359
>                 URL:
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.0-RC1
>         Environment: Windows, Ant 1.7.1 (but should be the same on Ant 1.8.3)
>            Reporter: Mitch Gitman
> I'm trying to use the parent Ivy module feature through the /ivy-module/info/extends
>   <info organisation="foo" module="bar" revision="1.0-SNAPSHOT">
>     <extends organisation="foo" module="master-parent" revision="1.0-SNAPSHOT" 
>         location="${env.MASTER_PARENT_PROJECT_DIR}/ivy.xml" extendType="configurations"
>   </info>
> The property placeholder in the location attribute translates to an absolute filesystem
path. This works in a functional sense. However, I'm seeing the following false-positive warning
message, apparently because I'm using a Windows filesystem path:
> [ivy:resolve] :: problems summary ::
> [ivy:resolve] :::: WARNINGS
> [ivy:resolve]   Unable to parse included ivy file C:\...\master-parent/ivy.xml: unknown
protocol: c
> [ivy:resolve]
> Here's the passage in XmlModuleDescriptorParser where this is arising:
>             //check on filesystem based on location attribute (for dev ONLY)
>             try {
>                 checkParentModuleOnFilesystem(location);
>             } catch (IOException e) {
>                 Message.warn("Unable to parse included ivy file " + location + ": "
>                     + e.getMessage());
>             }
> I hope people can agree that showing users a misleading warning message every time they
do an ivy:resolve is a bug worth resolving before there's a final 2.3.0 release.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message