1 follower Follow

Why is everything commented out in the file? When we change a default, do we need to uncomment it?




The order of the step in the step list for the noop operation. (inherited from: generic.CopiedArtifact.noopOrder)


Noop Verb (inherited from: generic.CopiedArtifact.noopVerb)


if true, preserve the existing files on the remote host (do not delete the copied files during the destroy operation). (inherited from: generic.CopiedArtifact.preserveExistingFiles)



Bernie Durfee Answered

Please sign in to leave a comment.



Hi Bernie,

The property file shows all the possible values in this way. It is like a document written with comments.

When you change a default, you need to uncomment it and restart the deployit server.

For example, the following is from

Placeholder scanning in archives (EAR, WAR, etc.) is now disabled by default. To enable it, edit and add the following line:

Levent Tutar 0 votes

Okay, thanks. But if those defaults are not be read, unless they're uncommented, then are they hardcoded somewhere else? Just seems strange to have a list of default in a properties file that are all commented out.

Either way, it might be good to state that you need to uncomment the value and bounce DeployIT (err... XL Deploy) in the docs and probably in the file. For example, in the docs you say...

You can change this list by setting the textFileNamesRegex property on the udm.BaseDeployableArtifact in the  file. Note that it takes a regular expression. It is also possible to change this on any of its subtypes which is important if you only want to change that for certain types of artifacts.

But if you just read that, it's not clear that you need to uncomment the line and bounce XL Deploy. So maybe just have section with a couple sentences on how to modify that file, the reference that.



Bernie Durfee 0 votes

Hi Bernie,

Lines that start with a comment character (#) are ignored, so that means you'll have to remove that character when you want to override a provided default value. The reasoning behind this is that the provided default value might change and you want to get that new value_ unless_ you have explicitly overridden it.

The file is automatically updated every time XL Deploy is started. All default values provided by the plugins installed in XL Deploy (including some built-in plugins such as the remoting-plugin that provides the overthere.SshHost type amongst others) are written to this file, except for those default values that have been explicitly overridden.

On a Unix machine, you can use the following command to see all the default values you have explicitly overridden:

grep -v ^# conf/ 

To ensure this is explained in the next iteration of the documentation, I have created issue DEPL-5801 in our internal issue tracker.

Regards, Vincent.


XebiaLabs Support 0 votes