Follow-up to #4659.
Core has a lot few dependencies which are not up to date.
Basically we have a set of dependencies which get upgraded in a regular frequency: e.g. Karaf, Jetty, PaxWeb, some of the commons libs, asm (typically all of them on every Karaf release); Xtext/Xtend, guava, ecj, etc.
In addition, there are a lot of dependencies which have not seen an upgrade over years. This typically leads to mayn outdated dependencies still being pulled in or other upgrades being blocked by dependency conflicts.
There is a list of dependencies which still need attention (will post an excerpt from mvn versions:display-dependency-updates below in the comment).
Deprecated javax namespace is still a topic, not all dependencies already support jakarta namespace (e.g. hivemq-mqtt).
We cannot work on most of this close to a release, as sometimes files are missing on jfrog and break plugin installation, etc.
Related PRs:
osgiified dependencies might be overlooked by this script, e.g.
Follow-up to #4659.
Core has a
lotfew dependencies which are not up to date.Basically we have a set of dependencies which get upgraded in a regular frequency: e.g. Karaf, Jetty, PaxWeb, some of the commons libs, asm (typically all of them on every Karaf release); Xtext/Xtend, guava, ecj, etc.
In addition, there are a lot of dependencies which have not seen an upgrade over years. This typically leads to mayn outdated dependencies still being pulled in or other upgrades being blocked by dependency conflicts.
There is a list of dependencies which still need attention (will post an excerpt from
mvn versions:display-dependency-updatesbelow in the comment).Deprecated javax namespace is still a topic, not all dependencies already support jakarta namespace (e.g. hivemq-mqtt).
We cannot work on most of this close to a release, as sometimes files are missing on jfrog and break plugin installation, etc.
Related PRs:
osgiified dependencies might be overlooked by this script, e.g.