From jonathan.gibbons at oracle.com  Tue Jan  7 11:22:51 2014
From: jonathan.gibbons at oracle.com (Jonathan Gibbons)
Date: Tue, 07 Jan 2014 11:22:51 -0800
Subject: CFV: New Code-Tools Committer: Mike Duigou
Message-ID: <52CC540B.2090808@oracle.com>

|I hereby nominate Mike Duigou to Code-Tools Committer.

Mike is a well-known OpenJDK contributor (committer and reviewer) of 
long standing, and helps out on infrastructure stuff as well as the main 
code base. This includes contributions to jtreg and webrev, both now in 
the Code Tools project.

Votes are due by Tuesday, January 21, 2014. Only current Code-Tools 
Committers [1] are eligible to vote on this nomination. Votes must be 
cast in the open by replying to to this mailing list.

For Lazy Consensus voting instructions, see [2].

Jonathan Gibbons

[1] http://openjdk.java.net/census
[2] http://openjdk.java.net/projects/#committer-vote|

From mark.reinhold at oracle.com  Tue Jan  7 14:13:35 2014
From: mark.reinhold at oracle.com (mark.reinhold at oracle.com)
Date: Tue, 07 Jan 2014 14:13:35 -0800
Subject: CFV: New Code-Tools Committer: Mike Duigou
In-Reply-To: <52CC540B.2090808@oracle.com>
References: <52CC540B.2090808@oracle.com>
Message-ID: <20140107141335.445288@eggemoggin.niobe.net>

Vote: yes

- Mark

From iris.clark at oracle.com  Tue Jan  7 14:28:01 2014
From: iris.clark at oracle.com (Iris Clark)
Date: Tue, 7 Jan 2014 14:28:01 -0800 (PST)
Subject: CFV: New Code-Tools Committer: Mike Duigou
In-Reply-To: <52CC540B.2090808@oracle.com>
References: <52CC540B.2090808@oracle.com>
Message-ID: <1fbfc99d-9bb3-4f58-9795-655edb042d53@default>

Vote: yes

iris

From kevin.looney at oracle.com  Tue Jan  7 15:29:00 2014
From: kevin.looney at oracle.com (Kevin Looney)
Date: Tue, 07 Jan 2014 15:29:00 -0800
Subject: CFV: New Code-Tools Committer: Mike Duigou
In-Reply-To: <52CC540B.2090808@oracle.com>
References: <52CC540B.2090808@oracle.com>
Message-ID: <52CC8DBC.9070506@oracle.com>

Vote: yes


Kevin L


From sadhak001 at gmail.com  Sat Jan 18 05:34:01 2014
From: sadhak001 at gmail.com (Mani Sarkar)
Date: Sat, 18 Jan 2014 13:34:01 +0000
Subject: jtreg nightly build version change
In-Reply-To: <CAP7YuASpwrA-2fLQxdfsA=LyW6t_ctuhcEBQ2XMNSVUWxaaoKQ@mail.gmail.com>
References: <CAP7YuASpwrA-2fLQxdfsA=LyW6t_ctuhcEBQ2XMNSVUWxaaoKQ@mail.gmail.com>
Message-ID: <CAGHtMWnZjTdM7RqV2kfx5=U_0DJPGsxkq_1ssMAToRRC3k7_Cg@mail.gmail.com>

Correct link is
https://adopt-openjdk.ci.cloudbees.com/job/jtreg/lastSuccessfulBuild/artifact/<https://adopt-openjdk.ci.cloudbees.com/job/jtreg/lastSuccessfulBuild/artifact/now>

the now at the end of it was a separate word.

Thanks Martijn.

Cheers,
Mani


On Sat, Jan 18, 2014 at 1:29 PM, Martijn Verburg
<martijnverburg at gmail.com>wrote:

