Comment all the properties in datadir (and harmonize the format of properties files) about datadir HOT 5 CLOSED

From my point of view:

• it's way easier for the administrator to configure these files: with a correctly configured editor, you directly see which properties are different from the default value (uncommented, generally displayed in white on black), and which properties will use the default value (commented, generally displayed in grey on black). The contrast helps a lot to navigate in these files.
• it also gives confidence to the administrator for its first steps: they only let the files untouched, or modify one or two parameters, and all should work as expected. And when they are a bit more experienced with geOrchestra, they will touch other parameters.
• currently, the administrator feels like they have to understand what every parameter does before trying geOrchestra, and it's uncomfortable (well, it was my feeling when I first approached geOrchestra, even if the configuration management was a bit different).

from datadir.

Well, this makes sense, even it feels weird to have nearly all values commented in a blank datadir !

from datadir.

in a blank datadir

Well, the datadir contains a lot more than properties files (maybe it's another issue, by the way)

from datadir.

TODO: for each property in an application properties file (and also for default.properties):

• verify that

  1. a default value is set in every placeholder that calls it in geOrchestra code,
  2. this default value is the same, if it's called in different places

• add a description, the default value, and comment the property, as for example:

  # Max time unused connections are kept idle in the pool. Unit is seconds for c3p0.
  # default: 60
  #dataSource.maxIdleTime=60
  

• test that no regression has been introduced.

from datadir.

See #138

from datadir.