[IVY-1359] ivy.xml extends feature complains about Windows filesystem path

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.3.0-RC1
• Fix Version/s: 2.3.0-RC2, 2.4.0-RC1
• Component/s: Core

Environment

Windows, Ant 1.7.1 (but should be the same on Ant 1.8.3)

• Assignee: Nicolas Lalevée
• Reporter: Mitch Gitman
• Created: 26/Jun/12 22:13
• Updated: 26/Mar/14 21:53
• Resolved: 22/Jul/12 19:47

Description

I'm trying to use the parent Ivy module feature through the /ivy-module/info/extends element:
<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]
[ivy:resolve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS

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.