On 2015-10-26 15:06, Markus Koschany wrote:
Am 26.10.2015 um 22:47 schrieb Emmanuel Bourg:
I haven't looked into the details but I don't think this is sufficient
to transition to httpclient. The Java classes and package names are not
the same, so a transition should imply code changes too. If it still
builds it probably means commons-httpclient is still in the dependency
graph at a deeper level, but activemq will FTBFS later when that other
package referencing commons-httpclient will transition to httpclient.


I haven't checked this fix either but I wanted to point out that
upstream has fixed this already. The latest upstream release depends on
httpcomponents-client instead of commons-httpclient, so upgrading to the
latest release should always resolve this issue.

The libregexp-java fix was the main focus to prevent the removal from
testing, but I will double-check the possibility of a nested dependency
on commons-httpclient.  Now that you mention it, I'm sure that has to be
the case.


This is the maintainer address of Debian's Java team
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to