[ https://issues.apache.org/jira/browse/PIVOT-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985235#comment-15985235 ]
Roger Whitcomb commented on PIVOT-996: -------------------------------------- Okay, make a version simple change to Version.java to account for this specific case, and added a test method to VersionTest to test it. "trunk": Sending core\src\org\apache\pivot\util\Version.java Sending core\test\org\apache\pivot\util\test\VersionTest.java Transmitting file data ..done Committing transaction... Committed revision 1792775. "branches/2.0.x": Sending . Sending core\src\org\apache\pivot\util\Version.java Sending core\test\org\apache\pivot\util\test\VersionTest.java Transmitting file data ..done Committing transaction... Committed revision 1792783. > 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)