Generalize use of dependency reports to find versions in OSGI tests

Description

Our OSGI tests need to know the versions of all artifacts to set up the test infrastructure (see BundleOptions).

Right now they do this by reading system properties that are defined in the parent POM, and injected in the Surefire plugin configuration in integration-tests/pom.xml.

As part of I had to remove two of those properties (native-protocol and shaded Guava versions), so instead I loaded the deps.txt file that we generate for Insights, and read the versions from there.

It would be nice to generalize this mechanism to all artifacts:

  • also create a dependency reports for test dependencies. We only need this for core, and it can be generated in test-classes.

  • change BundleOptions to also load that file, and get all versions with getVersionFromDepsTxt

  • remove getVersionFromSystemProperty (we can probably also rename getVersionFromDepsTxt)

  • clean up the properties in the POMs. In the parent POM, I think we only need to extract a version when it's shared across multiple dependencies. Otherwise it can be hardcoded in the <dependencyManagement> section. In the integration-test POM, we don't need to inject anything anymore.

Environment

None

Pull Requests

None

Assignee

Unassigned

Reporter

Olivier Michallat

Labels

None

PM Priority

None

Affects versions

None

Fix versions

Pull Request

None

Doc Impact

None

Size

None

External issue ID

None

External issue ID

None

Priority

Minor
Configure