[BUILD-793] Let ITs dependencies be managed by BOM Created: 16/May/22 Updated: 16/May/22 Resolved: 16/May/22 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Federico Grilli | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | testing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Team: | |||||||||
| Description |
|
Test dependencies should be managed in boms, as much as possible. For instance, we likely don’t need the nekohtml artifact which is old and unmaintained (replaced by a newer library with BUILD-752). Its sole purpose by now is to provide that xerces class to htmlunit but we can add xercesImpl directly to ITs with test scope. Also we should probably extract out the so-called magnolia-integration-tests-framework (the one used for non UI tests) into its own module (could be a submodule of test-framework?) and manage dependencies and classes to be extended in one place. |