[ODLPARENT-130] SFT needs Karaf branding Created: 15/Nov/17 Updated: 22/Mar/19 Resolved: 22/Mar/19 |
|
| Status: | Resolved |
| Project: | odlparent |
| Component/s: | SFT |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0, 4.0.10, 3.1.7 |
| Type: | Bug | Priority: | Medium |
| Reporter: | Stephen Kitt | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
In odlparent 3, SFT ends up needing our Karaf branding (or perhaps it already needed it, and we’ve dropped the dependency somewhere). As a stop-gap measure I’m adding an explicit dependency, but we should figure out whether this is really appropriate. |
| Comments |
| Comment by Robert Varga [ 22/Mar/19 ] |
|
The dependency is needed and should be inherited transitively from opendaylight-karaf-empty through features-test. Dropped dependency is features-test containing an explicit exclusion of all opendaylight-karaf-empty's dependencies. That was needed when infrautils was using features-test at runtime and enforcing classpath duplicates, but that is no longer the case – features-test is used by single-feature-parent exclusively, hence it is safe to remove the exclusion and the duplicate declaration. |