Hello Hudson users,
There seems to be a bug related to alternate settings file feature in Hudson ver. 1.329 and after upgrade it has been reproduce in Hudson ver. 1.332 too. Help for "Alternate settings file" field suggests that path should be relative to workspace root; regardless if build's "Local module directory" is empty or not, when build starts Hudson seems to check for existence of configured settings.xml file but it does so using wrong file path: to the job workspace Hudson wrongfully appends "Local module directory" (if empty then it appends last path component of URL), and then appends path configured as "Alternate settings file" which already contains "Local module directory" (or if empty, last path component of URL) because it is supposed to be relative to workspace root. This settings.xml file existence check fails build before maven is run.
When configuring "Alternate settings file" field it seems same wrong validation is used to check for existence of configured file, and it doesn't complain when configured "Alternate settings" file path doesn't start with "Local module directory" (or if empty, last path component of URL).
If one configures job's "Alternate settings file" path not to include "Local module directory", build starts (settings.xml file existence check seems to pass), but in build log I see that path used for -s option is wrong, it doesn't append "Local module directory" nor last path component of URL if "Local module directory" is empty; maven doesn't complain that -s option uses invalid path and just continues, but later build fails because alternate settings.xml isn't being used (e.g. dependency/plugin can not be downloaded from secured repository as appropriate server definition is missing).
Regards,
Stevo.
