updating TestNG and JUnit for jtreg
martinrb at google.com
Wed May 4 20:49:38 UTC 2016
Thanks! I was able to successfully build jtreg4.2-b02.
One thing I keep stumbling over is the need to update BUILD_NUMBER in
my scripts that build jtreg.
The makefiles have BUILD_NUMBER = b00, but that has to be overridden
at make time or the jtreg version check will fail later. It's a nice
service to your users to update BUILD_NUMBER in the source code before
creating the hg release tag (or abandon build numbers entirely).
(OTOH, other openjdk builds have the same problem)
On Tue, May 3, 2016 at 6:28 PM, Jonathan Gibbons
<jonathan.gibbons at oracle.com> wrote:
> The recent updates to jdk9/dev will require the version of jtreg tagged as
> This has the same dependency requirements as the previous build, and all
> versions of jtreg4.1,
> meaning, if you could build it before, you should be able to build
> jtreg4.2-b02 the same way.
> Going forward, the next update to jtreg will require the following:
> * built with JDK 7 or later
> * TestNG 6.9.5 or later
> * JUnit 4.10 or later
> * JTHarness 4.6 or later
> These updates will enable a number of bug fixes and enhancements that have
> been blocked until now.
> Those folk that build jtreg may need to update their build scripts or build
> Patches to make these changes are now in the jtreg repository.
> -- Jon
> On 04/15/2016 08:41 AM, Jonathan Gibbons wrote:
>> This is a heads-up for those folk that build their own copy of jtreg,
>> especially folk outside Oracle.
>> We are looking up update jtreg and the tests such that they will require
>> the following versions:
>> TestNG 6.9.5
>> JUnit 4.10
>> This will allow tests to use newer API in TestNG, and will facilitate
>> improved support for JUnit tests, using TestNG mixed mode.
>> Separately, we know that the external builds on cloudbees are broken, and
>> we are working to get that situation addressed.
>> -- Jon
More information about the jtreg-use