[
https://issues.apache.org/jira/browse/IVYDE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13711969#comment-13711969
]
JasonMing commented on IVYDE-302:
---------------------------------
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.
> Initial project import results in 'Unrecognized variables in the Ivy settings
> file"
> -----------------------------------------------------------------------------------
>
> Key: IVYDE-302
> URL: https://issues.apache.org/jira/browse/IVYDE-302
> Project: IvyDE
> Issue Type: Bug
> Components: workspace resolver
> Affects Versions: 2.2.0.beta1
> Environment: Windows 7 64-bit, MyEclipse 9.1
> Reporter: Michael Ondrejko
> Attachments: axis.war.zip, ivy_failure_on_import.png
>
>
> 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).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
