db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajesh Kartha (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:43:05 GMT

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

Rajesh Kartha commented on DERBY-2309:
--------------------------------------

Any idea by how much the size will increase if we add all these tests to derbyTesting,jar
?  I too was inclined keeping them separate, but on second thoughts, wouldn't keeping all
the Derby testing binaries in derbyTesting.jar avoid any confusion about keeping separate
testing jar files ?



> 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: 10.3.0.0
>            Reporter: Manjula Kutty
>         Assigned To: Manjula Kutty
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>
> 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.


Mime
View raw message