db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vemund Østgaard (JIRA) <j...@apache.org>
Subject [jira] Updated: (DERBY-2277) Make it possible to run the testsuite with jdk1.7
Date Tue, 06 Feb 2007 12:25:05 GMT

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

Vemund Østgaard updated DERBY-2277:
-----------------------------------

    Attachment: 2277-diff2.stat
                2277-diff2

Thank you, Myrna.

I've added a patch that makes the apporipriate modifications to java/testing/README.html,
documenting that jdk17 has been added. I also made a change to the README saying that jdk16
is now the default jvm if the testsuite is run with an "unknown" jvm, as this was changed
in JIRA2279.

I have one question, however, related to how the README.htm explains running the testsuite
with a new jvm. The documentation says that you should first just run the testsuite, and if
everything works ok you do not have to do anything. If behaviour is different with this jvm,
though, you may have to:
"create a subclass of
org.apache.derbyTesting.functionTests.harness.jvm. In this class,
specify any jvm specific property settings required"

Now, I found that this class was needed to be able to execute the testsuite at all, or I got
a ClassNotFoundException. Did I stumble on a bug, or should the documentation be changed to
say that you must always create a new subclass of harness.jvm when running with a new jvm?

> Make it possible to run the testsuite with jdk1.7
> -------------------------------------------------
>
>                 Key: DERBY-2277
>                 URL: https://issues.apache.org/jira/browse/DERBY-2277
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>         Environment: jdk1.7
>            Reporter: Vemund Østgaard
>         Assigned To: Vemund Østgaard
>            Priority: Trivial
>         Attachments: 2277-diff, 2277-diff.stat, 2277-diff2, 2277-diff2.stat
>
>
> Today if you try to run the testsuite with jdk1.7 you get a ClassNotFoundException:
> Process exception: java.lang.ClassNotFoundException: org.apache.derbyTesting.functionTests.harness.jdk17
> Exception in thread "main" java.lang.ClassNotFoundException: org.apache.derbyTesting.functionTests.harness.jdk17
>    at java.net.URLClassLoader$1.run(URLClassLoader.java:203)
>    at java.security.AccessController.doPrivileged(Native Method)
>    at java.net.URLClassLoader.findClass(URLClassLoader.java:191)
>    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
>    at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
>    at java.lang.Class.forName0(Native Method)
>    at java.lang.Class.forName(Class.java:169)
>    at org.apache.derbyTesting.functionTests.harness.jvm.getJvm(Unknown Source)
>    at org.apache.derbyTesting.functionTests.harness.RunTest.buildTestCommand(Unknown
Source)
>    at org.apache.derbyTesting.functionTests.harness.RunTest.testRun(Unknown Source)
>    at org.apache.derbyTesting.functionTests.harness.RunTest.main(Unknown Source) 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message