db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (DERBY-6860) Automatic download of junit.jar broken
Date Thu, 04 Feb 2016 10:15:39 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Knut Anders Hatlen closed DERBY-6860.
       Resolution: Fixed
    Fix Version/s:

> 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:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>             Fix For:
> 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:
> /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

View raw message