[ODLPARENT-207] Split out dependecies and policy from odlparent(-lite) Created: 22/Aug/19 Updated: 30/May/23 |
|
| Status: | Confirmed |
| Project: | odlparent |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | 14.0.0 |
| Type: | New Feature | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | pt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Our policy and its enforcement is tied up with dependency declarations in the odlparent/lite pom machinery, with no clear distinction drawn. This makes it difficult to modify policy enforcement rules downstream, as some things Just Come With odlparent. Create odlparent-dependencies, which will only contain dependencyManagement, pluginManagement sections. Create odlparent-policy, which will contain a pluginManagement section with configuration and tuneables. odlparent-lite should then inherit from odlparent-policy and contain appropriate policy trigger hooks. |