chore:cleaner dependencies

[svandenhoek]

What are the main changes you did:

• Solution for module-specific dependencies with shared versioning
• Migrated the "dependencies for all subprojects" (except generic testing ones like junit) to their actual projects and filtered out the ones not needed per-module.
• Tested for renovate support using LOG_LEVEL=debug renovate --platform=local > renovate.log. As shown below it seems that Renovate understands the changes.

master

{
                 "depName": "org.eclipse.rdf4j:rdf4j-rio-api",
                 "currentValue": "5.0.1",
                 "managerData": {
                   "fileReplacePosition": 1975,
                   "packageFile": "backend/build.gradle"
                 },
                 "fileReplacePosition": 1975,
                 "datasource": "maven",
                 "registryUrls": ["https://repo.maven.apache.org/maven2"],
                 "depType": "dependencies",
                 "updates": [
                   {
                     "bucket": "non-major",
                     "newVersion": "5.0.2",
                     "newValue": "5.0.2",
                     "releaseTimestamp": "2024-08-02T17:45:17.000Z",
                     "newMajor": 5,
                     "newMinor": 0,
                     "newPatch": 2,
                     "updateType": "patch",
                     "branchName": "renovate/org.eclipse.rdf4j"
                   }
                 ],

PR

"gradle": [
           {
             "packageFile": "gradle.properties",
             "datasource": "maven",
             "deps": [
               {
                 "depName": "org.eclipse.rdf4j:rdf4j-rio-api",
                 "currentValue": "5.0.1",
                 "groupName": "rdf4jVersion",
                 "managerData": {
                   "fileReplacePosition": 477,
                   "packageFile": "gradle.properties"
                 },
                 "fileReplacePosition": 477,
                 "datasource": "maven",
                 "registryUrls": ["https://repo.maven.apache.org/maven2"],
                 "depType": "dependencies",
                 "updates": [
                   {
                     "bucket": "non-major",
                     "newVersion": "5.0.2",
                     "newValue": "5.0.2",
                     "releaseTimestamp": "2024-08-02T17:45:17.000Z",
                     "newMajor": 5,
                     "newMinor": 0,
                     "newPatch": 2,
                     "updateType": "patch",
                     "branchName": "renovate/org.eclipse.rdf4j"
                   }
                 ],

• explain what you changed and essential considerations.

how to test:

• Check if module-specific dependencies are correct (by someone that knows per-module if the dependencies are in-line with expected).
• Renovate dry-run through the command line (LOG_LEVEL=debug renovate --platform=local > renovate.log) should indicate it understands the changes that were made.
• Check if once live Renovate still creates new PRs and also adjusts the version numbers in the right position.

todo:

• updated docs in case of new feature
• added/updated tests
• added/updated testplan to include a test for this fix, including ref to bug using # notation

[mswertz]

I need confirmation that this works with renovate before I can approve this. I find this not really much cleaner that it was before. In practice we are building one big fat jar so moving the shared dependencies to the /backend/build.gradle is in my mind better option.

[svandenhoek]

I need confirmation that this works with renovate before I can approve this.

I checked with the Renovate CLI version (see initial PR message) to see if it spotted the gradle.properties file. Additionally:

Renovate can update:

• *.gradle/*.gradle.kts files
• Dependencies with version definitions in gradle.properties files

[...]

Source: https://docs.renovatebot.com/java/#gradle-file-support

---

so moving the shared dependencies to the /backend/build.gradle is in my mind better option.

Done (untested which I'll do later, but do let me know if this is indeed the preferred way compared to 1394ef5).

[sonarcloud]

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 SonarCloud