db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2309) Seperating Each Task for the ease of tracking and fixing
Date Thu, 08 Feb 2007 22:54:05 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471514

Daniel John Debrunner commented on DERBY-2309:

I believe the one jar makes life easier. With two jars the security policy file will have
to have an extra section, as it would be good to have these tests running under the security
manager at some point. The OETest being already packaged in derbyTesting jar file has worked
well for me so far.

Also since we don't provide any ability to download individual jars there's no benefit there.

> Seperating Each Task for the ease of tracking and fixing
> --------------------------------------------------------
>                 Key: DERBY-2309
>                 URL: https://issues.apache.org/jira/browse/DERBY-2309
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>    Affects Versions:
>            Reporter: Manjula Kutty
>         Assigned To: Manjula Kutty
>            Priority: Minor
>             Fix For:
> Place holder for adding build.xml. Also I propose here to create derbySysTest.jar instead
of putting all the system test classes in the derbyTesting.jar. By doing that people who wish
to run the system test only need to download them. All comments and suggestions are welcome

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

View raw message