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

Posted to dev@pivot.apache.org by "Sandro Martini (JIRA)" <ji...@apache.org> on 2017/04/25 20:23:04 UTC

[jira] [Commented] (PIVOT-996) Unable to run with SAP JVM

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

Sandro Martini commented on PIVOT-996:
--------------------------------------

This is not directly related to changes of PIVOT-933 (just resolved), but maybe a more general solution could be good to handle all cases.

> Unable to run with SAP JVM
> --------------------------
>
>                 Key: PIVOT-996
>                 URL: https://issues.apache.org/jira/browse/PIVOT-996
>             Project: Pivot
>          Issue Type: Bug
>    Affects Versions: 2.0.4
>            Reporter: Sandro Martini
>            Assignee: Sandro Martini
>             Fix For: 2.0.5, 2.1.0
>
>
> As reported in our Dev mailing list, the check on JVM version that we do doesn't work with JVM different than Oracle Java.
> For example the SAP JVM with version "8.1.028 25.51-b14" generates the problem, which is blocking.
> The discussion thread is visible for example [here](http://apache-pivot-developers.417237.n3.nabble.com/Issue-in-Version-decode-with-SAPJVM-td4027425.html).
> We should check if log a warning and continue the execution, or parse anything after he major.minor.patch as a string ...



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)