> Hi all,
>
>
> https://adopt-openjdk.ci.cloudbees.com/job/jtreg/lastSuccessfulBuild/artifact/now
> produces a Maven compatible 5.0.0-SNAPSHOT version of jtreg.
>
> This was to make the download and install for the Virtual Machines we're
> producing for the build-farm as well as making jtreg Maven repo compatible.
>
> IIRC jtreg was last released as version 4.3? Hopefully 5.0.0 is the next
> logical number.
>
> Probably needs a conversation about how to deal with versioning and if
> jtreg can be uploaded to Maven Central or not (any legal barriers?).
>
> Cheers,
> Martijn
>



-- 
*Twitter:* @theNeomatrix369 <http://twitter.com/theNeomatrix369>
*Blog:* http://neomatrix369.wordpress.com
*JUG activity: *LJC Associate & LJC Advocate (@adoptopenjdk & @adoptajsr
programs)
*Meet-a-Project:* https://github.com/MutabilityDetector
*Bitbucket:* https://bitbucket.org/neomatrix369   *Github:* https://github
.com/neomatrix369
*LinkedIn:* http://uk.linkedin.com/pub/mani-sarkar/71/a77/39b

*Don't chase success, rather aim for "Excellence", and success will come
chasing after you!*

From jonathan.gibbons at oracle.com  Mon Jan 20 09:47:21 2014
From: jonathan.gibbons at oracle.com (Jonathan Gibbons)
Date: Mon, 20 Jan 2014 09:47:21 -0800
Subject: jtreg nightly build version change
In-Reply-To: <CAP7YuASpwrA-2fLQxdfsA=LyW6t_ctuhcEBQ2XMNSVUWxaaoKQ@mail.gmail.com>
References: <CAP7YuASpwrA-2fLQxdfsA=LyW6t_ctuhcEBQ2XMNSVUWxaaoKQ@mail.gmail.com>
Message-ID: <52DD6129.1010703@oracle.com>

On 01/18/2014 05:29 AM, Martijn Verburg wrote:
> Hi all,
>
> https://adopt-openjdk.ci.cloudbees.com/job/jtreg/lastSuccessfulBuild/artifact/ 
> now produces a Maven compatible 5.0.0-SNAPSHOT version of jtreg.
>
> This was to make the download and install for the Virtual Machines 
> we're producing for the build-farm as well as making jtreg Maven repo 
> compatible.
>
> IIRC jtreg was last released as version 4.3? Hopefully 5.0.0 is the 
> next logical number.
>
> Probably needs a conversation about how to deal with versioning and if 
> jtreg can be uploaded to Maven Central or not (any legal barriers?).
>
> Cheers,
> Martijn

Martijn,

jtreg has never been 4.3.  I think you're confusing it with the version 
of JTHarness that it uses.

For a while now, jtreg has been using jtreg 4.1 bNN where NN is a small 
interger, currently 08. This was more significant when we (Oracle) were 
producing binary builds.  Now that we are no longer doing that, I think 
we will start advancing the jtreg number in a more conventional fashion.

