IvyDE
  1. IvyDE
  2. IVYDE-302

Initial project import results in 'Unrecognized variables in the Ivy settings file"

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.2.0.beta1
    • Fix Version/s: None
    • Component/s: workspace resolver
    • Labels:
      None
    • Environment:

      Windows 7 64-bit, MyEclipse 9.1

      Description

      When first importing a project that includes resolving an ivysettings file to the workspace, the following error is received:

      Some projects fail to be resolved
      Failed to configure Ivy for build/build_resources/jboss43/ivy.xml[core] in axis.warError while resolving the ivy instance for build/build_resources/jboss43/ivy.xml[core] in 'axis.war':
      Unrecognized variables in the Ivy settings file $

      {workspace_loc:axis.war/build/build_resources/jboss43/ivysettings.xml}

      Error while resolving the ivy instance for build/build_resources/jboss43/ivy.xml[core] in 'axis.war':
      Unrecognized variables in the Ivy settings file $

      {workspace_loc:axis.war/build/build_resources/jboss43/ivysettings.xml}

      Subsequently selecting to manually resolve the project will succeed as will deleting the project and importing a second time (as long as done within the same eclipse session).

      1. axis.war.zip
        8 kB
        Michael Ondrejko
      2. ivy_failure_on_import.png
        37 kB
        J.C. Hamlin

        Activity

        Hide
        Michael Ondrejko added a comment -

        The attached project can be imported and immediately shows the error message described.

        Show
        Michael Ondrejko added a comment - The attached project can be imported and immediately shows the error message described.
        Hide
        J.C. Hamlin added a comment -

        Screenshot of error message immediately after importing the project

        Show
        J.C. Hamlin added a comment - Screenshot of error message immediately after importing the project
        Hide
        Nicolas Lalevée added a comment -

        This is Eclipse firing initial tasks without having "refreshed" its "cache" of the filesystem. It is starting to work even if the files are not there... but the files are actually being there... This is the second time this behaviour hit badly IvyDE. I'm not sure what can be done here.

        Show
        Nicolas Lalevée added a comment - This is Eclipse firing initial tasks without having "refreshed" its "cache" of the filesystem. It is starting to work even if the files are not there... but the files are actually being there... This is the second time this behaviour hit badly IvyDE. I'm not sure what can be done here.
        Hide
        J.C. Hamlin added a comment -

        Have IvyDE wait for the refresh before doing anything. You'll see lots of tasks that block with the message something like "Waiting for workspace refresh to complete" in Eclipse. I'm not sure how to do it, but there should be lots of examples of how since it is such a common thing to happen in Eclipse.

        Show
        J.C. Hamlin added a comment - Have IvyDE wait for the refresh before doing anything. You'll see lots of tasks that block with the message something like "Waiting for workspace refresh to complete" in Eclipse. I'm not sure how to do it, but there should be lots of examples of how since it is such a common thing to happen in Eclipse.
        Hide
        Michael Ondrejko added a comment -

        Now, I am seeing a slightly different error message (but, still see an error): "Variable references non-existent resource". Again, manually performing the Ivy->Resolve works around the issue.

        Show
        Michael Ondrejko added a comment - Now, I am seeing a slightly different error message (but, still see an error): "Variable references non-existent resource". Again, manually performing the Ivy->Resolve works around the issue.
        Hide
        Nicolas Lalevée added a comment -

        For reference, I asked for hints there http://www.eclipse.org/forums/index.php/m/946074/

        Show
        Nicolas Lalevée added a comment - For reference, I asked for hints there http://www.eclipse.org/forums/index.php/m/946074/
        Hide
        Matthew Campbell added a comment -

        We're suffering from this as well. I'm trying to check in a bunch of eclipse .project and .classpath files to help ease people into using Ivy and IvyDE when they're not used to it. One source of confusion has been making sure they're pointing at a valid ivysettings.xml, so I'm trying to set project-specific settings on the ivy classpath container to look for the ivysettings file relative to the project_loc. This looks like it's valid while I'm filling in the field, but after trying to do a resolve, it returns the 'unrecognized variables' error.

        Show
        Matthew Campbell added a comment - We're suffering from this as well. I'm trying to check in a bunch of eclipse .project and .classpath files to help ease people into using Ivy and IvyDE when they're not used to it. One source of confusion has been making sure they're pointing at a valid ivysettings.xml, so I'm trying to set project-specific settings on the ivy classpath container to look for the ivysettings file relative to the project_loc. This looks like it's valid while I'm filling in the field, but after trying to do a resolve, it returns the 'unrecognized variables' error.
        Hide
        Nicolas Lalevée added a comment -

        A workaround which should work most of the time. Instead of putting the path into the eclipse variable, you should try to put it next to it.
        For instance, instead of using:

        ${workspace_loc:myproject/myconf/ivysettings.xml}

        try:

        ${workspace_loc:myproject}/myconf/ivysettings.xml
        Show
        Nicolas Lalevée added a comment - A workaround which should work most of the time. Instead of putting the path into the eclipse variable, you should try to put it next to it. For instance, instead of using: ${workspace_loc:myproject/myconf/ivysettings.xml} try: ${workspace_loc:myproject}/myconf/ivysettings.xml
        Hide
        JasonMing added a comment - - edited

        I have same problem too. As eclipse official said, ${project_loc} indicates the current project.
        However, when I am using ${project_loc}/ivysettings.xml
        as the path of ivysettings.xml, "Unrecognized variables in the Ivy settings file" will raise.
        If I specified the project name to project_loc (like ${project_loc:MyProjectName}/ivysettings.xml), it's ok.

        Show
        JasonMing added a comment - - edited I have same problem too. As eclipse official said, ${project_loc} indicates the current project. However, when I am using ${project_loc}/ivysettings.xml as the path of ivysettings.xml, "Unrecognized variables in the Ivy settings file" will raise. If I specified the project name to project_loc (like ${project_loc:MyProjectName}/ivysettings.xml), it's ok.

          People

          • Assignee:
            Unassigned
            Reporter:
            Michael Ondrejko
          • Votes:
            9 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

            • Created:
              Updated:

              Development