Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 551094 - dev-vcs/subversion[doc,java] fails to build: ./subversion/bindings/javahl/src/org/tigris/subversion/javahl/ConflictDescriptor.java:173: error: unexpected content
Summary: dev-vcs/subversion[doc,java] fails to build: ./subversion/bindings/javahl/src...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Lars Wendler (Polynomial-C) (RETIRED)
URL:
Whiteboard:
Keywords:
: 594648 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-06-03 16:56 UTC by David W Noon
Modified: 2016-11-06 00:19 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info results (emerge_info.txt,6.64 KB, text/plain)
2015-06-03 16:56 UTC, David W Noon
Details
ebuild log (dev-vcs:subversion-1.8.13-r1:20150603-163121.log,679.73 KB, text/plain)
2015-06-03 16:58 UTC, David W Noon
Details
javadoc-nolint.patch (subversion-javadoc-nolint.patch,688 bytes, patch)
2016-09-18 22:39 UTC, Alexander Miller
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description David W Noon 2015-06-03 16:56:06 UTC
Created attachment 404524 [details]
emerge --info results

The javadoc utility reports multiple errors in the doc-javahl section of subversion.

The emerge --info and build log will follow in a few minutes.
Comment 1 David W Noon 2015-06-03 16:58:03 UTC
Created attachment 404526 [details]
ebuild log

ebuild log
Comment 2 Vasco Steinmetz 2015-06-04 07:22:51 UTC
Same issue here with a 1.8 VM:

*)      Oracle JDK 1.8.0.45 [oracle-jdk-bin-1.8]

after switching to a 1.7 VM:

chrome ~ # java-config -S 6
Now using oracle-jdk-bin-1.7 as your generation-2 system JVM

the javadoc errors disappear and Subversion can be emerged successfully.
Comment 3 David W Noon 2015-06-04 16:29:36 UTC
(In reply to Vasco Steinmetz from comment #2)
> Same issue here with a 1.8 VM:
> 
> *)      Oracle JDK 1.8.0.45 [oracle-jdk-bin-1.8]
> 
> after switching to a 1.7 VM:
> 
> chrome ~ # java-config -S 6
> Now using oracle-jdk-bin-1.7 as your generation-2 system JVM
> 
> the javadoc errors disappear and Subversion can be emerged successfully.

That's a good tip.  I switched the system-VM back to Icedtea 7 and it worked.
Comment 4 David W Noon 2015-08-10 17:36:05 UTC
This issue has arisen again with =dev-vcs/subversion-1.8.14.

Has there been any progress on this?
Comment 5 William L. Thomson Jr. 2015-08-20 21:25:24 UTC
Java 1.8 has is more strict on javadoc syntax. Technically they are issues to be addressed, but things need not fail due to poor javadoc syntax. The Java 1.8 option -Xdoclint:none relaxes this so javadoc is generated as it was before, despite it not conforming to W3C HTML 4.01 syntax. Need to see about setting -Xdoclint:none when javadocs are being generated. ejavadoc does this, but I do not see where that can come into play during build process. Thus need to see about passing that option to javadoc when the build system goes to generate the javadocs.
Comment 6 Torsten Kaiser 2015-09-26 16:50:42 UTC
I have dev-java/icedtea-3.0.0_pre04-r1 installed and as expected the same problem generating the javadocs.
The following patch works for me:

--- a/dev-vcs/subversion/subversion-1.9.2.ebuild     2015-09-24 04:31:02.000000000 +0200
+++ b/dev-vcs/subversion/subversion-1.9.2.ebuild   2015-09-26 18:35:55.046403521 +0200
@@ -145,6 +145,10 @@
        sed -i -e '1c\#!/usr/bin/env sh' build/transform_libtool_scripts.sh || \
                die "/bin/sh is not POSIX shell!"

+       # bad javadoc syntax breaks on java 1.8
+       sed -i -e 's/JAVADOC="$JAVA_BIN\/javadoc"/JAVADOC="$JAVA_BIN\/javadoc -Xdoclint:none"/' \
+               build/ac-macros/java.m4
+
        eautoconf
        elibtoolize
Comment 7 Torsten Kaiser 2015-12-19 18:28:20 UTC
dev-vcs/subversion-1.9.3 still has the same problem, the same fix from my previous comment is still working.
Comment 8 Pavel Goran 2016-05-09 14:51:01 UTC
It's still an issue with subversion-1.8.16, when building with IcedTea 3.0.1.
Comment 9 Alexander Miller 2016-09-18 22:39:00 UTC
Created attachment 446502 [details, diff]
javadoc-nolint.patch

Here is a patch for your convenience. (Note that the ebuild lacks a call to epatch_user, so it isn't as convenient as it could be.)
Works for me, tested with subversion-1.8.16.
Comment 10 Alexander Miller 2016-10-03 00:36:02 UTC
Still an issue with the recently stabilized subversion-1.9.4 (with icedtea-bin-3.1.0), and the same fix is still working.

Is there a particular reason why this hasn't been fixed yet?

Just try to emerge subversion with USE="doc java" and see yourself.
Comment 11 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2016-10-11 13:13:17 UTC
*** Bug 594648 has been marked as a duplicate of this bug. ***
Comment 12 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2016-10-11 13:28:49 UTC
commit 4ebaa7e551b2ad695f482b0b1d6d0f66f5d1db9e
Author: Lars Wendler <polynomial-c@gentoo.org>
Date:   Tue Oct 11 15:25:21 2016

    dev-vcs/subversion: Fixed creation of docs with USE="java" (bug #551094).

    Thanks to Alexander Miller for providing a patch.

    Package-Manager: portage-2.3.1
    Signed-off-by: Lars Wendler <polynomial-c@gentoo.org>


Sorry it took so long fixing this bug.
FYI, next release of subversion will get an EAPI-6 ebuild so user patches will be supported by default.
Comment 13 Honza 2016-11-06 00:19:43 UTC
Problem is that now it doesn't work with OLD java.