[ https://issues.apache.org/jira/browse/DERBY-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-3149: ----------------------------------- Derby Info: (was: [Patch Available]) Committed 'derby-3149-1b.diff' to trunk with revision 593571. I'm not marked the issue as resolved yet, because there are a few things that must be cleaned-up, and it would also be nice if someone tested the targets ('pptesting', 'junit-pptesting'). Targets are now dependent on Java SE 6, which they don't have to be. This is because I couldn't find a compile classpath for Java SE 5.0. Maybe this has already been introduced? > Add ant targets for building and running the package private tests against > the classes directories > -------------------------------------------------------------------------------------------------- > > Key: DERBY-3149 > URL: https://issues.apache.org/jira/browse/DERBY-3149 > Project: Derby > Issue Type: Sub-task > Components: Build tools, Test > Affects Versions: 10.4.0.0 > Reporter: Kristian Waagan > Assignee: Kristian Waagan > Priority: Minor > Fix For: 10.4.0.0 > > Attachments: derby-3149-1a.diff, derby-3149-1a.stat, > derby-3149-1b.diff > > > Create ant targets in build.xml to compile and run the package private tests. > The first step will be to run the tests against the classes directories. > Implementing a solution that runs against jars is not technically difficult, > it just brings a host of decisions to be taken... Maybe even more important, > does running against the jars add any value? > The compile will be included in the 'all' target to test the implementation. > Feel free to post your concerns if you think building the package private > tests should be a manual action only. > The tests will also be run as part of junit-all / junitreport. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.