Home/ Questions/Q 6217969
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T07:31:06+00:00

Here’s the situation: I trying to make a ant test script that does the

  • 0

Here’s the situation: I trying to make a ant test script that does the following
1 – Runs a utility to create test data
2 – Runs junit suite
3 – Runs a utility to clean up test data.

The problems is parts 2 & 3 need to access to some static fields of the utility in 1 (e.g. generated unique names of test data). This issue I’m having is that it the static fields of the class are null when I try to access them as though the java task in #1 was run in a separate process or using a different classloader (I’ve tried setting the attribute fork=”false” on the java task and using -Dant.reuse.loader=true on the cmd line). Any ant gurus know what’s going on here?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Since you are dealing with different class loaders, you’ll never get past one’s class loader finding the “wrong” instance of the exact same class and hence using the “wrong” static value. You need to do the communications between the ant invocations via a file. A temporary file will likely not do, as it will likely be removed before the second set of ant classes get a chance to work with it.

    There are two issues, the generation of suitable property values, and the transmission of them between ant calls. Perhaps you don’t need all of this since your situation might already generate suitable identifiers, but it’s here if you do.

    To generate suitable values, one ant process should the propertyfile task to generate the appropriate names, with the per-run changing identifier as part of the name

    <propertyfile file="testConfig.properties.ids" comment="Machine generated file, do not edit!">
  <entry key="test.suite.1.id" type="int" operation="+" unit="1"/>
  <entry key="test.suite.2.id" type="int" operation="+" unit="1"/>
</propertyfile>
<properties file="testConfig.properties.ids"/>
<propertyfile file="testConfig.properties" comment="Machine generated file, do not edit!">
  <entry key="test.suite.1.name" type="string" operation="=" value="TestSuite${test.suite.1.id}.sh"/>
  <entry key="test.suite.2.name" type="string" operation="=" value="TestSuite${test.suite.2.id}.sh"/>
</propertyfile>

    Subsequent ant processes can then just source in the original ant process’s generated property file.

    <property file="testConfig.properties"/>

    Which will have the effect of defining

    test.suite.1.name=TestSuite34.sh
test.suite.2.name=TestSuite83.sh
    • 0