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

Knut Anders Hatlen commented on DERBY-6860:
-------------------------------------------

git bisect says:

5d1f9f03c2741809d15ef482ac2a7989607970dc is the first bad commit
commit 5d1f9f03c2741809d15ef482ac2a7989607970dc
Author: Richard N. Hillegas <rhille...@apache.org>
Date:   Tue Jan 26 02:42:00 2016 +0000

    DERBY-6857: Replace hardcoded references to 1.8 in the build scripts with a 
min.version constant; commit derby-6857-03-aa-minimumVersion.diff.
    
    git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1726721 
13f79535-47bb-0310-9956-ffa450edef68

> Automatic download of junit.jar broken
> --------------------------------------
>
>                 Key: DERBY-6860
>                 URL: https://issues.apache.org/jira/browse/DERBY-6860
>             Project: Derby
>          Issue Type: Bug
>          Components: Build tools
>    Affects Versions: 10.13.0.0
>            Reporter: Knut Anders Hatlen
>
> Automatic download of junit.jar seems to be broken. If you don't already have 
> a copy in tools/java, "ant all" fails like this:
> {noformat}
> junit_check:
> BUILD FAILED
> /code/derby/trunk/build.xml:66: The following error occurred while executing 
> this line:
> /code/derby/trunk/build.xml:177: junit property is set to 
> /code/derby/trunk/tools/java/junit.jar, but there is no junit.jar there.
> {noformat}
> The problem seems to be that junit_check refuses to continue if the junit 
> property is set, but does not point to an existing file. This property is set 
> when the setCompilerProperties target, which runs before junit_check, loads 
> tools/ant/properties/extrapath.properties, as extrapath.properties contains 
> the following line:
> {noformat}
> junit=${javatools.dir}/junit.jar
> {noformat}
> Since the install_junit target depends on the check_junit target, this 
> prevents the build script from downloading junit.jar automatically.
> Workaround: run "ant install_junit" before "ant all"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to