You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2016/01/28 15:52:40 UTC

[jira] [Created] (DERBY-6860) Automatic download of junit.jar broken

Knut Anders Hatlen created DERBY-6860:
-----------------------------------------

             Summary: 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)