Update dependencies

[cstamas]

Changes:

• dropped plexus-xml, we use p-u 3.5.1 and no need for p-x
• maven-common-artifacts-filters 3.4.0
• junit 5.12.2

[kwin]

Usually in dynamic runtimes like OSGi you try to keep the dependency versions to the minimally required versions (as the import-package version ranges are calculated based on the compile classpath). In Maven context though the POM dependencies also define the runtime classpath (which should rather require latest&greatest). Not sure how to find middle ground and support older versions of deps at runtime outside Maven world….

[cstamas]

Oh, so you say to leave things as is? is fine to me... maybe just up JUnit then?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gnodet]

Usually in dynamic runtimes like OSGi you try to keep the dependency versions to the minimally required versions (as the import-package version ranges are calculated based on the compile classpath). In Maven context though the POM dependencies also define the runtime classpath (which should rather require latest&greatest). Not sure how to find middle ground and support older versions of deps at runtime outside Maven world….

Ideally, dependencies would be upgraded to their latest version, and if that's a problem for the OSGi metadata, we can upgrade the range to use a lower bound.

[cstamas]

Undone all, except for maven-common-artifact-filters and JUnit. Dropped plexus-xml as that one is not needed with plexus-util 3.x (how did that one got in at all?)