Limit CLJ_WATSON_* env vars to known properties?

[seancorfield]

As implemented, the CLJ_WATSON_* env var machinery could be used to set any Java system property that isn't already specified on the command-line.

Should we limit this to only properties that DC core knows about? That would mean reading dependencycheck.properties from the classpath and using those core properties as a check list.

Concern: not all core properties need be listed in that file -- I suspect some optional ones are omitted so it would be impossible to override those via env vars if we added this check. Does that matter?

[lread]

Concern: not all core properties need be listed in that file -- I suspect some optional ones are omitted so it would be impossible to override those via env vars if we added this check. Does that matter?

Good question, but I don't think it matters.