Re: JDK8 compatible javadoc

2014-05-02 Thread Gary Gregory
mons Developers List Subject: Re: JDK8 compatible javadoc >so it would be nice if our components do compile and work on Java 8 It does of course. But if you compile with java8 then it _might_ not work with older java versions. So it's fine for packages built by Fedora FOR Fedora. But th

Re: JDK8 compatible javadoc

2014-05-02 Thread Mark Struberg
>so it would be nice if our components do compile and work on Java 8 It does of course. But if you compile with java8 then it _might_ not work with older java versions. So it's fine for packages built by Fedora FOR Fedora. But those jars might not work on any other linux distro. Which is ok from

Re: JDK8 compatible javadoc

2014-05-02 Thread Gary Gregory
On Fri, May 2, 2014 at 9:43 AM, Emmanuel Bourg wrote: > Le 02/05/2014 15:37, Gary Gregory a écrit : > > So the plan is to let each [component] pick how they want to deal with > Java > > 8 right? > > As a side note, I'd like to emphasize that our source code is being > recompiled by downstream pac

Re: JDK8 compatible javadoc

2014-05-02 Thread Emmanuel Bourg
Le 02/05/2014 15:37, Gary Gregory a écrit : > So the plan is to let each [component] pick how they want to deal with Java > 8 right? As a side note, I'd like to emphasize that our source code is being recompiled by downstream packagers, most notably Linux distributions. Fedora 21 will default to J

Re: JDK8 compatible javadoc

2014-05-02 Thread Gary Gregory
So the plan is to let each [component] pick how they want to deal with Java 8 right? Gary On Fri, May 2, 2014 at 8:13 AM, Mark Struberg wrote: > -Xdoclint:all -Xdoclint:-missing -Xdoclint:-html > > That should fix the issue. > ATTN: this must ONLY be done in a java8 profile! If you set those p

Re: JDK8 compatible javadoc

2014-05-02 Thread Mark Struberg
-Xdoclint:all -Xdoclint:-missing -Xdoclint:-html That should fix the issue. ATTN: this must ONLY be done in a java8 profile! If you set those params in older java versions (1.7, 1.6) then the build will blow up... LieGrue, strub On Wednesday, 30 April 2014, 7:47, Paul Benedict wrote: Looks

Re: JDK8 compatible javadoc

2014-04-29 Thread Paul Benedict
Looks like I found the message I alluded to. Make sure you read the whole thread for fun ;-) http://mail.openjdk.java.net/pipermail/core-libs-dev/2013-July/019269.html On Wed, Apr 30, 2014 at 12:36 AM, Thomas Neidhart wrote: > On 04/30/2014 03:50 AM, Gary Gregory wrote: > > Well, it does not su

Re: JDK8 compatible javadoc

2014-04-29 Thread Thomas Neidhart
On 04/30/2014 03:50 AM, Gary Gregory wrote: > Well, it does not support HTML in the sense that you MUST close all tags. > No lonely s... Unless something has changed for jdk8, lonely s are supported and even advertised like this in the main javadoc guide from Sun/Oracle: http://www.oracle.com/tec

Re: JDK8 compatible javadoc

2014-04-29 Thread Paul Benedict
That's actually a really good point :-) On Tue, Apr 29, 2014 at 8:50 PM, Gary Gregory wrote: > Well, it does not support HTML in the sense that you MUST close all tags. > No lonely s... > > Gary > > > On Tue, Apr 29, 2014 at 9:35 PM, Paul Benedict > wrote: > > > JDK Javadoc only supports HTML.

Re: JDK8 compatible javadoc

2014-04-29 Thread Gary Gregory
Well, it does not support HTML in the sense that you MUST close all tags. No lonely s... Gary On Tue, Apr 29, 2014 at 9:35 PM, Paul Benedict wrote: > JDK Javadoc only supports HTML. It doesn't support XHTML. I remember > someone saying this on the OpenJDK lists but don't know where it is... bu

Re: JDK8 compatible javadoc

2014-04-29 Thread Paul Benedict
JDK Javadoc only supports HTML. It doesn't support XHTML. I remember someone saying this on the OpenJDK lists but don't know where it is... but I do remember that. On Tue, Apr 29, 2014 at 8:12 PM, Gary Gregory wrote: > Bernd, > > For paragraphs I use la di da, never the concept of a "line > sepa

Re: JDK8 compatible javadoc

2014-04-29 Thread Gary Gregory
Bernd, For paragraphs I use la di da, never the concept of a "line separator", that's a rendering concept IMO, not content, which is what Javadoc is. For code examples, then you end up in ... unless it's inline then you use {@code ...}. For IO-424, I've seen some discussion on the Maven ML and Ji

Re: JDK8 compatible javadoc

2014-04-29 Thread Bernd Eckenfels
Am Tue, 29 Apr 2014 20:19:03 -0400 schrieb Gary Gregory : > If you think XHTML/XML you should be fine. Hm, actually I dont know. It looks that neighter block (HTML) nor self-closing (XHTML) is valid/preferred. (So I plan to only use and as paragraph or line seperators.) BTW: Gary, did you fin

Re: JDK8 compatible javadoc

2014-04-29 Thread Gary Gregory
If you think XHTML/XML you should be fine. Gary On Tue, Apr 29, 2014 at 8:03 PM, Bernd Eckenfels wrote: > Hello, > > while running javadoc on VFS2 I get quite a few errors, especially > about self-closing (I can fix those) and (I am not sure how > to fix those). > > Is there any (ASF) JavaDoc

JDK8 compatible javadoc

2014-04-29 Thread Bernd Eckenfels
Hello, while running javadoc on VFS2 I get quite a few errors, especially about self-closing (I can fix those) and (I am not sure how to fix those). Is there any (ASF) JavaDoc guidelines which is recent enough to explain the JDK8 absudities? The Oracle Guide is outdated and actually recommends