Previously in deploymentBuilder.step ${dirs.deployment} referred to the deployment folder under the code_drop directory. In the new default.build.settings ${dirs.deployment} refers to the deployment folder under the current directory with ${dirs.drop.deployment} referring to the folder under the code_drop directory.
This leads to the template files being created incorrectly in the current directory and not under the code_drop directory for packaging.
Previously in deploymentBuilder.step ${dirs.deployment} referred to the deployment folder under the code_drop directory. In the new default.build.settings ${dirs.deployment} refers to the deployment folder under the current directory with ${dirs.drop.deployment} referring to the folder under the code_drop directory.
This leads to the template files being created incorrectly in the current directory and not under the code_drop directory for packaging.