[ODLPARENT-209] SFT does not reflect standard feature edits Created: 03/Sep/19 Updated: 20/Nov/19 Resolved: 20/Nov/19 |
|
| Status: | Resolved |
| Project: | odlparent |
| Component/s: | Karaf, SFT |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.2, 5.0.4, 4.0.14 |
| Type: | Bug | Priority: | High |
| Reporter: | Robert Varga | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
When SFT runs, it installs components based on unpatched version of standard-features.xml, which means it has down-revved aries-proxy (1.1.3 vs. 1.1.4) – thus failing on interface default methods. It also seems test-distribution boot features are based on unpatched versions as well. This leads to us testing not what we are shipping, but rather against vanilla karaf-4.2.2. We need to fix this, as we are forced to deploy workarounds for https://issues.apache.org/jira/browse/ARIES-1923 in at least three components. |
| Comments |
| Comment by Robert Varga [ 03/Sep/19 ] |
|
skitt any idea why this is happening? |
| Comment by Robert Varga [ 18/Nov/19 ] |
|
This is blocking our ability to upgrade to karaf-4.2.5+ it seems. |
| Comment by Robert Varga [ 18/Nov/19 ] |
|
So the boot features in test-distribution are okay, at least to the extent of resulting in correct (patched) stuff being installed. |