ivy.settings.dir for an included file has URL encoded spaces
------------------------------------------------------------
Key: IVY-1125
URL: https://issues.apache.org/jira/browse/IVY-1125
Project: Ivy
Issue Type: Bug
Components: Core
Affects Versions: 2.1.0-RC2
Environment: Windows XP
Ant 1.7.1
Reporter: Paul Mealor
Priority: Minor
I have two ivysettings files, similar to the following:
File 1:
{code:xml}
<ivysettings>
<include file="z:\path with spaces\to\ivysettings2.xml"/>
</ivysettings>
{code}
File 2:
{code:xml}
<ivysettings>
<resolvers>
<filesystem name="myresolver">
<ivy
pattern="${ivy.settings.dir}/repository/[organisation]/[module]/[revision]/ivy.xml"/>
<artifact
pattern="${ivy.settings.dir}/repository/[organisation]/[module]/[revision]/[artifact].[ext]"/>
</filesystem>
</resolvers>
</ivysettings>
{code}
{{ivy.settings.dir}} is set to "{{z:\path%20with%20spaces\to}}". Thus, if I
publish a module to {{myresolver}}, it _actually_ gets published to the literal
path "{{z:\path%20with%20spaces\to\repository}}" rather than "{{z:\path with
spaces\to\repository}}".
This seems similar to IVY-1114, except that I'm not seeing the file: prefix.
I have a workaround at the moment, which is to specify
{{workaround.ivy.settings.dir}} in my Ant build.xml files (or that could be in
File 1 in the above example), and have the following in File 2:
{code:xml}
<ivysettings>
<property name="workaround.ivy.settings.dir" value="${ivy.settings.dir}"
override="false"/>
<resolvers>
<filesystem name="myresolver">
<ivy
pattern="${workaround.ivy.settings.dir}/repository/[organisation]/[module]/[revision]/ivy.xml"/>
<artifact
pattern="${workaround.ivy.settings.dir}/repository/[organisation]/[module]/[revision]/[artifact].[ext]"/>
</filesystem>
</resolvers>
</ivysettings>
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
