I believe that the issue here is that some of the versions of org.apache.xmlrpc.server are very old and was relying on org.apache.commons.logging 1.1.0. Upgrading to Eclipse 2019-12 ended up requiring org.apache.commons.logging 1.2.0 somehow.
The correct fix would be to update where ever we got the bogus *.xmlrpc.server*.jar.
Another fix would be to remove org.eclipse.triquetrum.scisoft.analysis.rpc. It looks like org.eclipse.triquetrum.python.service/target/MANIFEST.MF imports it.
While updating to Eclipse 2019-12 (see Bug #341), the Triquetrum product fails to validate: A dialog appears:
Indeed, .metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.apache.xmlrpc.server_3.1.3.v20181004-1955.jar:meta-inf/manifest.mf contains:
I believe that the issue here is that some of the versions of org.apache.xmlrpc.server are very old and was relying on org.apache.commons.logging 1.1.0. Upgrading to Eclipse 2019-12 ended up requiring org.apache.commons.logging 1.2.0 somehow.
For a similar issue, see Eclipse Bug 537832: org.eclipse.platform.feature.group fails to install due to missing org.apache.commons.logging 1.1.1
The correct fix would be to update where ever we got the bogus
*.xmlrpc.server*.jar
.Another fix would be to remove org.eclipse.triquetrum.scisoft.analysis.rpc. It looks like org.eclipse.triquetrum.python.service/target/MANIFEST.MF imports it.