From openjdk at gatworks.com Fri Mar 2 19:24:49 2012 From: openjdk at gatworks.com (Uncle George) Date: Fri, 02 Mar 2012 14:24:49 -0500 Subject: where is the libstdc++ package? Message-ID: <4F511E81.2050108@gatworks.com> I am looking for the libstdc++ package for the libjvm that I am building on fedora 16. I was looking for a fedora compat package, but cant seem to find one. From dbhole at redhat.com Fri Mar 2 19:53:44 2012 From: dbhole at redhat.com (Deepak Bhole) Date: Fri, 2 Mar 2012 14:53:44 -0500 Subject: where is the libstdc++ package? In-Reply-To: <4F511E81.2050108@gatworks.com> References: <4F511E81.2050108@gatworks.com> Message-ID: <20120302195343.GN24599@redhat.com> * Uncle George [2012-03-02 14:35]: > I am looking for the libstdc++ package for the libjvm that I am > building on fedora 16. > > I was looking for a fedora compat package, but cant seem to find one. Do you mean libstdc++-static? Deepak From dbhole at redhat.com Fri Mar 2 20:04:38 2012 From: dbhole at redhat.com (Deepak Bhole) Date: Fri, 2 Mar 2012 15:04:38 -0500 Subject: where is the libstdc++ package? In-Reply-To: <20120302195343.GN24599@redhat.com> References: <4F511E81.2050108@gatworks.com> <20120302195343.GN24599@redhat.com> Message-ID: <20120302200437.GP24599@redhat.com> * Deepak Bhole [2012-03-02 14:53]: > * Uncle George [2012-03-02 14:35]: > > I am looking for the libstdc++ package for the libjvm that I am > > building on fedora 16. > > > > I was looking for a fedora compat package, but cant seem to find one. > > Do you mean libstdc++-static? > Hi, I just realized that this was sent to discuss at . Technical questions should go to one of the appropriate dev lists mentioned here: http://mail.openjdk.java.net/mailman/listinfo Cheers, Deepak From frans at meruvian.org Mon Mar 5 00:05:11 2012 From: frans at meruvian.org (Frans Thamura) Date: Mon, 5 Mar 2012 07:05:11 +0700 Subject: Miglayout Message-ID: hi all just read this, a long bugs issue 2007 and a little discussion with Geejan from Netbeans around MigLayout http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=e02b026c1ef0bffffffffdfbd57e8f43560d?bug_id=6530906 any idea why, MIG Layout cannot be part of JDK? -- Frans Thamura (???) Shadow Master and Lead Investor Meruvian. Integrated Hypermedia Java Solution Provider. Mobile: +628557888699 Blog: http://blogs.mervpolis.com/roller/flatburger (id) FB: http://www.facebook.com/meruvian TW: http://www.twitter.com/meruvian / @meruvian Website: http://www.meruvian.org "We grow because we share the same belief." From rom at rom1v.com Tue Mar 6 19:17:08 2012 From: rom at rom1v.com (=?UTF-8?Q?=C2=AEom?=) Date: Tue, 6 Mar 2012 11:17:08 -0800 (PST) Subject: Jar manifest and openjdk Message-ID: <33439789.post@talk.nabble.com> If I create a jar using /usr/lib/jvm/java-6-openjdk-amd64/bin/jar: jar cf test.jar anyfile It writes in META-INF/MANIFEST.MF : Created-By: 1.6.0_24 (Sun Microsystems Inc.) Why does it write "Sun Microsystems" ? -- View this message in context: http://old.nabble.com/Jar-manifest-and-openjdk-tp33439789p33439789.html Sent from the OpenJDK General discussion mailing list archive at Nabble.com. From martijnverburg at gmail.com Tue Mar 6 21:35:36 2012 From: martijnverburg at gmail.com (Martijn Verburg) Date: Tue, 6 Mar 2012 21:35:36 +0000 Subject: Miglayout In-Reply-To: References: Message-ID: Hi Frans, I think this Q is best posted to the 2d-dev mailing list. Cheers, Martijn On 5 March 2012 00:05, Frans Thamura wrote: > hi all > > just read this, a long bugs issue 2007 > > and a little discussion with Geejan from Netbeans around MigLayout > > http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=e02b026c1ef0bffffffffdfbd57e8f43560d?bug_id=6530906 > > any idea why, MIG Layout cannot be part of JDK? > > > -- > Frans Thamura (???) > Shadow Master and Lead Investor > Meruvian. > Integrated Hypermedia Java Solution Provider. > > Mobile: +628557888699 > Blog: http://blogs.mervpolis.com/roller/flatburger (id) > > FB: http://www.facebook.com/meruvian > TW: http://www.twitter.com/meruvian / @meruvian > Website: http://www.meruvian.org > > "We grow because we share the same belief." From jonathan.gibbons at oracle.com Sat Mar 10 19:19:47 2012 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Sat, 10 Mar 2012 11:19:47 -0800 Subject: Project Proposal: Code Tools Message-ID: <4F5BA953.6030405@oracle.com> In accordance with the OpenJDK guidelines [1], I would like to start the discussion of a new Project to provide tools of use to OpenJDK developers while working on the OpenJDK code base. Such tools currently include test tools and Mercurial extensions; it is envisaged that additional tools will be added over time, subject to the Project Lead's approval. There are a number of initial candidates for inclusion in such a Project. * jtreg jtreg is the regression test harness for the OpenJDK platform. It is currently just available via source bundles [2]. * jtharness jtharness is the test framework underlying jtreg [3]. * sigtest sigtest is a set of utilities relating to API signature checking [4]. * the Mercurial "jcheck" extension jcheck provides simple validity checks on the contents of a changeset It is expected that most of these tools will have their own separate communities, and so each tool should have its own repositories and mailing list. -- Jon Gibbons [1]http://openjdk.java.net/projects/#new-project [2]http://openjdk.java.net/jtreg [3]http://jtharness.java.net/ [4]http://sigtest.java.net/ From kelly.ohair at oracle.com Mon Mar 12 18:16:12 2012 From: kelly.ohair at oracle.com (Kelly O'Hair) Date: Mon, 12 Mar 2012 11:16:12 -0700 Subject: Project Proposal: Code Tools In-Reply-To: <4F5BA953.6030405@oracle.com> References: <4F5BA953.6030405@oracle.com> Message-ID: <7688050D-AE63-49CB-B213-E114D009CBC9@oracle.com> On Mar 10, 2012, at 11:19 AM, Jonathan Gibbons wrote: > In accordance with the OpenJDK guidelines [1], I would like to start the discussion of a new Project to provide tools of use to OpenJDK developers while working on the OpenJDK code base. Such tools currently include test tools and Mercurial extensions; it is envisaged that additional tools will be added over time, subject to the Project Lead's approval. > > There are a number of initial candidates for inclusion in such a Project. > > * jtreg > jtreg is the regression test harness for the OpenJDK platform. > It is currently just available via source bundles [2]. > > * jtharness > jtharness is the test framework underlying jtreg [3]. > > * sigtest > sigtest is a set of utilities relating to API signature checking [4]. > > * the Mercurial "jcheck" extension > jcheck provides simple validity checks on the contents of a changeset I wonder if one repository holding all the Mercurial extensions would make sense? Not sure it's a big deal, just a suggestion. I think this is a good idea. -kto > > It is expected that most of these tools will have their own separate communities, and so each tool should have its own repositories and mailing list. > > > -- Jon Gibbons > > > [1]http://openjdk.java.net/projects/#new-project > [2]http://openjdk.java.net/jtreg > [3]http://jtharness.java.net/ > [4]http://sigtest.java.net/ > > From jonathan.gibbons at oracle.com Mon Mar 12 18:31:34 2012 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Mon, 12 Mar 2012 11:31:34 -0700 Subject: Project Proposal: Code Tools In-Reply-To: <7688050D-AE63-49CB-B213-E114D009CBC9@oracle.com> References: <4F5BA953.6030405@oracle.com> <7688050D-AE63-49CB-B213-E114D009CBC9@oracle.com> Message-ID: <4F5E4106.2030400@oracle.com> On 03/12/2012 11:16 AM, Kelly O'Hair wrote: > On Mar 10, 2012, at 11:19 AM, Jonathan Gibbons wrote: > >> > In accordance with the OpenJDK guidelines [1], I would like to start the discussion of a new Project to provide tools of use to OpenJDK developers while working on the OpenJDK code base. Such tools currently include test tools and Mercurial extensions; it is envisaged that additional tools will be added over time, subject to the Project Lead's approval. >> > >> > There are a number of initial candidates for inclusion in such a Project. >> > >> > * jtreg >> > jtreg is the regression test harness for the OpenJDK platform. >> > It is currently just available via source bundles [2]. >> > >> > * jtharness >> > jtharness is the test framework underlying jtreg [3]. >> > >> > * sigtest >> > sigtest is a set of utilities relating to API signature checking [4]. >> > >> > * the Mercurial "jcheck" extension >> > jcheck provides simple validity checks on the contents of a changeset > I wonder if one repository holding all the Mercurial extensions would make sense? > > Not sure it's a big deal, just a suggestion. > > I think this is a good idea. > > -kto > I think it's a reasonable idea, subject to the consensus of those who might want to work on Mercurial extensions. -- Jon From jonathan.gibbons at oracle.com Mon Mar 12 21:12:53 2012 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Mon, 12 Mar 2012 14:12:53 -0700 Subject: Project Proposal: Code Tools In-Reply-To: <4F5BA953.6030405@oracle.com> References: <4F5BA953.6030405@oracle.com> Message-ID: <4F5E66D5.7010306@oracle.com> On behalf of the Compiler Group, I declare that the Compiler Group is pleased to sponsor such a Project. -- Jon On 03/10/2012 11:19 AM, Jonathan Gibbons wrote: > In accordance with the OpenJDK guidelines [1], I would like to start > the discussion of a new Project to provide tools of use to OpenJDK > developers while working on the OpenJDK code base. Such tools > currently include test tools and Mercurial extensions; it is envisaged > that additional tools will be added over time, subject to the Project > Lead's approval. > > There are a number of initial candidates for inclusion in such a Project. > > * jtreg > jtreg is the regression test harness for the OpenJDK platform. > It is currently just available via source bundles [2]. > > * jtharness > jtharness is the test framework underlying jtreg [3]. > > * sigtest > sigtest is a set of utilities relating to API signature checking > [4]. > > * the Mercurial "jcheck" extension > jcheck provides simple validity checks on the contents of a > changeset > > It is expected that most of these tools will have their own separate > communities, and so each tool should have its own repositories and > mailing list. > > > -- Jon Gibbons > > > [1]http://openjdk.java.net/projects/#new-project > [2]http://openjdk.java.net/jtreg > [3]http://jtharness.java.net/ > [4]http://sigtest.java.net/ > > From kevin.looney at oracle.com Tue Mar 13 21:31:13 2012 From: kevin.looney at oracle.com (Kevin Looney) Date: Tue, 13 Mar 2012 14:31:13 -0700 Subject: Project Proposal: Code Tools Message-ID: <4F5FBCA1.3050705@oracle.com> The following people are active contributors on the JTHarness [1] and SigTest [2] java.net projects: Brian Kurotsuchi: [1] Dmitry Fazunenko: [1, 2] Mikhail Ershov: [1, 2] Kevin Looney: [1, 2] Andrey Titov: [1] Larry Hoffman: [1, 2] Dawn Phillips: [1] [1]http://jtharness.java.net/ [2]http://sigtest.java.net/ Thank You, Kevin Looney From jonathan.gibbons at oracle.com Tue Mar 13 22:08:59 2012 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Tue, 13 Mar 2012 15:08:59 -0700 Subject: Project Proposal: Code Tools In-Reply-To: <4F5FBCA1.3050705@oracle.com> References: <4F5FBCA1.3050705@oracle.com> Message-ID: <4F5FC57B.6080602@oracle.com> Thanks for the details, Kevin. -- Jon On 03/13/2012 02:31 PM, Kevin Looney wrote: > The following people are active contributors on the JTHarness [1] and > SigTest [2] java.net projects: > > Brian Kurotsuchi: [1] > Dmitry Fazunenko: [1, 2] > Mikhail Ershov: [1, 2] > Kevin Looney: [1, 2] > Andrey Titov: [1] > Larry Hoffman: [1, 2] > Dawn Phillips: [1] > > [1]http://jtharness.java.net/ > [2]http://sigtest.java.net/ > > Thank You, > Kevin Looney From zhouyx at linux.vnet.ibm.com Tue Mar 20 02:25:38 2012 From: zhouyx at linux.vnet.ibm.com (Sean Chou) Date: Tue, 20 Mar 2012 10:25:38 +0800 Subject: Bug number not received after submitting Message-ID: Hi all, We encountered the problem since yesterday, there are several bugs reported, but no mail received. Is this mailing list the right place to ask ? -- Best Regards, Sean Chou From martijnverburg at gmail.com Tue Mar 20 08:31:00 2012 From: martijnverburg at gmail.com (Martijn Verburg) Date: Tue, 20 Mar 2012 08:31:00 +0000 Subject: Bug number not received after submitting In-Reply-To: References: Message-ID: Hi Sean, This isn't the right list no :-). Send me the details of your issue privately and I'll point you to the right list/bug database. Cheers, Martijn On 20 March 2012 02:25, Sean Chou wrote: > Hi all, > > We encountered the problem since yesterday, there are several bugs > reported, but no mail received. > > Is this mailing list the right place to ask ? > > -- > Best Regards, > Sean Chou > From roger.lewis at oracle.com Tue Mar 20 17:49:47 2012 From: roger.lewis at oracle.com (Roger Lewis) Date: Tue, 20 Mar 2012 10:49:47 -0700 Subject: Bug number not received after submitting In-Reply-To: References: Message-ID: <4F68C33B.9060309@oracle.com> Hello Sean, Due to to a change with the submission mechanism there was a temporary issue in creating IDs. The problem has been resolved and any new submissions will automatically generate an ID. There will be a change later in the week, which will not interrupt the service. We will attempt to generate IDs for the reports, such as yours, that are waiting in the queue by the end of the day. Thank you, Roger On 3/20/12 5:31 AM, Sean Chou wrote: > Hi all, > > We reported bugs yesterday, usually the bug system will send a > mail after a bug is submitted. But yesterday it didn't send. > > Is this mailing list the right place to ask ? > > -- > Best Regards, > Sean Chou > From ahughes at redhat.com Wed Mar 21 15:54:21 2012 From: ahughes at redhat.com (Andrew Hughes) Date: Wed, 21 Mar 2012 11:54:21 -0400 (EDT) Subject: OpenJDK bug database: Status update In-Reply-To: <20120315194543.C1780AB5@eggemoggin.niobe.net> Message-ID: ----- Original Message ----- > Last October I announced Oracle's intent to deploy a pilot JIRA > instance > for use by the OpenJDK Community within a few months and then, if all > goes well, to migrate the JDK bug corpus from Sun's creaky old legacy > internal system to a public JIRA instance by mid-2012 [1]. > > Following that announcement Iris Clark initiated and moderated the > first > of a planned series of discussions about the design and configuration > of > the system [2][3]. In parallel Mohan Pakkurti and his team have been > working to implement the pilot system; this includes configuring > JIRA, > acquiring and provisioning hardware, and getting the myriad internal > approvals required from various parts of Oracle. > > All of this work is, unfortunately, taking much longer than > anticipated. > We remain committed to the ultimate goal of making a public JIRA > instance > available, but at this point we don't think we can deliver it in the > next > few months. In the meantime it's now mid-March, and the legacy > internal > system is going to be shut down in late July. > > Faced with these constraints, we must change our plan. Rather than > make > a public pilot system available first, we're initially going to > migrate > the JDK bug corpus from the legacy internal system to an internal > JIRA > instance. Our goal is to complete that transition by mid-June, and > in > order to do that we've assigned several more Oracle engineers to the > effort. We'll move to an external public JIRA instance some time > later, > once the hardware is in place and the necessary approvals are > obtained. > > In order to speed the migration process the initial JIRA instances, > both > internal and external, will not be as deeply customized as envisioned > in > Iris's draft [3]. Some of the ideas in the draft will no doubt > influence > the design of the initial systems; the remainder will be reconsidered > after the public system is available. > > I understand that this news will be disappointing to many; I'm not > very > happy about it myself. It's unfortunate that there won't be a public > pilot system prior to the migration, that deep customization work > will > have to wait, and that the public system most likely won't be > available > by mid-2012. It will be far worse for all concerned, however, if > there > is not even a working internal bug system for the JDK by the time > that > Sun's legacy system is shut down. This new plan therefore places the > highest priority on migrating off of that system. Oracle remains > firmly > committed to making a public system available as soon as possible > after > that. > > - Mark > > > [1] > http://mail.openjdk.java.net/pipermail/announce/2011-October/000112.html > [2] > http://mail.openjdk.java.net/pipermail/discuss/2011-December/002237.html > [3] http://cr.openjdk.java.net/~iris/jira/JIRAforOpenJDK.html > Does this mean there will be a period where access to bug details is only available internally at Oracle and an external user can't, for instance, look up the details of a bug corresponding to an ID in the Mercurial repositories? -- Andrew :) Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) PGP Key: 248BDC07 (https://keys.indymedia.org/) Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07 From roger.calnan at oracle.com Wed Mar 21 17:26:19 2012 From: roger.calnan at oracle.com (Roger Calnan) Date: Wed, 21 Mar 2012 17:26:19 +0000 Subject: OpenJDK bug database: Status update In-Reply-To: References: Message-ID: <545D05D7-6627-40AF-8713-374647E8719F@oracle.com> no the goal is to continue the external access to the bugs pulling the data from the internal JIRA rather than the old system, Roger > Does this mean there will be a period where access to bug details > is only available internally at Oracle and an external user can't, > for instance, look up the details of a bug corresponding to an ID > in the Mercurial repositories? > -- > Andrew :) > > Free Java Software Engineer > Red Hat, Inc. (http://www.redhat.com) > > PGP Key: 248BDC07 (https://keys.indymedia.org/) > Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07 > From ahughes at redhat.com Wed Mar 21 17:27:15 2012 From: ahughes at redhat.com (Andrew Hughes) Date: Wed, 21 Mar 2012 13:27:15 -0400 (EDT) Subject: OpenJDK bug database: Status update In-Reply-To: <545D05D7-6627-40AF-8713-374647E8719F@oracle.com> Message-ID: <6187af8d-02b1-4ec0-8fc8-7ab9cb21c99c@zmail17.collab.prod.int.phx2.redhat.com> ----- Original Message ----- > no the goal is to continue the external access to the bugs > pulling the data from the internal JIRA rather than the old system, > Ah good. That wasn't clear from the original e-mail. > Roger > > > > Does this mean there will be a period where access to bug details > > is only available internally at Oracle and an external user can't, > > for instance, look up the details of a bug corresponding to an ID > > in the Mercurial repositories? > > -- > > Andrew :) > > > > Free Java Software Engineer > > Red Hat, Inc. (http://www.redhat.com) > > > > PGP Key: 248BDC07 (https://keys.indymedia.org/) > > Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07 > > > -- Andrew :) Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) PGP Key: 248BDC07 (https://keys.indymedia.org/) Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07 From joe.darcy at oracle.com Thu Mar 22 03:43:31 2012 From: joe.darcy at oracle.com (Joe Darcy) Date: Wed, 21 Mar 2012 20:43:31 -0700 Subject: OpenJDK bug database: Status update In-Reply-To: <545D05D7-6627-40AF-8713-374647E8719F@oracle.com> References: <545D05D7-6627-40AF-8713-374647E8719F@oracle.com> Message-ID: <4F6A9FE3.6000900@oracle.com> Just a quick follow-up, our overriding priority for the next few months is to make sure some bug system is continuously available for the JDK. With that goal, it possible that both some Oracle-internal as well as external boundary systems, like bugs.sun.com, are not ready to be migrated over when the cutover to the internal JIRA instance occurs. If that happens, there may some temporary gaps in the availability of or stale data in the boundary systems. However, as Roger indicates, our goal is to provide analogous access to JDK bug information from internal JIRA as is done today from the legacy bug system, subject to making the core migration deadlines. -Joe during the internal JIRA phase (before the external JIRA phase) our intention is to provide On 03/21/2012 10:26 AM, Roger Calnan wrote: > no the goal is to continue the external access to the bugs > pulling the data from the internal JIRA rather than the old system, > > Roger > > >> Does this mean there will be a period where access to bug details >> is only available internally at Oracle and an external user can't, >> for instance, look up the details of a bug corresponding to an ID >> in the Mercurial repositories? >> -- >> Andrew :) >> >> Free Java Software Engineer >> Red Hat, Inc. (http://www.redhat.com) >> >> PGP Key: 248BDC07 (https://keys.indymedia.org/) >> Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07 >> From artem.ananiev at oracle.com Fri Mar 23 09:38:45 2012 From: artem.ananiev at oracle.com (Artem Ananiev) Date: Fri, 23 Mar 2012 13:38:45 +0400 Subject: CFV: New Project: Code Tools In-Reply-To: <4F6BB9EA.6090904@oracle.com> References: <4F6BB9EA.6090904@oracle.com> Message-ID: <4F6C44A5.9010600@oracle.com> Vote: yes. On 3/23/2012 3:46 AM, Jonathan Gibbons wrote: > I hereby propose the creation of the Code Tools Project[1] with > Jon Gibbons as the Lead and the Compiler Group as the sponsoring > Group(s). > > The goal of the Code Tools Project will be to provide tools of use to > OpenJDK developers while working on the OpenJDK code base. > Such tools currently include test tools and Mercurial extensions; > it is envisaged that additional tools will be added over time, > after discussion on the Project's main mailing list, and subject > to the Project Lead's approval. > > There are a number of initial candidates for inclusion in such a Project. > > * jtreg > jtreg is the regression test harness for the OpenJDK platform. > It is currently just available via source bundles [2]. > > * jtharness > jtharness is the test framework underlying jtreg [3]. > > * sigtest > sigtest is a set of utilities relating to API signature checking [4]. > > * the Mercurial "jcheck" extension > jcheck provides simple validity checks on the contents of a changeset > > Jon has long been involved in the tools aspects of testing JDK. > He designed the original JavaTest harness, underlying both JCK > and jtreg. Since joining the JDK LangTools team, he has led the > way in improving the reliability of test runs, both by improving > tests and/or the jtreg test harness. > > The suggested sets of initial reviewers and committers are based > upon the contributors to the initial set of tools listed above. > > The suggested initial set of Reviewers is: > > Mark Reinhold > John Coomes > Iris Clark > Brian Kurotsuchi > Dmitry Fazunenko > Mikhail Ershov > Kevin Looney > Andrey Titov > > In addition, the suggested initial set of Committers is: > > Larry Hoffman > Dawn Phillips > > Votes are due by 7:00AM UTC, Friday 6 April [7]. > > Only current OpenJDK Members [5] are eligible to vote on this > motion. > > For Lazy Consensus voting instructions, see [6]. > > -- Jon Gibbons > > [1] http://mail.openjdk.java.net/pipermail/discuss/2012-March/002563.html > [2] http://openjdk.java.net/jtreg > [3] http://jtharness.java.net/ > [4] http://sigtest.java.net/ > [5] http://openjdk.java.net/census/#members > [6] http://openjdk.java.net/projects/#new-project-vote > [7] > http://www.timeanddate.com/worldclock/fixedtime.html?msg=CFV%3A+New+Code+Tools+Project&iso=20120406T0000&p1=224 > > From omajid at redhat.com Fri Mar 23 15:48:42 2012 From: omajid at redhat.com (Omair Majid) Date: Fri, 23 Mar 2012 11:48:42 -0400 Subject: CFV: New Project: Code Tools In-Reply-To: <4F6BB9EA.6090904@oracle.com> References: <4F6BB9EA.6090904@oracle.com> Message-ID: <4F6C9B5A.4040604@redhat.com> Vote: Yes On 03/22/2012 07:46 PM, Jonathan Gibbons wrote: > I hereby propose the creation of the Code Tools Project[1] with > Jon Gibbons as the Lead and the Compiler Group as the sponsoring > Group(s). > > The goal of the Code Tools Project will be to provide tools of use to > OpenJDK developers while working on the OpenJDK code base. > Such tools currently include test tools and Mercurial extensions; > it is envisaged that additional tools will be added over time, > after discussion on the Project's main mailing list, and subject > to the Project Lead's approval. > > There are a number of initial candidates for inclusion in such a Project. > > * jtreg > jtreg is the regression test harness for the OpenJDK platform. > It is currently just available via source bundles [2]. > > * jtharness > jtharness is the test framework underlying jtreg [3]. > > * sigtest > sigtest is a set of utilities relating to API signature checking [4]. > > * the Mercurial "jcheck" extension > jcheck provides simple validity checks on the contents of a changeset > > Jon has long been involved in the tools aspects of testing JDK. > He designed the original JavaTest harness, underlying both JCK > and jtreg. Since joining the JDK LangTools team, he has led the > way in improving the reliability of test runs, both by improving > tests and/or the jtreg test harness. > > The suggested sets of initial reviewers and committers are based > upon the contributors to the initial set of tools listed above. > > The suggested initial set of Reviewers is: > > Mark Reinhold > John Coomes > Iris Clark > Brian Kurotsuchi > Dmitry Fazunenko > Mikhail Ershov > Kevin Looney > Andrey Titov > > In addition, the suggested initial set of Committers is: > > Larry Hoffman > Dawn Phillips > > Votes are due by 7:00AM UTC, Friday 6 April [7]. > > Only current OpenJDK Members [5] are eligible to vote on this > motion. > > For Lazy Consensus voting instructions, see [6]. > > -- Jon Gibbons > > [1] http://mail.openjdk.java.net/pipermail/discuss/2012-March/002563.html > [2] http://openjdk.java.net/jtreg > [3] http://jtharness.java.net/ > [4] http://sigtest.java.net/ > [5] http://openjdk.java.net/census/#members > [6] http://openjdk.java.net/projects/#new-project-vote > [7] > http://www.timeanddate.com/worldclock/fixedtime.html?msg=CFV%3A+New+Code+Tools+Project&iso=20120406T0000&p1=224 > > From dalibor.topic at oracle.com Fri Mar 23 16:22:42 2012 From: dalibor.topic at oracle.com (Dalibor Topic) Date: Fri, 23 Mar 2012 17:22:42 +0100 Subject: CFV: New Project: Code Tools In-Reply-To: <4F6C44A5.9010600@oracle.com> References: <4F6BB9EA.6090904@oracle.com> <4F6C44A5.9010600@oracle.com> Message-ID: <4F6CA352.7020902@oracle.com> Vote: Yes. cheers, dalibor topic -- Oracle Dalibor Topic | Principal Product Manager Phone: +494089091214 | Mobile: +491737185961 Oracle Java Platform Group ORACLE Deutschland B.V. & Co. KG | Nagelsweg 55 | 20097 Hamburg ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 M?nchen Registergericht: Amtsgericht M?nchen, HRA 95603 Gesch?ftsf?hrer: J?rgen Kunz Komplement?rin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Gesch?ftsf?hrer: Alexander van der Ven, Astrid Kepper, Val Maher Green Oracle Oracle is committed to developing practices and products that help protect the environment From Abhi.Saha at Oracle.COM Fri Mar 23 16:37:05 2012 From: Abhi.Saha at Oracle.COM (Abhijit Saha) Date: Fri, 23 Mar 2012 09:37:05 -0700 Subject: CFV: New Project: Code Tools In-Reply-To: <4F6BB9EA.6090904@oracle.com> References: <4F6BB9EA.6090904@oracle.com> Message-ID: <4F6CA6B1.3060201@Oracle.COM> vote:yes On 3/22/2012 4:46 PM, Jonathan Gibbons wrote: > I hereby propose the creation of the Code Tools Project[1] with > Jon Gibbons as the Lead and the Compiler Group as the sponsoring > Group(s). > > The goal of the Code Tools Project will be to provide tools of use to > OpenJDK developers while working on the OpenJDK code base. > Such tools currently include test tools and Mercurial extensions; > it is envisaged that additional tools will be added over time, > after discussion on the Project's main mailing list, and subject > to the Project Lead's approval. > > There are a number of initial candidates for inclusion in such a Project. > > * jtreg > jtreg is the regression test harness for the OpenJDK platform. > It is currently just available via source bundles [2]. > > * jtharness > jtharness is the test framework underlying jtreg [3]. > > * sigtest > sigtest is a set of utilities relating to API signature checking > [4]. > > * the Mercurial "jcheck" extension > jcheck provides simple validity checks on the contents of a > changeset > > Jon has long been involved in the tools aspects of testing JDK. > He designed the original JavaTest harness, underlying both JCK > and jtreg. Since joining the JDK LangTools team, he has led the > way in improving the reliability of test runs, both by improving > tests and/or the jtreg test harness. > > The suggested sets of initial reviewers and committers are based > upon the contributors to the initial set of tools listed above. > > The suggested initial set of Reviewers is: > > Mark Reinhold > John Coomes > Iris Clark > Brian Kurotsuchi > Dmitry Fazunenko > Mikhail Ershov > Kevin Looney > Andrey Titov > > In addition, the suggested initial set of Committers is: > > Larry Hoffman > Dawn Phillips > > Votes are due by 7:00AM UTC, Friday 6 April [7]. > > Only current OpenJDK Members [5] are eligible to vote on this > motion. > > For Lazy Consensus voting instructions, see [6]. > > -- Jon Gibbons > > [1] http://mail.openjdk.java.net/pipermail/discuss/2012-March/002563.html > [2] http://openjdk.java.net/jtreg > [3] http://jtharness.java.net/ > [4] http://sigtest.java.net/ > [5] http://openjdk.java.net/census/#members > [6] http://openjdk.java.net/projects/#new-project-vote > [7] > http://www.timeanddate.com/worldclock/fixedtime.html?msg=CFV%3A+New+Code+Tools+Project&iso=20120406T0000&p1=224 > -- Release Lead, Java SE Updates Java Platform Group Oracle Corporation. (408)276-7564 From Alan.Bateman at oracle.com Fri Mar 23 16:41:39 2012 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Fri, 23 Mar 2012 16:41:39 +0000 Subject: CFV: New Project: Code Tools In-Reply-To: <4F6BB9EA.6090904@oracle.com> References: <4F6BB9EA.6090904@oracle.com> Message-ID: <4F6CA7C3.5000901@oracle.com> Vote: yes From mandy.chung at oracle.com Fri Mar 23 16:46:30 2012 From: mandy.chung at oracle.com (Mandy Chung) Date: Fri, 23 Mar 2012 09:46:30 -0700 Subject: CFV: New Project: Code Tools In-Reply-To: <4F6BB9EA.6090904@oracle.com> References: <4F6BB9EA.6090904@oracle.com> Message-ID: <4F6CA8E6.9020406@oracle.com> Vote: yes From neugens.limasoftware at gmail.com Fri Mar 23 16:47:40 2012 From: neugens.limasoftware at gmail.com (Mario Torre) Date: Fri, 23 Mar 2012 17:47:40 +0100 Subject: CFV: New Project: Code Tools In-Reply-To: <4F6BB9EA.6090904@oracle.com> References: <4F6BB9EA.6090904@oracle.com> Message-ID: Vote: Yes. Cheers, Mario 2012/3/23 Jonathan Gibbons : > I hereby propose the creation of the Code Tools Project[1] with > Jon Gibbons as the Lead and the Compiler Group as the sponsoring > Group(s). > > The goal of the Code Tools Project will be to provide tools of use to > OpenJDK developers while working on the OpenJDK code base. > Such tools currently include test tools and Mercurial extensions; > it is envisaged that additional tools will be added over time, > after discussion on the Project's main mailing list, and subject > to the Project Lead's approval. > > There are a number of initial candidates for inclusion in such a Project. > > * jtreg > ? ? ?jtreg is the regression test harness for the OpenJDK platform. > ? ? ?It is currently just available via source bundles [2]. > > * jtharness > ? ? ?jtharness is the test framework underlying jtreg [3]. > > * sigtest > ? ? ?sigtest is a set of utilities relating to API signature checking [4]. > > * the Mercurial "jcheck" extension > ? ? ?jcheck provides simple validity checks on the contents of a changeset > > Jon has long been involved in the tools aspects of testing JDK. > He designed the original JavaTest harness, underlying both JCK > and jtreg. ?Since joining the JDK LangTools team, he has led the > way in improving the reliability of test runs, both by improving > tests and/or the jtreg test harness. > > The suggested sets of initial reviewers and committers are based > upon the contributors to the initial set of tools listed above. > > The suggested initial set of Reviewers is: > > ? ?Mark Reinhold > ? ?John Coomes > ? ?Iris Clark > ? ?Brian Kurotsuchi > ? ?Dmitry Fazunenko > ? ?Mikhail Ershov > ? ?Kevin Looney > ? ?Andrey Titov > > In addition, the suggested initial set of Committers is: > > ? ?Larry Hoffman > ? ?Dawn Phillips > > Votes are due by 7:00AM UTC, Friday 6 April [7]. > > Only current OpenJDK Members [5] are eligible to vote on this > motion. > > For Lazy Consensus voting instructions, see [6]. > > -- Jon Gibbons > > [1] http://mail.openjdk.java.net/pipermail/discuss/2012-March/002563.html > [2] http://openjdk.java.net/jtreg > [3] http://jtharness.java.net/ > [4] http://sigtest.java.net/ > [5] http://openjdk.java.net/census/#members > [6] http://openjdk.java.net/projects/#new-project-vote > [7] > http://www.timeanddate.com/worldclock/fixedtime.html?msg=CFV%3A+New+Code+Tools+Project&iso=20120406T0000&p1=224 > -- pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF Fingerprint: BA39 9666 94EC 8B73 27FA? FC7C 4086 63E3 80F2 40CF IcedRobot: www.icedrobot.org Proud GNU Classpath developer: http://www.classpath.org/ Read About us at: http://planet.classpath.org OpenJDK: http://openjdk.java.net/projects/caciocavallo/ Please, support open standards: http://endsoftpatents.org/ From aph at redhat.com Fri Mar 23 16:51:13 2012 From: aph at redhat.com (Andrew Haley) Date: Fri, 23 Mar 2012 16:51:13 +0000 Subject: CFV: New Project: Code Tools In-Reply-To: <4F6CA6B1.3060201@Oracle.COM> References: <4F6BB9EA.6090904@oracle.com> <4F6CA6B1.3060201@Oracle.COM> Message-ID: <4F6CAA01.8030200@redhat.com> vote:yes From iris.clark at oracle.com Fri Mar 23 17:05:31 2012 From: iris.clark at oracle.com (Iris Clark) Date: Fri, 23 Mar 2012 10:05:31 -0700 (PDT) Subject: CFV: New Project: Code Tools In-Reply-To: <4F6BB9EA.6090904@oracle.com> References: <4F6BB9EA.6090904@oracle.com> Message-ID: <95b58a4b-306a-4894-876a-6166c19a2a95@default> Vote: yes iris From joe.darcy at oracle.com Fri Mar 23 17:08:57 2012 From: joe.darcy at oracle.com (Joe Darcy) Date: Fri, 23 Mar 2012 10:08:57 -0700 Subject: CFV: New Project: Code Tools In-Reply-To: <4F6BB9EA.6090904@oracle.com> References: <4F6BB9EA.6090904@oracle.com> Message-ID: <4F6CAE29.1030900@oracle.com> Vote: yes -Joe On 03/22/2012 04:46 PM, Jonathan Gibbons wrote: > I hereby propose the creation of the Code Tools Project[1] with > Jon Gibbons as the Lead and the Compiler Group as the sponsoring > Group(s). > > The goal of the Code Tools Project will be to provide tools of use to > OpenJDK developers while working on the OpenJDK code base. > Such tools currently include test tools and Mercurial extensions; > it is envisaged that additional tools will be added over time, > after discussion on the Project's main mailing list, and subject > to the Project Lead's approval. > > There are a number of initial candidates for inclusion in such a Project. > > * jtreg > jtreg is the regression test harness for the OpenJDK platform. > It is currently just available via source bundles [2]. > > * jtharness > jtharness is the test framework underlying jtreg [3]. > > * sigtest > sigtest is a set of utilities relating to API signature checking > [4]. > > * the Mercurial "jcheck" extension > jcheck provides simple validity checks on the contents of a > changeset > > Jon has long been involved in the tools aspects of testing JDK. > He designed the original JavaTest harness, underlying both JCK > and jtreg. Since joining the JDK LangTools team, he has led the > way in improving the reliability of test runs, both by improving > tests and/or the jtreg test harness. > > The suggested sets of initial reviewers and committers are based > upon the contributors to the initial set of tools listed above. > > The suggested initial set of Reviewers is: > > Mark Reinhold > John Coomes > Iris Clark > Brian Kurotsuchi > Dmitry Fazunenko > Mikhail Ershov > Kevin Looney > Andrey Titov > > In addition, the suggested initial set of Committers is: > > Larry Hoffman > Dawn Phillips > > Votes are due by 7:00AM UTC, Friday 6 April [7]. > > Only current OpenJDK Members [5] are eligible to vote on this > motion. > > For Lazy Consensus voting instructions, see [6]. > > -- Jon Gibbons > > [1] http://mail.openjdk.java.net/pipermail/discuss/2012-March/002563.html > [2] http://openjdk.java.net/jtreg > [3] http://jtharness.java.net/ > [4] http://sigtest.java.net/ > [5] http://openjdk.java.net/census/#members > [6] http://openjdk.java.net/projects/#new-project-vote > [7] > http://www.timeanddate.com/worldclock/fixedtime.html?msg=CFV%3A+New+Code+Tools+Project&iso=20120406T0000&p1=224 > From John.Coomes at oracle.com Fri Mar 23 17:39:14 2012 From: John.Coomes at oracle.com (John Coomes) Date: Fri, 23 Mar 2012 10:39:14 -0700 Subject: CFV: New Project: Code Tools In-Reply-To: <4F6BB9EA.6090904@oracle.com> References: <4F6BB9EA.6090904@oracle.com> Message-ID: <20332.46402.502006.59415@oracle.com> Vote: yes From tom.rodriguez at oracle.com Fri Mar 23 18:06:15 2012 From: tom.rodriguez at oracle.com (Tom Rodriguez) Date: Fri, 23 Mar 2012 11:06:15 -0700 Subject: CFV: New Project: Code Tools In-Reply-To: <4F6BB9EA.6090904@oracle.com> References: <4F6BB9EA.6090904@oracle.com> Message-ID: Vote: yes On Mar 22, 2012, at 4:46 PM, Jonathan Gibbons wrote: > I hereby propose the creation of the Code Tools Project[1] with > Jon Gibbons as the Lead and the Compiler Group as the sponsoring > Group(s). > > The goal of the Code Tools Project will be to provide tools of use to > OpenJDK developers while working on the OpenJDK code base. > Such tools currently include test tools and Mercurial extensions; > it is envisaged that additional tools will be added over time, > after discussion on the Project's main mailing list, and subject > to the Project Lead's approval. > > There are a number of initial candidates for inclusion in such a Project. > > * jtreg > jtreg is the regression test harness for the OpenJDK platform. > It is currently just available via source bundles [2]. > > * jtharness > jtharness is the test framework underlying jtreg [3]. > > * sigtest > sigtest is a set of utilities relating to API signature checking [4]. > > * the Mercurial "jcheck" extension > jcheck provides simple validity checks on the contents of a changeset > > Jon has long been involved in the tools aspects of testing JDK. > He designed the original JavaTest harness, underlying both JCK > and jtreg. Since joining the JDK LangTools team, he has led the > way in improving the reliability of test runs, both by improving > tests and/or the jtreg test harness. > > The suggested sets of initial reviewers and committers are based > upon the contributors to the initial set of tools listed above. > > The suggested initial set of Reviewers is: > > Mark Reinhold > John Coomes > Iris Clark > Brian Kurotsuchi > Dmitry Fazunenko > Mikhail Ershov > Kevin Looney > Andrey Titov > > In addition, the suggested initial set of Committers is: > > Larry Hoffman > Dawn Phillips > > Votes are due by 7:00AM UTC, Friday 6 April [7]. > > Only current OpenJDK Members [5] are eligible to vote on this > motion. > > For Lazy Consensus voting instructions, see [6]. > > -- Jon Gibbons > > [1] http://mail.openjdk.java.net/pipermail/discuss/2012-March/002563.html > [2] http://openjdk.java.net/jtreg > [3] http://jtharness.java.net/ > [4] http://sigtest.java.net/ > [5] http://openjdk.java.net/census/#members > [6] http://openjdk.java.net/projects/#new-project-vote > [7] http://www.timeanddate.com/worldclock/fixedtime.html?msg=CFV%3A+New+Code+Tools+Project&iso=20120406T0000&p1=224 > From james.holmlund at oracle.com Fri Mar 23 18:23:40 2012 From: james.holmlund at oracle.com (Jim Holmlund) Date: Fri, 23 Mar 2012 11:23:40 -0700 Subject: CFV: New Project: Code Tools In-Reply-To: <4F6CAE29.1030900@oracle.com> References: <4F6BB9EA.6090904@oracle.com> <4F6CAE29.1030900@oracle.com> Message-ID: <4F6CBFAC.8080505@oracle.com> Vote: yes On 03/22/2012 04:46 PM, Jonathan Gibbons wrote: > I hereby propose the creation of the Code Tools Project[1] with > Jon Gibbons as the Lead and the Compiler Group as the sponsoring > Group(s). > > The goal of the Code Tools Project will be to provide tools of use to > OpenJDK developers while working on the OpenJDK code base. > Such tools currently include test tools and Mercurial extensions; > it is envisaged that additional tools will be added over time, > after discussion on the Project's main mailing list, and subject > to the Project Lead's approval. > > There are a number of initial candidates for inclusion in such a Project. > > * jtreg > jtreg is the regression test harness for the OpenJDK platform. > It is currently just available via source bundles [2]. > > * jtharness > jtharness is the test framework underlying jtreg [3]. > > * sigtest > sigtest is a set of utilities relating to API signature checking [4]. > > * the Mercurial "jcheck" extension > jcheck provides simple validity checks on the contents of a changeset > > Jon has long been involved in the tools aspects of testing JDK. > He designed the original JavaTest harness, underlying both JCK > and jtreg. Since joining the JDK LangTools team, he has led the > way in improving the reliability of test runs, both by improving > tests and/or the jtreg test harness. > > The suggested sets of initial reviewers and committers are based > upon the contributors to the initial set of tools listed above. > > The suggested initial set of Reviewers is: > > Mark Reinhold > John Coomes > Iris Clark > Brian Kurotsuchi > Dmitry Fazunenko > Mikhail Ershov > Kevin Looney > Andrey Titov > > In addition, the suggested initial set of Committers is: > > Larry Hoffman > Dawn Phillips > > Votes are due by 7:00AM UTC, Friday 6 April [7]. > > Only current OpenJDK Members [5] are eligible to vote on this > motion. > > For Lazy Consensus voting instructions, see [6]. > > -- Jon Gibbons > > [1] http://mail.openjdk.java.net/pipermail/discuss/2012-March/002563.html > [2] http://openjdk.java.net/jtreg > [3] http://jtharness.java.net/ > [4] http://sigtest.java.net/ > [5] http://openjdk.java.net/census/#members > [6] http://openjdk.java.net/projects/#new-project-vote > [7] > http://www.timeanddate.com/worldclock/fixedtime.html?msg=CFV%3A+New+Code+Tools+Project&iso=20120406T0000&p1=224 > > From mark.reinhold at oracle.com Fri Mar 23 18:28:04 2012 From: mark.reinhold at oracle.com (mark.reinhold at oracle.com) Date: Fri, 23 Mar 2012 11:28:04 -0700 Subject: CFV: New Project: Code Tools In-Reply-To: jonathan.gibbons@oracle.com; Thu, 22 Mar 2012 16:46:50 PDT; <4F6BB9EA.6090904@oracle.com> Message-ID: <20120323182804.BE1AB9D8@eggemoggin.niobe.net> Vote: yes - Mark From mark.reinhold at oracle.com Fri Mar 23 20:01:16 2012 From: mark.reinhold at oracle.com (mark.reinhold at oracle.com) Date: Fri, 23 Mar 2012 13:01:16 -0700 Subject: CFV: New Project: Code Tools In-Reply-To: abhi.saha@oracle.com; Fri, 23 Mar 2012 09:37:05 PDT; <4F6CA6B1.3060201@Oracle.COM> Message-ID: <20120323200116.9BB5C9D8@eggemoggin.niobe.net> 2012/3/23 9:37 -0700, abhi.saha at oracle.com: > vote:yes Thanks for voting, but since you're not (yet) an OpenJDK Member [1][2], you're not eligible to vote on proposals for new Projects. - Mark [1] http://openjdk.java.net/census/#members [2] http://openjdk.java.net/groups/members/ From chris.hegarty at oracle.com Fri Mar 23 22:41:31 2012 From: chris.hegarty at oracle.com (Chris Hegarty) Date: Fri, 23 Mar 2012 15:41:31 -0700 (PDT) Subject: CFV: New Project: Code Tools In-Reply-To: <4F6BB9EA.6090904@oracle.com> References: <4F6BB9EA.6090904@oracle.com> Message-ID: <4F6CFC1B.2060806@oracle.com> Vote: yes -Chris From james.graham at oracle.com Fri Mar 23 22:48:43 2012 From: james.graham at oracle.com (Jim Graham) Date: Fri, 23 Mar 2012 15:48:43 -0700 Subject: CFV: New Project: Code Tools In-Reply-To: <4F6BB9EA.6090904@oracle.com> References: <4F6BB9EA.6090904@oracle.com> Message-ID: <4F6CFDCB.4090000@oracle.com> Vote: yes ...jim From john.r.rose at oracle.com Sat Mar 24 00:03:17 2012 From: john.r.rose at oracle.com (John Rose) Date: Fri, 23 Mar 2012 17:03:17 -0700 Subject: CFV: New Project: Code Tools In-Reply-To: <4F6BB9EA.6090904@oracle.com> References: <4F6BB9EA.6090904@oracle.com> Message-ID: Vote: yes From bradford.wetmore at oracle.com Mon Mar 26 18:42:04 2012 From: bradford.wetmore at oracle.com (Brad Wetmore) Date: Mon, 26 Mar 2012 11:42:04 -0700 Subject: CFV: New Project: Code Tools In-Reply-To: References: <4F6BB9EA.6090904@oracle.com> Message-ID: <4F70B87C.5050308@oracle.com> Vote: yes From david.katleman at oracle.com Mon Mar 26 19:35:21 2012 From: david.katleman at oracle.com (David Katleman (Oracle)) Date: Mon, 26 Mar 2012 12:35:21 -0700 Subject: CFV: New Project: Code Tools In-Reply-To: <4F6BB9EA.6090904@oracle.com> References: <4F6BB9EA.6090904@oracle.com> Message-ID: <4F70C4F9.5010104@oracle.com> Vote: yes From ahughes at redhat.com Tue Mar 27 13:12:35 2012 From: ahughes at redhat.com (Andrew Hughes) Date: Tue, 27 Mar 2012 09:12:35 -0400 (EDT) Subject: CFV: New Project: Code Tools In-Reply-To: <4F6BB9EA.6090904@oracle.com> Message-ID: <4737f7bc-a44a-481b-a955-48b0dd4a3812@zmail17.collab.prod.int.phx2.redhat.com> ----- Original Message ----- > I hereby propose the creation of the Code Tools Project[1] with > Jon Gibbons as the Lead and the Compiler Group as the sponsoring > Group(s). > > The goal of the Code Tools Project will be to provide tools of use to > OpenJDK developers while working on the OpenJDK code base. > Such tools currently include test tools and Mercurial extensions; > it is envisaged that additional tools will be added over time, > after discussion on the Project's main mailing list, and subject > to the Project Lead's approval. > > There are a number of initial candidates for inclusion in such a > Project. > > * jtreg > jtreg is the regression test harness for the OpenJDK platform. > It is currently just available via source bundles [2]. > > * jtharness > jtharness is the test framework underlying jtreg [3]. > > * sigtest > sigtest is a set of utilities relating to API signature > checking [4]. > > * the Mercurial "jcheck" extension > jcheck provides simple validity checks on the contents of a > changeset > > Jon has long been involved in the tools aspects of testing JDK. > He designed the original JavaTest harness, underlying both JCK > and jtreg. Since joining the JDK LangTools team, he has led the > way in improving the reliability of test runs, both by improving > tests and/or the jtreg test harness. > > The suggested sets of initial reviewers and committers are based > upon the contributors to the initial set of tools listed above. > > The suggested initial set of Reviewers is: > > Mark Reinhold > John Coomes > Iris Clark > Brian Kurotsuchi > Dmitry Fazunenko > Mikhail Ershov > Kevin Looney > Andrey Titov > > In addition, the suggested initial set of Committers is: > > Larry Hoffman > Dawn Phillips > > Votes are due by 7:00AM UTC, Friday 6 April [7]. > > Only current OpenJDK Members [5] are eligible to vote on this > motion. > > For Lazy Consensus voting instructions, see [6]. > > -- Jon Gibbons > > [1] > http://mail.openjdk.java.net/pipermail/discuss/2012-March/002563.html > [2] http://openjdk.java.net/jtreg > [3] http://jtharness.java.net/ > [4] http://sigtest.java.net/ > [5] http://openjdk.java.net/census/#members > [6] http://openjdk.java.net/projects/#new-project-vote > [7] > http://www.timeanddate.com/worldclock/fixedtime.html?msg=CFV%3A+New+Code+Tools+Project&iso=20120406T0000&p1=224 > > Good to see this happening, and hopefully it means jcheck will finally be open-sourced? Vote: Yes -- Andrew :) Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) PGP Key: 248BDC07 (https://keys.indymedia.org/) Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07 From ahughes at redhat.com Tue Mar 27 13:59:10 2012 From: ahughes at redhat.com (Andrew Hughes) Date: Tue, 27 Mar 2012 09:59:10 -0400 (EDT) Subject: CFV: New Project: Code Tools In-Reply-To: <4737f7bc-a44a-481b-a955-48b0dd4a3812@zmail17.collab.prod.int.phx2.redhat.com> Message-ID: ----- Original Message ----- > ----- Original Message ----- > > I hereby propose the creation of the Code Tools Project[1] with > > Jon Gibbons as the Lead and the Compiler Group as the sponsoring > > Group(s). > > > > The goal of the Code Tools Project will be to provide tools of use > > to > > OpenJDK developers while working on the OpenJDK code base. > > Such tools currently include test tools and Mercurial extensions; > > it is envisaged that additional tools will be added over time, > > after discussion on the Project's main mailing list, and subject > > to the Project Lead's approval. > > > > There are a number of initial candidates for inclusion in such a > > Project. > > > > * jtreg > > jtreg is the regression test harness for the OpenJDK > > platform. > > It is currently just available via source bundles [2]. > > > > * jtharness > > jtharness is the test framework underlying jtreg [3]. > > > > * sigtest > > sigtest is a set of utilities relating to API signature > > checking [4]. > > > > * the Mercurial "jcheck" extension > > jcheck provides simple validity checks on the contents of a > > changeset > > > > Jon has long been involved in the tools aspects of testing JDK. > > He designed the original JavaTest harness, underlying both JCK > > and jtreg. Since joining the JDK LangTools team, he has led the > > way in improving the reliability of test runs, both by improving > > tests and/or the jtreg test harness. > > > > The suggested sets of initial reviewers and committers are based > > upon the contributors to the initial set of tools listed above. > > > > The suggested initial set of Reviewers is: > > > > Mark Reinhold > > John Coomes > > Iris Clark > > Brian Kurotsuchi > > Dmitry Fazunenko > > Mikhail Ershov > > Kevin Looney > > Andrey Titov > > > > In addition, the suggested initial set of Committers is: > > > > Larry Hoffman > > Dawn Phillips > > > > Votes are due by 7:00AM UTC, Friday 6 April [7]. > > > > Only current OpenJDK Members [5] are eligible to vote on this > > motion. > > > > For Lazy Consensus voting instructions, see [6]. > > > > -- Jon Gibbons > > > > [1] > > http://mail.openjdk.java.net/pipermail/discuss/2012-March/002563.html > > [2] http://openjdk.java.net/jtreg > > [3] http://jtharness.java.net/ > > [4] http://sigtest.java.net/ > > [5] http://openjdk.java.net/census/#members > > [6] http://openjdk.java.net/projects/#new-project-vote > > [7] > > http://www.timeanddate.com/worldclock/fixedtime.html?msg=CFV%3A+New+Code+Tools+Project&iso=20120406T0000&p1=224 > > > > > > Good to see this happening, and hopefully it means jcheck will > finally > be open-sourced? > > Vote: Yes > -- > Andrew :) > > Free Java Software Engineer > Red Hat, Inc. (http://www.redhat.com) > > PGP Key: 248BDC07 (https://keys.indymedia.org/) > Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07 > > Vote: Yes -- Andrew :) Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) PGP Key: 248BDC07 (https://keys.indymedia.org/) Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07