You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tubemq.apache.org by "viviel (Jira)" <ji...@apache.org> on 2020/05/15 08:49:00 UTC

[jira] [Resolved] (TUBEMQ-108) About maven jdk version configuration problem

     [ https://issues.apache.org/jira/browse/TUBEMQ-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

viviel resolved TUBEMQ-108.
---------------------------
    Resolution: Fixed

> About maven jdk version configuration problem
> ---------------------------------------------
>
>                 Key: TUBEMQ-108
>                 URL: https://issues.apache.org/jira/browse/TUBEMQ-108
>             Project: Apache TubeMQ
>          Issue Type: Improvement
>            Reporter: viviel
>            Assignee: viviel
>            Priority: Minor
>
> hi:
> [~gosonzhang], [~technoboy]
> I found some problems with the current maven jdk version configuration. For the 1.8 syntax, it can be compiled, but there will be problems during runtime.
> for example:
> The core module uses the syntax of 1.8. If you refer to the method that is only available in 1.8, it can be compiled. However, because the server is configured with the syntax of 1.7, when the server is running on jdk1.7, it will caused method not found errors because it depends on the core module.
> In response to this problem, please ask [~gosonzhang] to determine the specific jdk running version of the server and client module, so as to make corresponding adjustments to the maven configuration. When the syntax is wrong, you can find and solve the problem in time during compilation



--
This message was sent by Atlassian Jira
(v8.3.4#803005)