Overhaul system of properties files that override baked-in values in uPortal 5 (Proposal)

Description

I would badly like to update the system we currently have WRT overrides.properties for the uPortal 5 release. These files allow deployers to "override" the values of properties that have been "baked-in" the build.

In uP4 we used primarily Maven Filters, and this system played a minor role. In uP5 we're getting rid of Maven Filters, and this system will be the primary means of configuration. We should get it right.

We currently source properties from the following external files...

And these files are documented thusly...

The first two files (overrides.properties) are intended to contain properties,

such as database secrets, that are shared with portlets (they read those property

files also). The latter two files (uPortal_overrides.properties) are for properties

that are specific to uPortal (portlets should not read these files).

That's what it says – but that's not at all what the portlets actually do. In fact they source EXACTLY the same files – all four of them.

Here is the system I would like to implement for uPortal 5...

Where 'portal.home' defaults to

but may be changed with a system property.

The 'global.properties' file may be sourced by any module; but the 'uPortal.properties' should only be sourced by uPortal.

Feedback please! (I'd like to move quickly.)

Environment

None

Activity

Show:
Christian Murphy
July 24, 2017, 10:28 PM
Edited
Andrew Wills
July 25, 2017, 6:31 PM
Andrew Wills
July 25, 2017, 10:45 PM
Andrew Wills
July 26, 2017, 8:26 PM

merged.

Assignee

Unassigned

Reporter

Andrew Wills

Labels

None

Estimated End Date

None

Fix versions

Priority

Critical
Configure