[External] : Re: valid tags for jtreg-6+1

[Jonathan Gibbons]

Vitaly,

I have pushed changes to the makefiles so that you can build jtreg with 
JDK 11, and run all the tests that don't rely on pre-module system features.

-- Jon


On 6/9/21 9:24 AM, Jonathan Gibbons wrote:
> Vitaly,
>
> Yes, I see and can recreate your issue when using JDK 11 to build 
> jtreg. We normally use JDK 8 to build jtreg, so that we can use jtreg 
> for older systems.  You might try that until I can fix the code to be 
> compilable with 11 and later.
>
> -- Jon
>
>
> On 6/8/21 3:39 PM, Vitaly Provodin wrote:
>> Jon,
>>
>> Thanks for the reply.
>>
>> I tried building with make/build.sh but got an error. The tail of the 
>> building log looks like (full log was attached)
>> —————————8<—————————
>> ../src/share/classes/com/sun/javatest/regtest/agent/StringArray.java:142: 
>> warning: [rawtypes] found raw type: Vector
>>         Vector v = new Vector();
>>                        ^
>>   missing type arguments for generic class Vector<E>
>>   where E is a type-variable:
>>     E extends Object declared in class Vector
>> ../src/share/classes/com/sun/javatest/regtest/agent/StringArray.java:158: 
>> warning: [unchecked] unchecked call to addElement(E) as a member of 
>> the raw type Vector
>>             v.addElement(s.substring(tokenStart, tokenEnd));
>>                         ^
>>   where E is a type-variable:
>>     E extends Object declared in class Vector
>> 1 error
>> 40 warnings
>> make: *** 
>> [/Users/vprovodin/workspace/github/jtreg/build/classes.com.sun.javatest.regtest-othervm.ok] 
>> Error 1
>> —————————8<—————————
>>
>> Unfortunately I could not catch the cause of this error (so far)
>>
>>
>> Thanks,
>> Vitaly
>>
>> > On 8 Jun 2021, at 22:01, Jonathan Gibbons 
>> <jonathan.gibbons at oracle.com> wrote:
>> >
>> > Vitaly,
>> >
>> > The format for the tags has changed to be in line with the format 
>> for JDK tags.  The format is `jtreg-VERSION+BUILD`. The tag for the 
>> latest recommended version is `jtreg-6+1`. It is the only (and thus 
>> latest) tag matching the new form.
>> >
>> > Also, make sure you are using the new `make/build.sh` script (or 
>> driving the Makefile directly) and not the older `make/build-all.sh` 
>> script which will be removed in the next update.
>>