Uploaded image for project: 'Ivy'
  1. Ivy
  2. IVY-1359

ivy.xml extends feature complains about Windows filesystem path

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.3.0-RC1
    • 2.3.0-RC2, 2.4.0-RC1
    • Core
    • None
    • Windows, Ant 1.7.1 (but should be the same on Ant 1.8.3)

    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.

      Attachments

        1. ivy-2.3.x.patch
          10 kB
          Mitch Gitman
        2. ivy-trunk.patch
          10 kB
          Mitch Gitman

        Activity

          People

            hibou Nicolas Lalevée
            mgitman Mitch Gitman
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: