You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2013/02/22 10:10:13 UTC

[jira] [Commented] (DERBY-6087) Can't build Javadoc with JDK 1.8 if explicit j5lib, j6lib and j7lib paths are set

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

Knut Anders Hatlen commented on DERBY-6087:
-------------------------------------------

The patch seems to do the right thing in my environment. +1
                
> Can't build Javadoc with JDK 1.8 if explicit j5lib, j6lib and j7lib paths are set
> ---------------------------------------------------------------------------------
>
>                 Key: DERBY-6087
>                 URL: https://issues.apache.org/jira/browse/DERBY-6087
>             Project: Derby
>          Issue Type: Bug
>          Components: Build tools, Javadoc
>            Reporter: Dag H. Wanvik
>            Assignee: Dag H. Wanvik
>            Priority: Minor
>         Attachments: derby-6087.diff
>
>
> We set these library properties to get better compile time checking of old level source using too new  library contents. We should be able to build the Javadoc without unsetting them. It works with a JDK 1.7.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira