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

ASF GitHub Bot commented on TAMAYA-349:
---------------------------------------

GitHub user acoburn opened a pull request:

    https://github.com/apache/incubator-tamaya/pull/24

    TAMAYA-349: Ensure Tamaya builds on JDK 11

    This updates the Javadoc plugin to 3.0.1 and the JaCoCo plugin to 0.8.2. It 
also fixes a javadoc tag that, apparently, is not valid under JDK 11.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/acoburn/incubator-tamaya TAMAYA-349

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-tamaya/pull/24.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #24
    
----
commit 67777536b919b5bd90fbda2bd09bac2abc210f42
Author: Aaron Coburn <acoburn@...>
Date:   2018-09-12T12:39:45Z

    TAMAYA-349: Ensure Tamaya builds on JDK 11

----


> Ensure that Tamaya builds properly on JDK 11
> --------------------------------------------
>
>                 Key: TAMAYA-349
>                 URL: https://issues.apache.org/jira/browse/TAMAYA-349
>             Project: Tamaya
>          Issue Type: Improvement
>          Components: API, Extensions, Sandbox
>    Affects Versions: 0.3-incubating
>            Reporter: Aaron Coburn
>            Priority: Major
>             Fix For: 0.4-incubating
>
>
> When JDK 11 is released, it will be the new LTS platform, so it is important 
> that Tamaya can be built with JDK11. I can confirm that Tamaya 0.3-incubating 
> currently *runs* fine on JDK 11, but there appear to be some minor issues 
> with the maven javadoc plugin that prevent it from building properly on JDK 
> 11. The JaCoCo plugin version could also be updated to 0.8.2, which supports 
> JDK 11.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to