You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2014/06/17 10:37:02 UTC

[jira] [Created] (JENA-716) Build breaks when in a java8 only environment.

Andy Seaborne created JENA-716:
----------------------------------

             Summary: Build breaks when in a java8 only environment.
                 Key: JENA-716
                 URL: https://issues.apache.org/jira/browse/JENA-716
             Project: Apache Jena
          Issue Type: Bug
          Components: Build
    Affects Versions: Jena 2.11.2
         Environment: java 1.8.0_05
            Reporter: Andy Seaborne


See http://stackoverflow.com/questions/15886209/maven-is-not-working-in-java-8-when-javadoc-tags-are-incomplete

The build breaks (in jena-iri) when java8 used as the setting of JAVA_HOME.




--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: [jira] [Created] (JENA-716) Build breaks when in a java8 only environment.

Posted by Andy Seaborne <an...@apache.org>.
This is madness.

One error and nothing is produced.
One warning and maven fails the build.

And even when it's Java 1.7 source code, it breaks with a java8 compiler.

http://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-javadoc.html

To say the Jena build is comprehensive broken is an understatement.

It is ridiculously picky -

1/ <br/> ILLEGAL!

2/ all @params, @returns, @throws MUST be present.

3/ <table> without summary is illegal.

4/ ">" (which is OK to all browsers -- only "<" must be escaped)

5/ And other stuff I keep coming across.

Yes - doclint can be turned off - but -Xdoclint:none is illegal to java7 
javadoc.

The only way to preserve the build is to turn doclint off ... which 
defeats the purpose.

Which I have done in jena-parent, conditional of java8+.


BUT even then the build breaks:

A/ Mythical javadoc (merely 100 warnings)

.../jena/ontology/OntProperty.java:483: warning - @propertyDescription 
is an unknown tag.

Yes - it's unknown.  It is also NOT IN THE FILE.

.../jena/ontology/OntProperty.java:483: warning - Tags @propertyGetter, 
@propertySetter and @propertyDescription can only be used in JavaFX 
properties getters and setters.

which does not occur in the code code.


B/ ... in ARQ ...

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process 
(default) on project jena-arq: Error rendering velocity resource. 
NullPointerException -> [Help 1]

	Andy


On 17/06/14 09:37, Andy Seaborne (JIRA) wrote:
> Andy Seaborne created JENA-716:
> ----------------------------------
>
>               Summary: Build breaks when in a java8 only environment.
>                   Key: JENA-716
>                   URL: https://issues.apache.org/jira/browse/JENA-716
>               Project: Apache Jena
>            Issue Type: Bug
>            Components: Build
>      Affects Versions: Jena 2.11.2
>           Environment: java 1.8.0_05
>              Reporter: Andy Seaborne
>
>
> See http://stackoverflow.com/questions/15886209/maven-is-not-working-in-java-8-when-javadoc-tags-are-incomplete
>
> The build breaks (in jena-iri) when java8 used as the setting of JAVA_HOME.
>
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.2#6252)
>