[ 
https://issues.apache.org/jira/browse/DERBY-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555851#action_12555851
 ] 

Kristian Waagan commented on DERBY-3149:
----------------------------------------

Regarding why junit-pptesting isn't adding junit.jar automatically, I'm not 
quite sure.

I experimented a little bit, but it seems that with my ant version (1.6.5) 
adding the jar in the target isn't enough. Even if I add tools/java/junit.jar 
to the classpath for target junit-pptesting I'm not able to run it without 
already having told ant where to find it (I currently have a junit.jar in 
~/.ant/lib). I think ant needs junit.jar to "initialize" the junit task. 

I know this area is a bit tricky with ant, and they also have a FAQ-entry for 
it: http://ant.apache.org/faq.html#delegating-classloader-1.6
Maybe ant 1.7 solves the problem for us, but we only require 1.6.3 (or higher) 
to build Derby.

It would be nice if someone knowing ant well could help find the best way to do 
this.

> 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, derby-3149-2a-conditional_compilation_fix.diff, 
> derby-3149-2b-conditional_compilation_fix.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.

Reply via email to