jtreg has long contained an Ant task, so that it can be invoked directly from Ant.
The task has never (ever?) been widely used, and these days there are other more dominant ways to invoke jtreg:
1. The JDK "make test" system
2. Running individual tests from within an IDE
3. Direct invocation of jtreg, perhaps using custom personal scripts.
The Ant task has been updated in a long time, and there have been no requests to do so, especially to support more recent command-line options.
We should remove the Ant task. jtreg can still be invoked from Ant, using either the `<java>` task to invoke the tool directly, or the `<exec>` task to invoke the script.
Given the recent removal of the Ant build (CODETOOLS-7903104), removing the Ant task will mean we can drop Ant as a build dependence.
The task has never (ever?) been widely used, and these days there are other more dominant ways to invoke jtreg:
1. The JDK "make test" system
2. Running individual tests from within an IDE
3. Direct invocation of jtreg, perhaps using custom personal scripts.
The Ant task has been updated in a long time, and there have been no requests to do so, especially to support more recent command-line options.
We should remove the Ant task. jtreg can still be invoked from Ant, using either the `<java>` task to invoke the tool directly, or the `<exec>` task to invoke the script.
Given the recent removal of the Ant build (
- relates to
-
CODETOOLS-7903287 Remove left-over obsolete support for Ant task
-
- Resolved
-
