New jtreg version numbers

[Jonathan Gibbons]

Peter,

As things currently stand, no, we do not publish jtreg to Maven 
Central.  The Adopt OpenJDK group provides builds, or you can easily 
build it yourself with the `make/build-all.sh` script, which just 
requires JDK 8 or later.

-- Jon

On 2/11/20 9:52 PM, Peter Firmstone wrote:
> Hi Jon,
>
> A little off topic, but any chance of publishing jtreg 5.0 on Maven 
> Central?
>
> Cheers,
>
> Peter.
>
>
> On 2/12/2020 7:05 AM, Jonathan Gibbons wrote:
>> For folk that build jtreg from source, jtreg 5.0 has now been tagged 
>> in the repo.
>>
>> -- Jon
>>
>> On 2/5/20 2:12 PM, Jonathan Gibbons wrote:
>>> This is FYI for folk that use the OpenJDK Regression Test Harness, 
>>> jtreg, to run OpenJDK tests.
>>>
>>> For the past few years, jtreg has used a version numbering scheme 
>>> "4.2 bNN" where NN slowly incremented, instead of a more 
>>> conventional "$MAJOR.$MINOR" numbering scheme. The reasons for this 
>>> choice have long since disappeared, and so going forward, jtreg will 
>>> use a "$MAJOR.$MINOR" numbering scheme, starting with 5.0.
>>>
>>> Along with this change, jtreg will also require JDK 8 or later to 
>>> compile and execute it.  That should not affect most people, for 
>>> whom JDK 8 or later has long been recommended, although not 
>>> required.  In the unlikely event that we need to fix an issue in a 
>>> version of jtreg that can run on JDK 7, we can provide an update 
>>> based on the latest 4.2 version.
>>>
>>> For those folk that build jtreg from the tip of the repo, you may 
>>> notice the related changes in the repo.
>>>
>>> -- Jon
>>>