Default behaviour loading user properties file may caue unexpected behaviour
allisterbeharry - August 24, 2007 - 14:22
| Project: | Drupal Automated Staging Toolkit |
| Version: | 5.x-2.0-soc07final |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | allisterbeharry |
| Status: | closed |
Jump to:
Description
By default a DAST build file called mybuild.xml always looks for mybuild-base.properties and mybuild.properties if you don't specify explicitly a base or user properties file. For example if I run mybuild.xml -d"basePropertiesFile=mybuild-custom.properties" then if mybuild.properties is present in the same directory as the build file it will still be loaded, because the propertiesFile property was not set on the command line. This may cause unexpected behaviour and will be changed so that as long as a basePropertiesFile or propertiesFile property is explicitly specified, no default property files will be loaded.

#1
Fixed in 5.x-2.1. SOLUTION: If you now specify a user properties file and not a base properties file DAST will load the default base properties file for the build script. However if you specify explicitly a custom base properties file, DAST will not attempt to load the default user properties file.
#2