You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2007/01/04 18:44:27 UTC

[jira] Created: (DERBY-2213) Support running Junit tests with just embedded jar file and testing jars.

Support running Junit tests with just embedded jar file and testing jars.
-------------------------------------------------------------------------

                 Key: DERBY-2213
                 URL: https://issues.apache.org/jira/browse/DERBY-2213
             Project: Derby
          Issue Type: Improvement
          Components: Test
            Reporter: Daniel John Debrunner


1) It's good to perform testing with different jvm classpaths, included those typically used, such as an embedded environment.

2) Running tests with platofrms such as J2ME/CDC/Foundation should be supported with the only  jars that the platform supports in the class path.

Currently running suites.All with just derby.jar hits this error:
Failed to invoke suite():java.lang.NoClassDefFoundError: org.apache.derby.client.am.SqlException


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (DERBY-2213) Support running Junit tests with just embedded jar file and testing jars.

Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463720 ] 

Daniel John Debrunner commented on DERBY-2213:
----------------------------------------------

Also works with WCTME 5.7 and just derby.jar from the set of derby jars.

> Support running Junit tests with just embedded jar file and testing jars.
> -------------------------------------------------------------------------
>
>                 Key: DERBY-2213
>                 URL: https://issues.apache.org/jira/browse/DERBY-2213
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Daniel John Debrunner
>         Assigned To: Daniel John Debrunner
>             Fix For: 10.3.0.0
>
>
> 1) It's good to perform testing with different jvm classpaths, included those typically used, such as an embedded environment.
> 2) Running tests with platofrms such as J2ME/CDC/Foundation should be supported with the only  jars that the platform supports in the class path.
> Currently running suites.All with just derby.jar hits this error:
> Failed to invoke suite():java.lang.NoClassDefFoundError: org.apache.derby.client.am.SqlException

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (DERBY-2213) Support running Junit tests with just embedded jar file and testing jars.

Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463407 ] 

Daniel John Debrunner commented on DERBY-2213:
----------------------------------------------

Revision 492822 allows suites.All to successfully run without debynet.jar and derbyclient.jar in the classpath.

> Support running Junit tests with just embedded jar file and testing jars.
> -------------------------------------------------------------------------
>
>                 Key: DERBY-2213
>                 URL: https://issues.apache.org/jira/browse/DERBY-2213
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Daniel John Debrunner
>         Assigned To: Daniel John Debrunner
>
> 1) It's good to perform testing with different jvm classpaths, included those typically used, such as an embedded environment.
> 2) Running tests with platofrms such as J2ME/CDC/Foundation should be supported with the only  jars that the platform supports in the class path.
> Currently running suites.All with just derby.jar hits this error:
> Failed to invoke suite():java.lang.NoClassDefFoundError: org.apache.derby.client.am.SqlException

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (DERBY-2213) Support running Junit tests with just embedded jar file and testing jars.

Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel John Debrunner closed DERBY-2213.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.3.0.0

Revision 494951 enables suites.All to be run with just derby.jar from the set of derby jars. Tested with jdk 1.5

> Support running Junit tests with just embedded jar file and testing jars.
> -------------------------------------------------------------------------
>
>                 Key: DERBY-2213
>                 URL: https://issues.apache.org/jira/browse/DERBY-2213
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Daniel John Debrunner
>         Assigned To: Daniel John Debrunner
>             Fix For: 10.3.0.0
>
>
> 1) It's good to perform testing with different jvm classpaths, included those typically used, such as an embedded environment.
> 2) Running tests with platofrms such as J2ME/CDC/Foundation should be supported with the only  jars that the platform supports in the class path.
> Currently running suites.All with just derby.jar hits this error:
> Failed to invoke suite():java.lang.NoClassDefFoundError: org.apache.derby.client.am.SqlException

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Assigned: (DERBY-2213) Support running Junit tests with just embedded jar file and testing jars.

Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel John Debrunner reassigned DERBY-2213:
--------------------------------------------

    Assignee: Daniel John Debrunner

> Support running Junit tests with just embedded jar file and testing jars.
> -------------------------------------------------------------------------
>
>                 Key: DERBY-2213
>                 URL: https://issues.apache.org/jira/browse/DERBY-2213
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Daniel John Debrunner
>         Assigned To: Daniel John Debrunner
>
> 1) It's good to perform testing with different jvm classpaths, included those typically used, such as an embedded environment.
> 2) Running tests with platofrms such as J2ME/CDC/Foundation should be supported with the only  jars that the platform supports in the class path.
> Currently running suites.All with just derby.jar hits this error:
> Failed to invoke suite():java.lang.NoClassDefFoundError: org.apache.derby.client.am.SqlException

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira