I was investigating the Java 11 FTBFS of axis and uddi4j. I wonder if we rather should focus on removing these packages instead of patching them.
Axis has seen its last release in 2006. AFAIK Apache CXF would be a better alternative because it is actively maintained. Unfortunately it is not available in Debian. Looking at the reverse build-dependencies of axis: Reverse-Build-Depends-Indep =========================== * starjava-vo * starjava-votable * uimaj Reverse-Build-Depends ===================== * eclipse-mylyn * eclipse-wtp * jalview * jets3t * jglobus * uddi4j eclipse-* packages can be ignored and jalview has been RC buggy for a long time. uddi4j can go as well and it only has eclipse-wtp and wsil4j as r-deps. Thus the remaining packages would be: * starjava-vo * starjava-votable * uimaj * jets3t * jglobus jglobus just seems to build an axis module and a binary package without any r-deps, so it could be removed I guess. The jets3t version in Debian is very old but the latest one is also from 2015, so I doubt it has been fixed upstream. I don't see any code in starjava-vo that uses axis, looks more like a runtime feature but I'm not sure. In uimaj the uimaj-adapter-soap makes use of axis. So with a bit of effort we could get rid of a couple of hardly used packages and don't have to maintain them any longer. Thoughts? Markus
signature.asc
Description: OpenPGP digital signature
__ This is the maintainer address of Debian's Java team <https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use debian-j...@lists.debian.org for discussions and questions.
