Return-Path: X-Original-To: apmail-gump-general-archive@www.apache.org Delivered-To: apmail-gump-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5E71410A7A for ; Tue, 15 Oct 2013 04:17:59 +0000 (UTC) Received: (qmail 55226 invoked by uid 500); 15 Oct 2013 04:17:56 -0000 Delivered-To: apmail-gump-general-archive@gump.apache.org Received: (qmail 55146 invoked by uid 500); 15 Oct 2013 04:17:47 -0000 Mailing-List: contact general-help@gump.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Gump code and data" Reply-To: "Gump code and data" Delivered-To: mailing list general@gump.apache.org Received: (qmail 55132 invoked by uid 99); 15 Oct 2013 04:17:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Oct 2013 04:17:43 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [178.254.33.213] (HELO samaflost.de) (178.254.33.213) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Oct 2013 04:17:38 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by samaflost.de (Postfix) with ESMTP id 224FA588C753 for ; Tue, 15 Oct 2013 06:17:15 +0200 (CEST) Received: from samaflost.de ([127.0.0.1]) by localhost (v35516.1blu.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4S2nwXCwbSt5 for ; Tue, 15 Oct 2013 06:16:54 +0200 (CEST) Received: by samaflost.de (Postfix, from userid 1000) id B23EB588C752; Tue, 15 Oct 2013 06:16:54 +0200 (CEST) From: Stefan Bodewig To: general@gump.apache.org Subject: Re: logging-log4j-12 failed References: <525328C8.7040202@oracle.com> <87ob70ghil.fsf@v35516.1blu.de> <525C8552.1000303@oracle.com> Date: Tue, 15 Oct 2013 06:16:54 +0200 In-Reply-To: <525C8552.1000303@oracle.com> (Ludmila Shikhvarg's message of "Mon, 14 Oct 2013 16:59:14 -0700") Message-ID: <87fvs3183t.fsf@v35516.1blu.de> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Virus-Checked: Checked by ClamAV on apache.org On 2013-10-15, Ludmila Shikhvarg wrote: > Stefan Bodewig wrote: >> On 2013-10-07, Ludmila Shikhvarg wrote: >>> Hi, >>> I'm using JDK8 from https://jdk8.java.net/download.html to run gump. >>> logging-log4j-12 is started to fail with b75 and onward (the build log >>> is attached). >>> Any ideas? >>> com.sun.tools.javac.code.Symbol$CompletionFailure: class file for sun.util.locale.provider.LocaleProviderAdapter not found >>> com.sun.tools.doclets.internal.toolkit.util.DocletAbortException: com.sun.tools.javac.code.Symbol$CompletionFailure: class file for sun.util.locale.provider.LocaleProviderAdapter not found >> Looks like a defect in javadoc to me - at least not like anything the >> log4j devs would be able to fix. >> Stefan > The same exception seen before the failure. > Heads up: > javadoc -Xdoclint is a new feature in jdk8. Default behavior is on so > that javadoc now issues warnings and errors and problems in javadoc > comments in the source: > $ jdk8/bin/javadoc -X > -Xdoclint Enable recommended checks for > problems in javadoc comments > -Xdoclint:(all|none|[-]) > Enable or disable specific checks for problems in javadoc comments, > where is one of accessibility, html, missing, reference, > or syntax. > You may choose to fix your javadoc comments, or to get backward > compatible behavior with jdk7 use -Xdoclint:none. I'll forward this to the log4j developers. But I really don't think this is an option. This is Java6: ,---- | $ javadoc -Xdoclint:none | javadoc: error - invalid flag: -Xdoclint:none `---- so my build process would have to detect Java8 at runtime and pass different arguments to javadoc based on it - this adds complexity. TBH I think it is a really bad idea to change defaults in a manner that breaks the build processes of code that worked before. In addition the exception itself isn't really helpful as it doesn't say what is wrong (at least I didn't see anything) but rather looks like a bug in javadoc - that one can avoid to trigger. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@gump.apache.org For additional commands, e-mail: general-help@gump.apache.org