[ODLPARENT-34] Remove project-specific settings from custom.properties Created: 19/May/16 Updated: 03/Mar/22 Resolved: 03/Mar/22 |
|
| Status: | Resolved |
| Project: | odlparent |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | 10.0.0 |
| Type: | Task | ||
| Reporter: | Robert Varga | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||||||
| Description |
|
karaf/opendaylight-karaf-resources/src/main/resources/etc/custom.properties currently contains a slew of default settings used by downstream projects. From semantics perspective this means we have have a circular dependency and downstream projects have to push patches to controller to change the defaults. Define a mechanism by which downstream projects can define these themselves and move these settings out of the controller project. |
| Comments |
| Comment by Robert Varga [ 24/May/16 ] |
|
OFP: https://git.opendaylight.org/gerrit/39367 |
| Comment by Robert Varga [ 22/Aug/19 ] |
|
As per https://jira.opendaylight.org/browse/LISPMAP-146?focusedCommentId=67182&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-67182 this is targetted at odlparent-7 |
| Comment by Robert Varga [ 05/Oct/21 ] |
|
We can now ditch everything except lispflowmapping. Let's at least do that and then see if we can also close LISPMAP-146 during integration. |