You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Aditya Dhulipala (JIRA)" <ji...@apache.org> on 2015/03/06 04:47:38 UTC

[jira] [Commented] (OODT-823) OODT JDK8 Maven3 build errors

    [ https://issues.apache.org/jira/browse/OODT-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14349905#comment-14349905 ] 

Aditya Dhulipala commented on OODT-823:
---------------------------------------

Hi,

I've been reading up on this issue and found a quick fix
http://stackoverflow.com/questions/15886209/maven-is-not-working-in-java-8-when-javadoc-tags-are-incomplete

JDK8 introduces DocLint to catch javadoc error early in the development cycle. Mvn3 raises errors when installing.
A quick fix is to specify -Xdoclint:none as an additional param.

I tried this and the mvn install worked fine using mvn3 on jdk8.

However, I did find some new issues. 
The mvn install now fails for building 'Catalog and Archive Resource Management Component'

I will look into the surefire reports  (and also post it on the dev list) shortly.

My question regarding this issue is as follows:

Since this fixes the javadoc error, is it a good fix to OODT-823? Can I submit this as a patch?

Or should we open a new issue where we rewrite all the javadoc to conform to the JDK8 doclint?


Thanks!

--
aditya

> OODT JDK8 Maven3 build errors
> -----------------------------
>
>                 Key: OODT-823
>                 URL: https://issues.apache.org/jira/browse/OODT-823
>             Project: OODT
>          Issue Type: Bug
>          Components: build proces
>    Affects Versions: 0.8
>         Environment: OS X Yosemite. maven 3 with JDK8
>            Reporter: Aditya Dhulipala
>            Priority: Minor
>
> OODT build fails when using maven 3 with jdk8. Specifically while generating javadocs (the javadoc compiler that ships with JDK8 throws errors if the javadoc does not conform to the format prescribed for javadocs under jdk8)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)