I had hoped to combine the advance to 4.2 with a major update to the 
jtreg documentation, but that seems to be never quite high enough 
priority to have anything happen :-(

-- Jon

From jonathan.gibbons at oracle.com  Tue Jan 21 08:37:25 2014
From: jonathan.gibbons at oracle.com (Jonathan Gibbons)
Date: Tue, 21 Jan 2014 08:37:25 -0800
Subject: jtreg nightly build version change
In-Reply-To: <CAP7YuASGQtyyQf=iD5z8e01AMz_k2NN=kUBhCB14SkaAa3A8rw@mail.gmail.com>
References: <CAP7YuASpwrA-2fLQxdfsA=LyW6t_ctuhcEBQ2XMNSVUWxaaoKQ@mail.gmail.com>	<52DD6129.1010703@oracle.com>
	<CAP7YuASGQtyyQf=iD5z8e01AMz_k2NN=kUBhCB14SkaAa3A8rw@mail.gmail.com>
Message-ID: <52DEA245.9050303@oracle.com>

Martin,

Right now, the latest tag in the repo should be jtreg4.1-b08.   It seems 
to be it would be good if your build could reflect that. There should be 
enough hooks in the build script to allow you to set the version.

-- Jon

On 01/20/2014 09:54 AM, Martijn Verburg wrote:
> Hi Jonathan,
>
> Thanks for the info.  In that case I'll change the build to produce a 
> 4.2.0-SNAPSHOT following the traditional model. I guess we can then 
> work on the build script to allow it to produce formal releases (such 
> as 4.2.0) to Maven central.
>
> I don't have permission to raise an issue directly in JBUG for this, 
> are you able to or does it still need to go through the bugs.sun... 
> method?
>
>
>
> Cheers,
> Martijn
>
>
> On 20 January 2014 17:47, Jonathan Gibbons 
> <jonathan.gibbons at oracle.com <mailto:jonathan.gibbons at oracle.com>> wrote:
>
>     On 01/18/2014 05:29 AM, Martijn Verburg wrote:
>
>         Hi all,
>
>         https://adopt-openjdk.ci.cloudbees.com/job/jtreg/lastSuccessfulBuild/artifact/
>         now produces a Maven compatible 5.0.0-SNAPSHOT version of jtreg.
>
>         This was to make the download and install for the Virtual
>         Machines we're producing for the build-farm as well as making
>         jtreg Maven repo compatible.
>
>         IIRC jtreg was last released as version 4.3? Hopefully 5.0.0
>         is the next logical number.
>
>         Probably needs a conversation about how to deal with
>         versioning and if jtreg can be uploaded to Maven Central or
>         not (any legal barriers?).
>
>         Cheers,
>         Martijn
>
>
>     Martijn,
>
>     jtreg has never been 4.3.  I think you're confusing it with the
>     version of JTHarness that it uses.
>
>     For a while now, jtreg has been using jtreg 4.1 bNN where NN is a
>     small interger, currently 08. This was more significant when we
>     (Oracle) were producing binary builds.  Now that we are no longer
>     doing that, I think we will start advancing the jtreg number in a
>     more conventional fashion.
>
>     I had hoped to combine the advance to 4.2 with a major update to
>     the jtreg documentation, but that seems to be never quite high
>     enough priority to have anything happen :-(
>
>     -- Jon
>
>


From volker.simonis at gmail.com  Fri Jan 24 02:36:47 2014
From: volker.simonis at gmail.com (Volker Simonis)
Date: Fri, 24 Jan 2014 11:36:47 +0100
Subject: Fwd: FYI, JDK_MINOR_VERSION updated from 8 to 9, current jtreg needed
	to run TestNG tests
In-Reply-To: <52CCB9EE.10904@oracle.com>
References: <52CCB9EE.10904@oracle.com>
Message-ID: <CA+3eh10542ko-AjBYbshdBiTnwxb82pPqsw4+pDBQ3b=sPDwBA@mail.gmail.com>

Hi Jonathan,

could you please put the attached information on:

http://openjdk.java.net/jtreg/runtests.html

I think it could also help to mention the least version that supports
groups and that it is required to run the current tests.

This probably means that people have to build JTreg from source
because as far as I remember the latest downloadable version doesn't
support neither groups nor jdk9. This could be mentioned as well right
on top of the page to save the people the time of looking for a binary
version.

Thank you and best regards,
Volker


---------- Forwarded message ----------
From: Joe Darcy <joe.darcy at oracle.com>
Date: Wed, Jan 8, 2014 at 3:37 AM
Subject: FYI, JDK_MINOR_VERSION updated from 8 to 9, current jtreg
needed to run TestNG tests
To: jdk9-dev at openjdk.java.net


Hello,

Earlier today I pushed a changeset to the JDK 9 dev repo to update
JDK_MINOR_VERSION from 8 to 9:

    http://hg.openjdk.java.net/jdk9/dev/rev/99544d4803b0

As a consequence of this change, to successfully run the TestNG tests
in the JDK 9 jdk and langtools repos, you will need an version of
jtreg:

    http://openjdk.java.net/projects/code-tools/jtreg/

that includes a fix made in December of 2013.

Happy testing,

-Joe

From martijnverburg at gmail.com  Sat Jan 18 13:29:20 2014
From: martijnverburg at gmail.com (Martijn Verburg)
Date: Sat, 18 Jan 2014 13:29:20 -0000
Subject: jtreg nightly build version change
Message-ID: <CAP7YuASpwrA-2fLQxdfsA=LyW6t_ctuhcEBQ2XMNSVUWxaaoKQ@mail.gmail.com>

Hi all,

https://adopt-openjdk.ci.cloudbees.com/job/jtreg/lastSuccessfulBuild/artifact/now
produces a Maven compatible 5.0.0-SNAPSHOT version of jtreg.

This was to make the download and install for the Virtual Machines we're
producing for the build-farm as well as making jtreg Maven repo compatible.

IIRC jtreg was last released as version 4.3? Hopefully 5.0.0 is the next
logical number.

Probably needs a conversation about how to deal with versioning and if
jtreg can be uploaded to Maven Central or not (any legal barriers?).

Cheers,
Martijn

From martijnverburg at gmail.com  Mon Jan 20 17:54:10 2014
From: martijnverburg at gmail.com (Martijn Verburg)
Date: Mon, 20 Jan 2014 17:54:10 -0000
Subject: jtreg nightly build version change
In-Reply-To: <52DD6129.1010703@oracle.com>
References: <CAP7YuASpwrA-2fLQxdfsA=LyW6t_ctuhcEBQ2XMNSVUWxaaoKQ@mail.gmail.com>
	<52DD6129.1010703@oracle.com>
Message-ID: <CAP7YuASGQtyyQf=iD5z8e01AMz_k2NN=kUBhCB14SkaAa3A8rw@mail.gmail.com>

Hi Jonathan,

Thanks for the info.  In that case I'll change the build to produce a
4.2.0-SNAPSHOT following the traditional model. I guess we can then work on
the build script to allow it to produce formal releases (such as 4.2.0) to
Maven central.

I don't have permission to raise an issue directly in JBUG for this, are
you able to or does it still need to go through the bugs.sun... method?



Cheers,
Martijn


On 20 January 2014 17:47, Jonathan Gibbons <jonathan.gibbons at oracle.com>wrote:

> On 01/18/2014 05:29 AM, Martijn Verburg wrote:
>
>> Hi all,
>>
>> https://adopt-openjdk.ci.cloudbees.com/job/jtreg/
>> lastSuccessfulBuild/artifact/ now produces a Maven compatible
>> 5.0.0-SNAPSHOT version of jtreg.
>>
>> This was to make the download and install for the Virtual Machines we're
>> producing for the build-farm as well as making jtreg Maven repo compatible.
>>
>> IIRC jtreg was last released as version 4.3? Hopefully 5.0.0 is the next
>> logical number.
>>
>> Probably needs a conversation about how to deal with versioning and if
>> jtreg can be uploaded to Maven Central or not (any legal barriers?).
>>
>> Cheers,
>> Martijn
>>
>
> Martijn,
>
> jtreg has never been 4.3.  I think you're confusing it with the version of
> JTHarness that it uses.
>
> For a while now, jtreg has been using jtreg 4.1 bNN where NN is a small
> interger, currently 08. This was more significant when we (Oracle) were
> producing binary builds.  Now that we are no longer doing that, I think we
> will start advancing the jtreg number in a more conventional fashion.
>
> I had hoped to combine the advance to 4.2 with a major update to the jtreg
> documentation, but that seems to be never quite high enough priority to
> have anything happen :-(
>
> -- Jon
>