[ 
https://issues.apache.org/jira/browse/CURATOR-523?focusedWorklogId=286654&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-286654
 ]

ASF GitHub Bot logged work on CURATOR-523:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 01/Aug/19 11:54
            Start Date: 01/Aug/19 11:54
    Worklog Time Spent: 10m 
      Work Description: asdf2014 commented on pull request #321: CURATOR-523: 
Fix ByteBuffer's compatibility issues
URL: https://github.com/apache/curator/pull/321
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 286654)
            Time Spent: 10m
    Remaining Estimate: 0h

> Use --release flag when compiling on JDK9+
> ------------------------------------------
>
>                 Key: CURATOR-523
>                 URL: https://issues.apache.org/jira/browse/CURATOR-523
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: 4.2.0
>            Reporter: Paco
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> From the manifest 4.2.0 jars are compiled with jdk11:
> {{Build-Jdk: 11.0.2 }}
> Changes to covariant return types for {{ByteBuffer}} in JDK11 cause a 
> {{java.lang.NoSuchMethodError}} at runtime when running on JDK 8. These calls 
> paths are impacted:
> [https://github.com/apache/curator/blob/master/curator-framework/src/main/java/org/apache/curator/framework/imps/GzipCompressionProvider.java#L307-L319]
> This can be mitigated by setting the {{--release}} to 8.
> [http://openjdk.java.net/jeps/247]
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to