CMS-11726 Tika was upgraded to version 1.20
This brings in a compile scope dependency to com.sun.activation:javax.activation:jar:1.2.0, so that ends up in the CMS war through hippo-repository-tika dependency.
The jar contains the same classes as javax.activation:activation:jar:1.1.1 which used to be a compile scope dependency, see
Having activation classes in CMS.war is unwanted; can lead to class loader problems since these are normally present in container installation, say Tomcat /lib.
This happens in archetype projects on 13.1.0, 12.6.2 and 11.2.12.