This is an internal documentation. There is a good chance you’re looking for something else. See Disclaimer.
Dependency management in root build.gradle¶
All external dependencies should be added to the
dependencyManagement block in the root build.gradle. This way,
they can be managed in one single place which makes it much easier to keep them up to date.
Each dependency is added with the desired version number to the
dependencyManagement block. Once defined there,
there is no version number needed in the dependency declaration in the actual module where the dependency is included.
Imagine we need the dependency
org.jsoup:jsoup in the module
:optional:address. We further assume,
that the current version of JSOUP is
The dependency would be included as follows:
Add the dependency
dependency "org.jsoup:jsoup:1.14.3"to the root build.gradle of the Nice2 project in the
Include the dependency
implementation "org.jsoup:jsoup"in the
:optional:addressmodule (don’t specify a version). If the dependency is used in the api or spi package of the module the dependency should be added as api dependency (
If you need to manage a set of dependencies which share the same version number, it makes sense to define a
variable for that version number
jsoupVersion=1.10.3) which can be used for all
dependencies in the
Update backend dependencies on a regular basis¶
It’s important to keep all dependencies up to date. Therefore, there’s a weekly job on GitLab which generates a report of all dependencies which are out-of-date. The job runs every Saturday.
Find the latest report:
Find check for outdated dependencies on the Schedules page.
Open the last pipeline (link in column Last Pipeline).
Open job list-outdated-dependencies
Browse job artifacts (right panel)