Bug 698288 – net-p2p/vuze-4.8.1.2-r1 - .../work/vuze-4.8.1.2/com/aelitis/azureus/util/ImportExportUtils.java:363: error: constructor JSONArray in class JSONArray cannot be applied to given types;

• Status: RESOLVED WONTFIX
• Product: Gentoo Linux

[Description Rob van Riel 2019-10-22 14:46:40 UTC]

Created attachment 593622 [details]
build.log

Note: this was cloned from Bug 698262, which was correctly rejected because the build log I attached was based on an ebuild not in the Gentoo repository but in a local overlay. That particular ebuild is identical to the one in the Gentoo repository though, so the issue remains. My apologies for the mixup.


The build for this package fails due to the interface for JSONArray not being what the code expects.

A quick internet search shows the interface for JSONArray changed between Java 6 and Java 7; I suspect this is the immediate cause of the problem.

The source for Vuze includes a local version of the JSON classes, but the current ebuild deletes this before starting the build. As an experiment, I removed the delete command from the ebuild. This resulted in a succesful build, and a binary that at first glance appears to function. I do not know why the local JSON was removed of course, so this may not be a real solution.

[Comment 1 Rob van Riel 2019-10-22 14:47:48 UTC]

Created attachment 593624 [details]
output from emerge --info

[Comment 2 Miroslav Šulc 2019-10-22 18:52:55 UTC]

i don't use vuze so i have no idea why we have both version 4.8 and 5.7 in the tree. 5.7.2.0-r1 compiles fine for me. could you please explain why the 4.8 version is needed?

[Comment 3 Rob van Riel 2019-10-22 23:42:00 UTC]

Vuze 4.x was a free Bittorrent client. Vuze 5.x became an adware delivery system for a media subscription service, with a bittorrent client hiding inside it. From a user (interface) perspective, they are completely different tools, even if the code base and parent company are the same.

I have no idea how many people beside me still use the old Vuze, nor do I have the required Java knowledge to quickly judge how much effort would be involved to make this code work with the modern JSON interface (and possibly other Java changes), so it's hard for me to build a case for keepin 4.x in.
I do know that from my point of view, it's even harder to build a case for having 5.x in the repository at all.

[Comment 4 Miroslav Šulc 2021-04-19 08:02:02 UTC]

that version has been removed