[
https://issues.apache.org/jira/browse/DERBY-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656159#comment-13656159
]
Mike Matrigali commented on DERBY-6222:
---------------------------------------
Here is the related conversation, seems very hard to do anything other than
fail on the byte code error as rick explains:
On 5/10/13 12:16 PM, Mike Matrigali wrote:
> thanks for the explanation, didn't realize it was going to be so dramatic. I
> am actually less worried if this is the case, what I did
> not want to happen is for someone to seemingly boot fine and then just
> have stuff mysteriously fail.
>
> If someone has a easy good idea, fine, but not worth much effort. At a
> minimum we should just cut/paste the various errors you get when you try
> to boot on wrong jvm into a release note and a JIRA entry so that a search on
> the error could lead someone quickly to understanding what is
> going on. I'll add this todo to the release note issue I posted and
> can take on the work once we are much closer to having a 10.11 release
> with all the changes in.
Thanks, Mike. That sounds like a good idea.
>
> On 5/10/2013 11:39 AM, Rick Hillegas wrote:
>> On 5/10/13 11:17 AM, Mike Matrigali wrote:
>>> If it is not too hard I wonder if we should disable derby from booting
>>> if the jvm is not 1.6 or higher, with hopefully a clear message saying
>>> why the boot is failing.
>>>
>>>
>> Hi Mike,
>>
>> I'm not sure we can do much here. The compiled Derby byte code will be
>> Java 6 byte code. If you try to run Java 6 byte code on an older VM you
>> will get a java.lang.UnsupportedClassVersionError. This error is raised
>> as the VM tries to load Derby, that is, long before we have an
>> opportunity to inject an explanatory message.
>>
>> But perhaps someone else has a clever idea.
>>
>> Thanks,
>> -Rick
>>
>
> add release note for 10.11 noting that using a JVM previous to jdk1.6 will
> not work
> -----------------------------------------------------------------------------------
>
> Key: DERBY-6222
> URL: https://issues.apache.org/jira/browse/DERBY-6222
> Project: Derby
> Issue Type: Task
> Reporter: Mike Matrigali
> Priority: Blocker
>
> We should add a release note to make it clear that using a JVM prior to 1.6
> will not work. The
> language should be stronger than "is not supported" as I believe derby
> functionality will break in
> unknown ways if version 10.11 is used with a JVM prior to 1.6. This is as
> expected and was
> approved by community vote, just should make it very clear when 10.11 is
> released.
> I am not sure exactly what the problems will be, but note that the derby
> tests already have failures
> when run against ibm15, and have been disabled.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
