Ivy settings file must be a property, not a hardwired absolute file path

[GoogleCodeExporter]

Environment : ivybeans for 6.7, netbeans 6.9 , OS both, jdk 1.6.0_21

Description :

We build in two environments, on the desktop and on a Bamboo CIM server on the 
cloud.

The first is Windows, the second unix. So any absolute paths in the build 
configuration must necessarily be overwritten in the CIM environment. The 
mechanism available is to set ant properties from the ant command line, or from 
a properties file included from the ant command.

Unfortunately the ivysettings absolute path is entered directly into 
ivy-build.xml when Iybeans builds ivy-impl, and will be written back there 
whenever ivybeans changes it.

It needs to be entered via a property so that in the CIM environment it can be 
overridden. I put an ivy.settings.file property in project.properties and 
change the two instances of <ivy:settings in ivy-impl to

<ivy:settings file="${ivy.settings.file}"/>

and this does work, but Ivybeans tends to overwrite it. 

Note, the ivysettings file has different content in the two environments, 
reaching the repository requires in this case different routing.

Ideally the ivysettings should be on, e.g. the user's home directory by default.

Original issue reported on code.google.com by malcolm....@googlemail.com on 22 Sep 2010 at 3:08

• Merged into: #70

[GoogleCodeExporter]

As you said may be we can use that convention and not configure it.

Original comment by laurent....@gmail.com on 22 Sep 2010 at 3:35

• Added labels: Fix-1.2

[GoogleCodeExporter]

Original comment by laurent....@gmail.com on 24 Sep 2010 at 7:41

• Changed state: Duplicate