[
https://issues.apache.org/jira/browse/DERBY-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471519
]
Andrew McIntyre commented on DERBY-2309:
----------------------------------------
Big +1 to a single jar. I'd move dynamic generation of the test resources up
the list of todos, though, because inclusion of the resource jars will almost
double the size of derbyTesting.jar. Considering that we include
derbyTesting.jar in all the release distributions, that's a lot of overhead for
nothing.
Maven projects can and do download the Derby jars individually from the various
maven repositories, but I don't think there would be many maven users who would
be interested in including just our system tests in their projects. :-)
> 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.
