Description
WARN GrouperStartup.printConfigOnce(177) - Grouper starting up: version: 2.4.0, build date: null, env: <no label configured>
...
grouper.hibernate.properties: null@null
We do have a settings for grouper.env.name, and the hibernate properties. However, they are not in the default conf/grouper*properties. They are in environment-specific cascade files defined outside the classpath. We then set the grouper.*.config.hierarchy with the file last in the list, so that it can override.
It seems that the startup is looking only at conf/grouper.properties and conf/grouper.hibernate.properties for certain settings during startup. Other than the startup, the rest of the API reads the override values just fine.
Attachments
Issue Links
- depends on
-
GRP-1949 harmonize Manifest properties in maven vs. ant build and fix dead project url
- Resolved