From james.laskey at oracle.com Wed Jun 4 15:26:03 2014 From: james.laskey at oracle.com (Jim Laskey (Oracle)) Date: Wed, 4 Jun 2014 12:26:03 -0300 Subject: CFV: New Project: Panama In-Reply-To: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: Vote: YES On Jun 4, 2014, at 2:19 AM, John Rose wrote: > I hereby propose the creation of Project Panama with myself (John > Rose) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project > will provide new connections between the Java virtual > machine and well-defined but "foreign" (non-Java) APIs, > including many interfaces commonly used by C programmers. > The project will provide an venue to incubate early work on > JEP 191[2] and similar enhancements, as discussed on my blog[3]. > > In short, the components developed in this project will support: > > * native code and data access between the JVM and native APIs > * tooling for header file API extraction and API metadata storage > * wrapper interposition for specialized safety invariants and value transformations > * basic bindings for selected native APIs > > The initial source of this project will be based on a clone of a JDK 9 > repository, most specifically the hotspot, langtools, and jdk > sub-repositories. We also plan (with appropriate permissions) to make > use of certain software components mentioned in JEP 191. To host > components which may not immediately fit into the existing repository > structure, there will also be a "scratch" repository modeled on that > of Sumatra[4]. > > The initial Reviewers and Committers will be: > > * David Chase (Reviewer, HotSpot/compiler) > * Mandy Chung (Reviewer, Core Libraries) > * Mike Duigou (Reviewer, Core Libraries) > * Vladimir Ivanov (Reviewer, HotSpot/compiler) > * Henry Jen (Committer, Core Libraries) > * Wayne Meissner (Committer, libffi/JNR) > * Charles Nutter (Reviewer, JRuby/JNR) > * Paul Sandoz (Committer, Core Libraries) > * David Simms (Committer, HotSpot/runtime) > * Attila Szegedi (Reviewer, Language Tools) > * Chris Thalinger (Reviewer, HotSpot/compiler) > * Bob Vandette (Reviewer, HotSpot/embedded) > > (In parentheses are their prospective Panama role and a current > OpenJDK or other affiliation. Reviewer status is assigned based on > previous review history. Note that, per OpenJDK requirements[5], > authoring for this project requires a filed Oracle Contributor > Agreement.) > > The project will maintain at least two mailing lists: > > * panama-dev for developers (as usual) > * panama-spec-experts for specification issues only > > For widest discussion of standardization questions, the specification > mailing list, distinct from the developer list, may include > participants from the Java Community Process who are not OpenJDK > contributors. This list will exclude discussion of implementation > code, and may be moderated or otherwise restricted to meet this goal. > > Change review will be determined by the Lead and a consensus of > Reviewers. Review is expected to be loose initially but made more > strict, perhaps on a per-component basis as components become > candidates for integration into Java SE releases such as JDK 9. > > Votes are due in two weeks, by 12:00 midnight June 18 2014 Pacific US Time > (18-06-2014 07:00 GMT). > > Only current OpenJDK Members [6] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [7]. > > Regards, > > John Rose > > [1] http://openjdk.java.net/projects/#new-project > [2] http://openjdk.java.net/jeps/191 > [3] https://blogs.oracle.com/jrose/entry/the_isthmus_in_the_vm > [4] http://hg.openjdk.java.net/sumatra/sumatra-dev/scratch/ > [5] http://openjdk.java.net/contribute/ > [6] http://openjdk.java.net/census#members > [7] http://openjdk.java.net/projects/#new-project-vote > From brian.goetz at oracle.com Wed Jun 4 15:28:27 2014 From: brian.goetz at oracle.com (Brian Goetz) Date: Wed, 04 Jun 2014 11:28:27 -0400 Subject: CFV: New Project: Panama In-Reply-To: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: <538F3B1B.2030006@oracle.com> Vote: Yes On 6/4/2014 1:19 AM, John Rose wrote: > I hereby propose the creation of Project Panama with myself (John > Rose) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project > will provide new connections between the Java virtual > machine and well-defined but "foreign" (non-Java) APIs, > including many interfaces commonly used by C programmers. > The project will provide an venue to incubate early work on > JEP 191[2] and similar enhancements, as discussed on my blog[3]. > > In short, the components developed in this project will support: > > * native code and data access between the JVM and native APIs > * tooling for header file API extraction and API metadata storage > * wrapper interposition for specialized safety invariants and value transformations > * basic bindings for selected native APIs > > The initial source of this project will be based on a clone of a JDK 9 > repository, most specifically the hotspot, langtools, and jdk > sub-repositories. We also plan (with appropriate permissions) to make > use of certain software components mentioned in JEP 191. To host > components which may not immediately fit into the existing repository > structure, there will also be a "scratch" repository modeled on that > of Sumatra[4]. > > The initial Reviewers and Committers will be: > > * David Chase (Reviewer, HotSpot/compiler) > * Mandy Chung (Reviewer, Core Libraries) > * Mike Duigou (Reviewer, Core Libraries) > * Vladimir Ivanov (Reviewer, HotSpot/compiler) > * Henry Jen (Committer, Core Libraries) > * Wayne Meissner (Committer, libffi/JNR) > * Charles Nutter (Reviewer, JRuby/JNR) > * Paul Sandoz (Committer, Core Libraries) > * David Simms (Committer, HotSpot/runtime) > * Attila Szegedi (Reviewer, Language Tools) > * Chris Thalinger (Reviewer, HotSpot/compiler) > * Bob Vandette (Reviewer, HotSpot/embedded) > > (In parentheses are their prospective Panama role and a current > OpenJDK or other affiliation. Reviewer status is assigned based on > previous review history. Note that, per OpenJDK requirements[5], > authoring for this project requires a filed Oracle Contributor > Agreement.) > > The project will maintain at least two mailing lists: > > * panama-dev for developers (as usual) > * panama-spec-experts for specification issues only > > For widest discussion of standardization questions, the specification > mailing list, distinct from the developer list, may include > participants from the Java Community Process who are not OpenJDK > contributors. This list will exclude discussion of implementation > code, and may be moderated or otherwise restricted to meet this goal. > > Change review will be determined by the Lead and a consensus of > Reviewers. Review is expected to be loose initially but made more > strict, perhaps on a per-component basis as components become > candidates for integration into Java SE releases such as JDK 9. > > Votes are due in two weeks, by 12:00 midnight June 18 2014 Pacific US Time > (18-06-2014 07:00 GMT). > > Only current OpenJDK Members [6] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [7]. > > Regards, > > John Rose > > [1] http://openjdk.java.net/projects/#new-project > [2] http://openjdk.java.net/jeps/191 > [3] https://blogs.oracle.com/jrose/entry/the_isthmus_in_the_vm > [4] http://hg.openjdk.java.net/sumatra/sumatra-dev/scratch/ > [5] http://openjdk.java.net/contribute/ > [6] http://openjdk.java.net/census#members > [7] http://openjdk.java.net/projects/#new-project-vote > From richard.bair at oracle.com Wed Jun 4 15:37:38 2014 From: richard.bair at oracle.com (Richard Bair) Date: Wed, 4 Jun 2014 08:37:38 -0700 Subject: CFV: New Project: Panama In-Reply-To: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: <7323CDB7-6B2D-43DB-B7D3-B79E32F511B2@oracle.com> Vote: YES On Jun 3, 2014, at 10:19 PM, John Rose wrote: > I hereby propose the creation of Project Panama with myself (John > Rose) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project > will provide new connections between the Java virtual > machine and well-defined but "foreign" (non-Java) APIs, > including many interfaces commonly used by C programmers. > The project will provide an venue to incubate early work on > JEP 191[2] and similar enhancements, as discussed on my blog[3]. > > In short, the components developed in this project will support: > > * native code and data access between the JVM and native APIs > * tooling for header file API extraction and API metadata storage > * wrapper interposition for specialized safety invariants and value transformations > * basic bindings for selected native APIs > > The initial source of this project will be based on a clone of a JDK 9 > repository, most specifically the hotspot, langtools, and jdk > sub-repositories. We also plan (with appropriate permissions) to make > use of certain software components mentioned in JEP 191. To host > components which may not immediately fit into the existing repository > structure, there will also be a "scratch" repository modeled on that > of Sumatra[4]. > > The initial Reviewers and Committers will be: > > * David Chase (Reviewer, HotSpot/compiler) > * Mandy Chung (Reviewer, Core Libraries) > * Mike Duigou (Reviewer, Core Libraries) > * Vladimir Ivanov (Reviewer, HotSpot/compiler) > * Henry Jen (Committer, Core Libraries) > * Wayne Meissner (Committer, libffi/JNR) > * Charles Nutter (Reviewer, JRuby/JNR) > * Paul Sandoz (Committer, Core Libraries) > * David Simms (Committer, HotSpot/runtime) > * Attila Szegedi (Reviewer, Language Tools) > * Chris Thalinger (Reviewer, HotSpot/compiler) > * Bob Vandette (Reviewer, HotSpot/embedded) > > (In parentheses are their prospective Panama role and a current > OpenJDK or other affiliation. Reviewer status is assigned based on > previous review history. Note that, per OpenJDK requirements[5], > authoring for this project requires a filed Oracle Contributor > Agreement.) > > The project will maintain at least two mailing lists: > > * panama-dev for developers (as usual) > * panama-spec-experts for specification issues only > > For widest discussion of standardization questions, the specification > mailing list, distinct from the developer list, may include > participants from the Java Community Process who are not OpenJDK > contributors. This list will exclude discussion of implementation > code, and may be moderated or otherwise restricted to meet this goal. > > Change review will be determined by the Lead and a consensus of > Reviewers. Review is expected to be loose initially but made more > strict, perhaps on a per-component basis as components become > candidates for integration into Java SE releases such as JDK 9. > > Votes are due in two weeks, by 12:00 midnight June 18 2014 Pacific US Time > (18-06-2014 07:00 GMT). > > Only current OpenJDK Members [6] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [7]. > > Regards, > > John Rose > > [1] http://openjdk.java.net/projects/#new-project > [2] http://openjdk.java.net/jeps/191 > [3] https://blogs.oracle.com/jrose/entry/the_isthmus_in_the_vm > [4] http://hg.openjdk.java.net/sumatra/sumatra-dev/scratch/ > [5] http://openjdk.java.net/contribute/ > [6] http://openjdk.java.net/census#members > [7] http://openjdk.java.net/projects/#new-project-vote > From omajid at redhat.com Wed Jun 4 15:52:19 2014 From: omajid at redhat.com (Omair Majid) Date: Wed, 4 Jun 2014 11:52:19 -0400 Subject: CFV: New Project: Panama In-Reply-To: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: <20140604155219.GC2370@redhat.com> Vote: Yes * John Rose [2014-06-04 11:23]: > I hereby propose the creation of Project Panama with myself (John > Rose) as the Lead and the HotSpot Group as the sponsoring Group. Cheers, Omair -- PGP Key: 66484681 (http://pgp.mit.edu/) Fingerprint = F072 555B 0A17 3957 4E95 0056 F286 F14F 6648 4681 From jon.masamitsu at oracle.com Wed Jun 4 15:58:46 2014 From: jon.masamitsu at oracle.com (Jon Masamitsu) Date: Wed, 04 Jun 2014 08:58:46 -0700 Subject: CFV: New Project: Panama In-Reply-To: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: <538F4236.8070106@oracle.com> Vote: Yes On 6/3/2014 10:19 PM, John Rose wrote: > I hereby propose the creation of Project Panama with myself (John > Rose) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project > will provide new connections between the Java virtual > machine and well-defined but "foreign" (non-Java) APIs, > including many interfaces commonly used by C programmers. > The project will provide an venue to incubate early work on > JEP 191[2] and similar enhancements, as discussed on my blog[3]. > > In short, the components developed in this project will support: > > * native code and data access between the JVM and native APIs > * tooling for header file API extraction and API metadata storage > * wrapper interposition for specialized safety invariants and value transformations > * basic bindings for selected native APIs > > The initial source of this project will be based on a clone of a JDK 9 > repository, most specifically the hotspot, langtools, and jdk > sub-repositories. We also plan (with appropriate permissions) to make > use of certain software components mentioned in JEP 191. To host > components which may not immediately fit into the existing repository > structure, there will also be a "scratch" repository modeled on that > of Sumatra[4]. > > The initial Reviewers and Committers will be: > > * David Chase (Reviewer, HotSpot/compiler) > * Mandy Chung (Reviewer, Core Libraries) > * Mike Duigou (Reviewer, Core Libraries) > * Vladimir Ivanov (Reviewer, HotSpot/compiler) > * Henry Jen (Committer, Core Libraries) > * Wayne Meissner (Committer, libffi/JNR) > * Charles Nutter (Reviewer, JRuby/JNR) > * Paul Sandoz (Committer, Core Libraries) > * David Simms (Committer, HotSpot/runtime) > * Attila Szegedi (Reviewer, Language Tools) > * Chris Thalinger (Reviewer, HotSpot/compiler) > * Bob Vandette (Reviewer, HotSpot/embedded) > > (In parentheses are their prospective Panama role and a current > OpenJDK or other affiliation. Reviewer status is assigned based on > previous review history. Note that, per OpenJDK requirements[5], > authoring for this project requires a filed Oracle Contributor > Agreement.) > > The project will maintain at least two mailing lists: > > * panama-dev for developers (as usual) > * panama-spec-experts for specification issues only > > For widest discussion of standardization questions, the specification > mailing list, distinct from the developer list, may include > participants from the Java Community Process who are not OpenJDK > contributors. This list will exclude discussion of implementation > code, and may be moderated or otherwise restricted to meet this goal. > > Change review will be determined by the Lead and a consensus of > Reviewers. Review is expected to be loose initially but made more > strict, perhaps on a per-component basis as components become > candidates for integration into Java SE releases such as JDK 9. > > Votes are due in two weeks, by 12:00 midnight June 18 2014 Pacific US Time > (18-06-2014 07:00 GMT). > > Only current OpenJDK Members [6] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [7]. > > Regards, > > John Rose > > [1] http://openjdk.java.net/projects/#new-project > [2] http://openjdk.java.net/jeps/191 > [3] https://blogs.oracle.com/jrose/entry/the_isthmus_in_the_vm > [4] http://hg.openjdk.java.net/sumatra/sumatra-dev/scratch/ > [5] http://openjdk.java.net/contribute/ > [6] http://openjdk.java.net/census#members > [7] http://openjdk.java.net/projects/#new-project-vote > From aph at redhat.com Wed Jun 4 17:07:05 2014 From: aph at redhat.com (Andrew Haley) Date: Wed, 04 Jun 2014 18:07:05 +0100 Subject: CFV: New Project: Panama In-Reply-To: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: <538F5239.2070907@redhat.com> Vote: Yes On 06/04/2014 06:19 AM, John Rose wrote: > I hereby propose the creation of Project Panama with myself (John > Rose) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project > will provide new connections between the Java virtual > machine and well-defined but "foreign" (non-Java) APIs, > including many interfaces commonly used by C programmers. > The project will provide an venue to incubate early work on > JEP 191[2] and similar enhancements, as discussed on my blog[3]. > > In short, the components developed in this project will support: > > * native code and data access between the JVM and native APIs > * tooling for header file API extraction and API metadata storage > * wrapper interposition for specialized safety invariants and value transformations > * basic bindings for selected native APIs > > The initial source of this project will be based on a clone of a JDK 9 > repository, most specifically the hotspot, langtools, and jdk > sub-repositories. We also plan (with appropriate permissions) to make > use of certain software components mentioned in JEP 191. To host > components which may not immediately fit into the existing repository > structure, there will also be a "scratch" repository modeled on that > of Sumatra[4]. > > The initial Reviewers and Committers will be: > > * David Chase (Reviewer, HotSpot/compiler) > * Mandy Chung (Reviewer, Core Libraries) > * Mike Duigou (Reviewer, Core Libraries) > * Vladimir Ivanov (Reviewer, HotSpot/compiler) > * Henry Jen (Committer, Core Libraries) > * Wayne Meissner (Committer, libffi/JNR) > * Charles Nutter (Reviewer, JRuby/JNR) > * Paul Sandoz (Committer, Core Libraries) > * David Simms (Committer, HotSpot/runtime) > * Attila Szegedi (Reviewer, Language Tools) > * Chris Thalinger (Reviewer, HotSpot/compiler) > * Bob Vandette (Reviewer, HotSpot/embedded) > > (In parentheses are their prospective Panama role and a current > OpenJDK or other affiliation. Reviewer status is assigned based on > previous review history. Note that, per OpenJDK requirements[5], > authoring for this project requires a filed Oracle Contributor > Agreement.) > > The project will maintain at least two mailing lists: > > * panama-dev for developers (as usual) > * panama-spec-experts for specification issues only > > For widest discussion of standardization questions, the specification > mailing list, distinct from the developer list, may include > participants from the Java Community Process who are not OpenJDK > contributors. This list will exclude discussion of implementation > code, and may be moderated or otherwise restricted to meet this goal. > > Change review will be determined by the Lead and a consensus of > Reviewers. Review is expected to be loose initially but made more > strict, perhaps on a per-component basis as components become > candidates for integration into Java SE releases such as JDK 9. > > Votes are due in two weeks, by 12:00 midnight June 18 2014 Pacific US Time > (18-06-2014 07:00 GMT). > > Only current OpenJDK Members [6] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [7]. > > Regards, > > John Rose > > [1] http://openjdk.java.net/projects/#new-project > [2] http://openjdk.java.net/jeps/191 > [3] https://blogs.oracle.com/jrose/entry/the_isthmus_in_the_vm > [4] http://hg.openjdk.java.net/sumatra/sumatra-dev/scratch/ > [5] http://openjdk.java.net/contribute/ > [6] http://openjdk.java.net/census#members > [7] http://openjdk.java.net/projects/#new-project-vote > From karen.kinnear at oracle.com Wed Jun 4 17:09:32 2014 From: karen.kinnear at oracle.com (Karen Kinnear) Date: Wed, 4 Jun 2014 13:09:32 -0400 Subject: CFV: New Project: Panama In-Reply-To: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: vote: yes On Jun 4, 2014, at 1:19 AM, John Rose wrote: > I hereby propose the creation of Project Panama with myself (John > Rose) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project > will provide new connections between the Java virtual > machine and well-defined but "foreign" (non-Java) APIs, > including many interfaces commonly used by C programmers. > The project will provide an venue to incubate early work on > JEP 191[2] and similar enhancements, as discussed on my blog[3]. > > In short, the components developed in this project will support: > > * native code and data access between the JVM and native APIs > * tooling for header file API extraction and API metadata storage > * wrapper interposition for specialized safety invariants and value transformations > * basic bindings for selected native APIs > > The initial source of this project will be based on a clone of a JDK 9 > repository, most specifically the hotspot, langtools, and jdk > sub-repositories. We also plan (with appropriate permissions) to make > use of certain software components mentioned in JEP 191. To host > components which may not immediately fit into the existing repository > structure, there will also be a "scratch" repository modeled on that > of Sumatra[4]. > > The initial Reviewers and Committers will be: > > * David Chase (Reviewer, HotSpot/compiler) > * Mandy Chung (Reviewer, Core Libraries) > * Mike Duigou (Reviewer, Core Libraries) > * Vladimir Ivanov (Reviewer, HotSpot/compiler) > * Henry Jen (Committer, Core Libraries) > * Wayne Meissner (Committer, libffi/JNR) > * Charles Nutter (Reviewer, JRuby/JNR) > * Paul Sandoz (Committer, Core Libraries) > * David Simms (Committer, HotSpot/runtime) > * Attila Szegedi (Reviewer, Language Tools) > * Chris Thalinger (Reviewer, HotSpot/compiler) > * Bob Vandette (Reviewer, HotSpot/embedded) > > (In parentheses are their prospective Panama role and a current > OpenJDK or other affiliation. Reviewer status is assigned based on > previous review history. Note that, per OpenJDK requirements[5], > authoring for this project requires a filed Oracle Contributor > Agreement.) > > The project will maintain at least two mailing lists: > > * panama-dev for developers (as usual) > * panama-spec-experts for specification issues only > > For widest discussion of standardization questions, the specification > mailing list, distinct from the developer list, may include > participants from the Java Community Process who are not OpenJDK > contributors. This list will exclude discussion of implementation > code, and may be moderated or otherwise restricted to meet this goal. > > Change review will be determined by the Lead and a consensus of > Reviewers. Review is expected to be loose initially but made more > strict, perhaps on a per-component basis as components become > candidates for integration into Java SE releases such as JDK 9. > > Votes are due in two weeks, by 12:00 midnight June 18 2014 Pacific US Time > (18-06-2014 07:00 GMT). > > Only current OpenJDK Members [6] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [7]. > > Regards, > > John Rose > > [1] http://openjdk.java.net/projects/#new-project > [2] http://openjdk.java.net/jeps/191 > [3] https://blogs.oracle.com/jrose/entry/the_isthmus_in_the_vm > [4] http://hg.openjdk.java.net/sumatra/sumatra-dev/scratch/ > [5] http://openjdk.java.net/contribute/ > [6] http://openjdk.java.net/census#members > [7] http://openjdk.java.net/projects/#new-project-vote > From maurizio.cimadamore at oracle.com Wed Jun 4 17:21:46 2014 From: maurizio.cimadamore at oracle.com (Maurizio Cimadamore) Date: Wed, 04 Jun 2014 18:21:46 +0100 Subject: CFV: New Project: Panama In-Reply-To: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: <538F55AA.6010503@oracle.com> Vote: yes Maurizio On 04/06/14 06:19, John Rose wrote: > I hereby propose the creation of Project Panama with myself (John > Rose) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project > will provide new connections between the Java virtual > machine and well-defined but "foreign" (non-Java) APIs, > including many interfaces commonly used by C programmers. > The project will provide an venue to incubate early work on > JEP 191[2] and similar enhancements, as discussed on my blog[3]. > > In short, the components developed in this project will support: > > * native code and data access between the JVM and native APIs > * tooling for header file API extraction and API metadata storage > * wrapper interposition for specialized safety invariants and value transformations > * basic bindings for selected native APIs > > The initial source of this project will be based on a clone of a JDK 9 > repository, most specifically the hotspot, langtools, and jdk > sub-repositories. We also plan (with appropriate permissions) to make > use of certain software components mentioned in JEP 191. To host > components which may not immediately fit into the existing repository > structure, there will also be a "scratch" repository modeled on that > of Sumatra[4]. > > The initial Reviewers and Committers will be: > > * David Chase (Reviewer, HotSpot/compiler) > * Mandy Chung (Reviewer, Core Libraries) > * Mike Duigou (Reviewer, Core Libraries) > * Vladimir Ivanov (Reviewer, HotSpot/compiler) > * Henry Jen (Committer, Core Libraries) > * Wayne Meissner (Committer, libffi/JNR) > * Charles Nutter (Reviewer, JRuby/JNR) > * Paul Sandoz (Committer, Core Libraries) > * David Simms (Committer, HotSpot/runtime) > * Attila Szegedi (Reviewer, Language Tools) > * Chris Thalinger (Reviewer, HotSpot/compiler) > * Bob Vandette (Reviewer, HotSpot/embedded) > > (In parentheses are their prospective Panama role and a current > OpenJDK or other affiliation. Reviewer status is assigned based on > previous review history. Note that, per OpenJDK requirements[5], > authoring for this project requires a filed Oracle Contributor > Agreement.) > > The project will maintain at least two mailing lists: > > * panama-dev for developers (as usual) > * panama-spec-experts for specification issues only > > For widest discussion of standardization questions, the specification > mailing list, distinct from the developer list, may include > participants from the Java Community Process who are not OpenJDK > contributors. This list will exclude discussion of implementation > code, and may be moderated or otherwise restricted to meet this goal. > > Change review will be determined by the Lead and a consensus of > Reviewers. Review is expected to be loose initially but made more > strict, perhaps on a per-component basis as components become > candidates for integration into Java SE releases such as JDK 9. > > Votes are due in two weeks, by 12:00 midnight June 18 2014 Pacific US Time > (18-06-2014 07:00 GMT). > > Only current OpenJDK Members [6] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [7]. > > Regards, > > John Rose > > [1] http://openjdk.java.net/projects/#new-project > [2] http://openjdk.java.net/jeps/191 > [3] https://blogs.oracle.com/jrose/entry/the_isthmus_in_the_vm > [4] http://hg.openjdk.java.net/sumatra/sumatra-dev/scratch/ > [5] http://openjdk.java.net/contribute/ > [6] http://openjdk.java.net/census#members > [7] http://openjdk.java.net/projects/#new-project-vote > From alex.buckley at oracle.com Wed Jun 4 18:39:10 2014 From: alex.buckley at oracle.com (Alex Buckley) Date: Wed, 04 Jun 2014 11:39:10 -0700 Subject: CFV: New Project: Panama In-Reply-To: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: <538F67CE.8080304@oracle.com> A minor admin point: On 6/3/2014 10:19 PM, John Rose wrote: > The project will maintain at least two mailing lists: > > * panama-dev for developers (as usual) > * panama-spec-experts for specification issues only I recommend panama-spec-discuss as the name of the latter. The term 'experts' is suggestive of an Expert Group for a JSR, which the Panama incubator probably wants to hold at arm's length for the time being. The -spec-discuss idiom is seen in enhanced-metadata-spec-discuss and jdbc-spec-discuss at http://mail.openjdk.java.net/mailman/listinfo. Alex From neugens.limasoftware at gmail.com Wed Jun 4 18:48:20 2014 From: neugens.limasoftware at gmail.com (Mario Torre) Date: Wed, 4 Jun 2014 20:48:20 +0200 Subject: CFV: New Project: Panama In-Reply-To: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: Vote: Yes, Cheers, Mario 2014-06-04 7:19 GMT+02:00 John Rose : > I hereby propose the creation of Project Panama with myself (John > Rose) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project > will provide new connections between the Java virtual > machine and well-defined but "foreign" (non-Java) APIs, > including many interfaces commonly used by C programmers. > The project will provide an venue to incubate early work on > JEP 191[2] and similar enhancements, as discussed on my blog[3]. > > In short, the components developed in this project will support: > > * native code and data access between the JVM and native APIs > * tooling for header file API extraction and API metadata storage > * wrapper interposition for specialized safety invariants and value transformations > * basic bindings for selected native APIs > > The initial source of this project will be based on a clone of a JDK 9 > repository, most specifically the hotspot, langtools, and jdk > sub-repositories. We also plan (with appropriate permissions) to make > use of certain software components mentioned in JEP 191. To host > components which may not immediately fit into the existing repository > structure, there will also be a "scratch" repository modeled on that > of Sumatra[4]. > > The initial Reviewers and Committers will be: > > * David Chase (Reviewer, HotSpot/compiler) > * Mandy Chung (Reviewer, Core Libraries) > * Mike Duigou (Reviewer, Core Libraries) > * Vladimir Ivanov (Reviewer, HotSpot/compiler) > * Henry Jen (Committer, Core Libraries) > * Wayne Meissner (Committer, libffi/JNR) > * Charles Nutter (Reviewer, JRuby/JNR) > * Paul Sandoz (Committer, Core Libraries) > * David Simms (Committer, HotSpot/runtime) > * Attila Szegedi (Reviewer, Language Tools) > * Chris Thalinger (Reviewer, HotSpot/compiler) > * Bob Vandette (Reviewer, HotSpot/embedded) > > (In parentheses are their prospective Panama role and a current > OpenJDK or other affiliation. Reviewer status is assigned based on > previous review history. Note that, per OpenJDK requirements[5], > authoring for this project requires a filed Oracle Contributor > Agreement.) > > The project will maintain at least two mailing lists: > > * panama-dev for developers (as usual) > * panama-spec-experts for specification issues only > > For widest discussion of standardization questions, the specification > mailing list, distinct from the developer list, may include > participants from the Java Community Process who are not OpenJDK > contributors. This list will exclude discussion of implementation > code, and may be moderated or otherwise restricted to meet this goal. > > Change review will be determined by the Lead and a consensus of > Reviewers. Review is expected to be loose initially but made more > strict, perhaps on a per-component basis as components become > candidates for integration into Java SE releases such as JDK 9. > > Votes are due in two weeks, by 12:00 midnight June 18 2014 Pacific US Time > (18-06-2014 07:00 GMT). > > Only current OpenJDK Members [6] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [7]. > > Regards, > > John Rose > > [1] http://openjdk.java.net/projects/#new-project > [2] http://openjdk.java.net/jeps/191 > [3] https://blogs.oracle.com/jrose/entry/the_isthmus_in_the_vm > [4] http://hg.openjdk.java.net/sumatra/sumatra-dev/scratch/ > [5] http://openjdk.java.net/contribute/ > [6] http://openjdk.java.net/census#members > [7] http://openjdk.java.net/projects/#new-project-vote > -- pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF Blog: http://neugens.wordpress.com - Twitter: @neugens 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 paul.sandoz at oracle.com Thu Jun 5 07:28:38 2014 From: paul.sandoz at oracle.com (Paul Sandoz) Date: Thu, 5 Jun 2014 09:28:38 +0200 Subject: CFV: New Project: Panama In-Reply-To: References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: <97A7664F-82B2-4ADA-B6D0-B45F854D94C7@oracle.com> Vote: yes Paul. From david.holmes at oracle.com Thu Jun 5 11:30:39 2014 From: david.holmes at oracle.com (David Holmes) Date: Thu, 05 Jun 2014 21:30:39 +1000 Subject: CFV: New Project: Panama In-Reply-To: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: <539054DF.1070905@oracle.com> Vote: yes David On 4/06/2014 3:19 PM, John Rose wrote: > I hereby propose the creation of Project Panama with myself (John > Rose) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project > will provide new connections between the Java virtual > machine and well-defined but "foreign" (non-Java) APIs, > including many interfaces commonly used by C programmers. > The project will provide an venue to incubate early work on > JEP 191[2] and similar enhancements, as discussed on my blog[3]. > > In short, the components developed in this project will support: > > * native code and data access between the JVM and native APIs > * tooling for header file API extraction and API metadata storage > * wrapper interposition for specialized safety invariants and value transformations > * basic bindings for selected native APIs > > The initial source of this project will be based on a clone of a JDK 9 > repository, most specifically the hotspot, langtools, and jdk > sub-repositories. We also plan (with appropriate permissions) to make > use of certain software components mentioned in JEP 191. To host > components which may not immediately fit into the existing repository > structure, there will also be a "scratch" repository modeled on that > of Sumatra[4]. > > The initial Reviewers and Committers will be: > > * David Chase (Reviewer, HotSpot/compiler) > * Mandy Chung (Reviewer, Core Libraries) > * Mike Duigou (Reviewer, Core Libraries) > * Vladimir Ivanov (Reviewer, HotSpot/compiler) > * Henry Jen (Committer, Core Libraries) > * Wayne Meissner (Committer, libffi/JNR) > * Charles Nutter (Reviewer, JRuby/JNR) > * Paul Sandoz (Committer, Core Libraries) > * David Simms (Committer, HotSpot/runtime) > * Attila Szegedi (Reviewer, Language Tools) > * Chris Thalinger (Reviewer, HotSpot/compiler) > * Bob Vandette (Reviewer, HotSpot/embedded) > > (In parentheses are their prospective Panama role and a current > OpenJDK or other affiliation. Reviewer status is assigned based on > previous review history. Note that, per OpenJDK requirements[5], > authoring for this project requires a filed Oracle Contributor > Agreement.) > > The project will maintain at least two mailing lists: > > * panama-dev for developers (as usual) > * panama-spec-experts for specification issues only > > For widest discussion of standardization questions, the specification > mailing list, distinct from the developer list, may include > participants from the Java Community Process who are not OpenJDK > contributors. This list will exclude discussion of implementation > code, and may be moderated or otherwise restricted to meet this goal. > > Change review will be determined by the Lead and a consensus of > Reviewers. Review is expected to be loose initially but made more > strict, perhaps on a per-component basis as components become > candidates for integration into Java SE releases such as JDK 9. > > Votes are due in two weeks, by 12:00 midnight June 18 2014 Pacific US Time > (18-06-2014 07:00 GMT). > > Only current OpenJDK Members [6] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [7]. > > Regards, > > John Rose > > [1] http://openjdk.java.net/projects/#new-project > [2] http://openjdk.java.net/jeps/191 > [3] https://blogs.oracle.com/jrose/entry/the_isthmus_in_the_vm > [4] http://hg.openjdk.java.net/sumatra/sumatra-dev/scratch/ > [5] http://openjdk.java.net/contribute/ > [6] http://openjdk.java.net/census#members > [7] http://openjdk.java.net/projects/#new-project-vote > From Alan.Bateman at oracle.com Thu Jun 5 12:11:19 2014 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Thu, 05 Jun 2014 13:11:19 +0100 Subject: CFV: New Project: Panama In-Reply-To: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: <53905E67.3060108@oracle.com> Vote: yes From mandy.chung at oracle.com Thu Jun 5 14:12:16 2014 From: mandy.chung at oracle.com (Mandy Chung) Date: Thu, 05 Jun 2014 07:12:16 -0700 Subject: CFV: New Project: Panama In-Reply-To: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: <53907AC0.9060600@oracle.com> Vote: yes Mandy On 6/3/2014 10:19 PM, John Rose wrote: > I hereby propose the creation of Project Panama with myself (John > Rose) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project > will provide new connections between the Java virtual > machine and well-defined but "foreign" (non-Java) APIs, > including many interfaces commonly used by C programmers. > The project will provide an venue to incubate early work on > JEP 191[2] and similar enhancements, as discussed on my blog[3]. > > In short, the components developed in this project will support: > > * native code and data access between the JVM and native APIs > * tooling for header file API extraction and API metadata storage > * wrapper interposition for specialized safety invariants and value transformations > * basic bindings for selected native APIs > > The initial source of this project will be based on a clone of a JDK 9 > repository, most specifically the hotspot, langtools, and jdk > sub-repositories. We also plan (with appropriate permissions) to make > use of certain software components mentioned in JEP 191. To host > components which may not immediately fit into the existing repository > structure, there will also be a "scratch" repository modeled on that > of Sumatra[4]. > > The initial Reviewers and Committers will be: > > * David Chase (Reviewer, HotSpot/compiler) > * Mandy Chung (Reviewer, Core Libraries) > * Mike Duigou (Reviewer, Core Libraries) > * Vladimir Ivanov (Reviewer, HotSpot/compiler) > * Henry Jen (Committer, Core Libraries) > * Wayne Meissner (Committer, libffi/JNR) > * Charles Nutter (Reviewer, JRuby/JNR) > * Paul Sandoz (Committer, Core Libraries) > * David Simms (Committer, HotSpot/runtime) > * Attila Szegedi (Reviewer, Language Tools) > * Chris Thalinger (Reviewer, HotSpot/compiler) > * Bob Vandette (Reviewer, HotSpot/embedded) > > (In parentheses are their prospective Panama role and a current > OpenJDK or other affiliation. Reviewer status is assigned based on > previous review history. Note that, per OpenJDK requirements[5], > authoring for this project requires a filed Oracle Contributor > Agreement.) > > The project will maintain at least two mailing lists: > > * panama-dev for developers (as usual) > * panama-spec-experts for specification issues only > > For widest discussion of standardization questions, the specification > mailing list, distinct from the developer list, may include > participants from the Java Community Process who are not OpenJDK > contributors. This list will exclude discussion of implementation > code, and may be moderated or otherwise restricted to meet this goal. > > Change review will be determined by the Lead and a consensus of > Reviewers. Review is expected to be loose initially but made more > strict, perhaps on a per-component basis as components become > candidates for integration into Java SE releases such as JDK 9. > > Votes are due in two weeks, by 12:00 midnight June 18 2014 Pacific US Time > (18-06-2014 07:00 GMT). > > Only current OpenJDK Members [6] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [7]. > > Regards, > > John Rose > > [1] http://openjdk.java.net/projects/#new-project > [2] http://openjdk.java.net/jeps/191 > [3] https://blogs.oracle.com/jrose/entry/the_isthmus_in_the_vm > [4] http://hg.openjdk.java.net/sumatra/sumatra-dev/scratch/ > [5] http://openjdk.java.net/contribute/ > [6] http://openjdk.java.net/census#members > [7] http://openjdk.java.net/projects/#new-project-vote > From mark.reinhold at oracle.com Thu Jun 5 14:34:28 2014 From: mark.reinhold at oracle.com (mark.reinhold at oracle.com) Date: Thu, 05 Jun 2014 07:34:28 -0700 Subject: CFV: New Project: Panama In-Reply-To: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: <20140605073428.832165@eggemoggin.niobe.net> Vote: yes - Mark From ivan at azulsystems.com Thu Jun 5 14:46:47 2014 From: ivan at azulsystems.com (Ivan Krylov) Date: Thu, 5 Jun 2014 14:46:47 +0000 Subject: CFV: New Project: Panama In-Reply-To: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: <859D222D-6920-4625-9330-118166BF4947@azulsystems.com> Vote: yes On 4 Jun 2014, at 09:19, John Rose wrote: > I hereby propose the creation of Project Panama with myself (John > Rose) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project > will provide new connections between the Java virtual > machine and well-defined but "foreign" (non-Java) APIs, > including many interfaces commonly used by C programmers. > The project will provide an venue to incubate early work on > JEP 191[2] and similar enhancements, as discussed on my blog[3]. > > In short, the components developed in this project will support: > > * native code and data access between the JVM and native APIs > * tooling for header file API extraction and API metadata storage > * wrapper interposition for specialized safety invariants and value transformations > * basic bindings for selected native APIs > > The initial source of this project will be based on a clone of a JDK 9 > repository, most specifically the hotspot, langtools, and jdk > sub-repositories. We also plan (with appropriate permissions) to make > use of certain software components mentioned in JEP 191. To host > components which may not immediately fit into the existing repository > structure, there will also be a "scratch" repository modeled on that > of Sumatra[4]. > > The initial Reviewers and Committers will be: > > * David Chase (Reviewer, HotSpot/compiler) > * Mandy Chung (Reviewer, Core Libraries) > * Mike Duigou (Reviewer, Core Libraries) > * Vladimir Ivanov (Reviewer, HotSpot/compiler) > * Henry Jen (Committer, Core Libraries) > * Wayne Meissner (Committer, libffi/JNR) > * Charles Nutter (Reviewer, JRuby/JNR) > * Paul Sandoz (Committer, Core Libraries) > * David Simms (Committer, HotSpot/runtime) > * Attila Szegedi (Reviewer, Language Tools) > * Chris Thalinger (Reviewer, HotSpot/compiler) > * Bob Vandette (Reviewer, HotSpot/embedded) > > (In parentheses are their prospective Panama role and a current > OpenJDK or other affiliation. Reviewer status is assigned based on > previous review history. Note that, per OpenJDK requirements[5], > authoring for this project requires a filed Oracle Contributor > Agreement.) > > The project will maintain at least two mailing lists: > > * panama-dev for developers (as usual) > * panama-spec-experts for specification issues only > > For widest discussion of standardization questions, the specification > mailing list, distinct from the developer list, may include > participants from the Java Community Process who are not OpenJDK > contributors. This list will exclude discussion of implementation > code, and may be moderated or otherwise restricted to meet this goal. > > Change review will be determined by the Lead and a consensus of > Reviewers. Review is expected to be loose initially but made more > strict, perhaps on a per-component basis as components become > candidates for integration into Java SE releases such as JDK 9. > > Votes are due in two weeks, by 12:00 midnight June 18 2014 Pacific US Time > (18-06-2014 07:00 GMT). > > Only current OpenJDK Members [6] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [7]. > > Regards, > > John Rose > > [1] http://openjdk.java.net/projects/#new-project > [2] http://openjdk.java.net/jeps/191 > [3] https://blogs.oracle.com/jrose/entry/the_isthmus_in_the_vm > [4] http://hg.openjdk.java.net/sumatra/sumatra-dev/scratch/ > [5] http://openjdk.java.net/contribute/ > [6] http://openjdk.java.net/census#members > [7] http://openjdk.java.net/projects/#new-project-vote > > From joe.darcy at oracle.com Thu Jun 5 16:10:14 2014 From: joe.darcy at oracle.com (Joe Darcy) Date: Thu, 05 Jun 2014 09:10:14 -0700 Subject: CFV: New Project: Panama In-Reply-To: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: <53909666.3030407@oracle.com> Vote: yes -Joe On 06/03/2014 10:19 PM, John Rose wrote: > I hereby propose the creation of Project Panama with myself (John > Rose) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project > will provide new connections between the Java virtual > machine and well-defined but "foreign" (non-Java) APIs, > including many interfaces commonly used by C programmers. > The project will provide an venue to incubate early work on > JEP 191[2] and similar enhancements, as discussed on my blog[3]. > > In short, the components developed in this project will support: > > * native code and data access between the JVM and native APIs > * tooling for header file API extraction and API metadata storage > * wrapper interposition for specialized safety invariants and value transformations > * basic bindings for selected native APIs > > The initial source of this project will be based on a clone of a JDK 9 > repository, most specifically the hotspot, langtools, and jdk > sub-repositories. We also plan (with appropriate permissions) to make > use of certain software components mentioned in JEP 191. To host > components which may not immediately fit into the existing repository > structure, there will also be a "scratch" repository modeled on that > of Sumatra[4]. > > The initial Reviewers and Committers will be: > > * David Chase (Reviewer, HotSpot/compiler) > * Mandy Chung (Reviewer, Core Libraries) > * Mike Duigou (Reviewer, Core Libraries) > * Vladimir Ivanov (Reviewer, HotSpot/compiler) > * Henry Jen (Committer, Core Libraries) > * Wayne Meissner (Committer, libffi/JNR) > * Charles Nutter (Reviewer, JRuby/JNR) > * Paul Sandoz (Committer, Core Libraries) > * David Simms (Committer, HotSpot/runtime) > * Attila Szegedi (Reviewer, Language Tools) > * Chris Thalinger (Reviewer, HotSpot/compiler) > * Bob Vandette (Reviewer, HotSpot/embedded) > > (In parentheses are their prospective Panama role and a current > OpenJDK or other affiliation. Reviewer status is assigned based on > previous review history. Note that, per OpenJDK requirements[5], > authoring for this project requires a filed Oracle Contributor > Agreement.) > > The project will maintain at least two mailing lists: > > * panama-dev for developers (as usual) > * panama-spec-experts for specification issues only > > For widest discussion of standardization questions, the specification > mailing list, distinct from the developer list, may include > participants from the Java Community Process who are not OpenJDK > contributors. This list will exclude discussion of implementation > code, and may be moderated or otherwise restricted to meet this goal. > > Change review will be determined by the Lead and a consensus of > Reviewers. Review is expected to be loose initially but made more > strict, perhaps on a per-component basis as components become > candidates for integration into Java SE releases such as JDK 9. > > Votes are due in two weeks, by 12:00 midnight June 18 2014 Pacific US Time > (18-06-2014 07:00 GMT). > > Only current OpenJDK Members [6] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [7]. > > Regards, > > John Rose > > [1] http://openjdk.java.net/projects/#new-project > [2] http://openjdk.java.net/jeps/191 > [3] https://blogs.oracle.com/jrose/entry/the_isthmus_in_the_vm > [4] http://hg.openjdk.java.net/sumatra/sumatra-dev/scratch/ > [5] http://openjdk.java.net/contribute/ > [6] http://openjdk.java.net/census#members > [7] http://openjdk.java.net/projects/#new-project-vote > From john.r.rose at oracle.com Thu Jun 5 16:24:00 2014 From: john.r.rose at oracle.com (John Rose) Date: Thu, 5 Jun 2014 09:24:00 -0700 Subject: CFV: New Project: Panama In-Reply-To: <538F67CE.8080304@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> <538F67CE.8080304@oracle.com> Message-ID: <1B59976A-38BE-4BD9-B947-93A42A7B525B@oracle.com> Good point, Alex. Will do. ? John On Jun 4, 2014, at 11:39 AM, Alex Buckley wrote: > A minor admin point: > > On 6/3/2014 10:19 PM, John Rose wrote: >> The project will maintain at least two mailing lists: >> >> * panama-dev for developers (as usual) >> * panama-spec-experts for specification issues only > > I recommend panama-spec-discuss as the name of the latter. The term 'experts' is suggestive of an Expert Group for a JSR, which the Panama incubator probably wants to hold at arm's length for the time being. The -spec-discuss idiom is seen in enhanced-metadata-spec-discuss and jdbc-spec-discuss at http://mail.openjdk.java.net/mailman/listinfo. > > Alex From per at bothner.com Fri Jun 6 01:08:37 2014 From: per at bothner.com (Per Bothner) Date: Thu, 05 Jun 2014 18:08:37 -0700 Subject: importing old JEPs happening Message-ID: <53911495.9030503@bothner.com> I will shortly start importing the old JEP files into JBS. The initial script-based import (using JIRA's REST API, btw) will not be complete. The full import is a multi-step multi-person operation, including some bulk SQL operations, further REST calls, and some hand-editing. One of these steps will be to convert the security from "confidential" to none. (This step is needed because the default for Oracle-created issues is confidential.) So I apologize, but until we do this step the newly imported issues will only be visible to Oracle employees. A few of you have manually ported JEPs. These will have to be resolved as duplicates. Note also some of you might get some email notifications. Hopefully not too many, or too confusing ... We will send out another email when we're done. At that point you should review your issues, and may need to manually edit what we didn't handle. -- --Per Bothner per at bothner.com http://per.bothner.com/ From iris.clark at oracle.com Tue Jun 10 16:20:20 2014 From: iris.clark at oracle.com (Iris Clark) Date: Tue, 10 Jun 2014 09:20:20 -0700 (PDT) Subject: CFV: New Project: Panama In-Reply-To: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: <66be4f7c-b240-42c5-b6d9-825d43269160@default> Vote: yes iris From John.Coomes at oracle.com Fri Jun 13 01:00:21 2014 From: John.Coomes at oracle.com (John Coomes) Date: Thu, 12 Jun 2014 18:00:21 -0700 Subject: CFV: New Project: Panama In-Reply-To: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: <21402.19749.106560.914852@mykonos.us.oracle.com> Vote: yes -John From jonathan.gibbons at oracle.com Fri Jun 13 01:05:11 2014 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Thu, 12 Jun 2014 18:05:11 -0700 Subject: CFV: New Project: Panama In-Reply-To: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> References: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> Message-ID: <539A4E47.6050400@oracle.com> Vote: yes On 06/03/2014 10:19 PM, John Rose wrote: > I hereby propose the creation of Project Panama with myself (John > Rose) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project > will provide new connections between the Java virtual > machine and well-defined but "foreign" (non-Java) APIs, > including many interfaces commonly used by C programmers. > The project will provide an venue to incubate early work on > JEP 191[2] and similar enhancements, as discussed on my blog[3]. > > In short, the components developed in this project will support: > > * native code and data access between the JVM and native APIs > * tooling for header file API extraction and API metadata storage > * wrapper interposition for specialized safety invariants and value transformations > * basic bindings for selected native APIs > > The initial source of this project will be based on a clone of a JDK 9 > repository, most specifically the hotspot, langtools, and jdk > sub-repositories. We also plan (with appropriate permissions) to make > use of certain software components mentioned in JEP 191. To host > components which may not immediately fit into the existing repository > structure, there will also be a "scratch" repository modeled on that > of Sumatra[4]. > > The initial Reviewers and Committers will be: > > * David Chase (Reviewer, HotSpot/compiler) > * Mandy Chung (Reviewer, Core Libraries) > * Mike Duigou (Reviewer, Core Libraries) > * Vladimir Ivanov (Reviewer, HotSpot/compiler) > * Henry Jen (Committer, Core Libraries) > * Wayne Meissner (Committer, libffi/JNR) > * Charles Nutter (Reviewer, JRuby/JNR) > * Paul Sandoz (Committer, Core Libraries) > * David Simms (Committer, HotSpot/runtime) > * Attila Szegedi (Reviewer, Language Tools) > * Chris Thalinger (Reviewer, HotSpot/compiler) > * Bob Vandette (Reviewer, HotSpot/embedded) > > (In parentheses are their prospective Panama role and a current > OpenJDK or other affiliation. Reviewer status is assigned based on > previous review history. Note that, per OpenJDK requirements[5], > authoring for this project requires a filed Oracle Contributor > Agreement.) > > The project will maintain at least two mailing lists: > > * panama-dev for developers (as usual) > * panama-spec-experts for specification issues only > > For widest discussion of standardization questions, the specification > mailing list, distinct from the developer list, may include > participants from the Java Community Process who are not OpenJDK > contributors. This list will exclude discussion of implementation > code, and may be moderated or otherwise restricted to meet this goal. > > Change review will be determined by the Lead and a consensus of > Reviewers. Review is expected to be loose initially but made more > strict, perhaps on a per-component basis as components become > candidates for integration into Java SE releases such as JDK 9. > > Votes are due in two weeks, by 12:00 midnight June 18 2014 Pacific US Time > (18-06-2014 07:00 GMT). > > Only current OpenJDK Members [6] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [7]. > > Regards, > > John Rose > > [1] http://openjdk.java.net/projects/#new-project > [2] http://openjdk.java.net/jeps/191 > [3] https://blogs.oracle.com/jrose/entry/the_isthmus_in_the_vm > [4] http://hg.openjdk.java.net/sumatra/sumatra-dev/scratch/ > [5] http://openjdk.java.net/contribute/ > [6] http://openjdk.java.net/census#members > [7] http://openjdk.java.net/projects/#new-project-vote > From brian.goetz at oracle.com Sat Jun 21 01:44:18 2014 From: brian.goetz at oracle.com (Brian Goetz) Date: Fri, 20 Jun 2014 21:44:18 -0400 Subject: CFV: Project Valhalla Message-ID: <53A4E372.4070602@oracle.com> I hereby propose the creation of Project Valhalla with myself as the Lead and the HotSpot group as the sponsoring group. In accordance with the OpenJDK guidelines [1], this project will provide a venue to explore and incubate advanced Java VM and Language feature candidates such as Value Types [2], Generic Specialization [3], enhanced volatiles [4] (and possibly other related topics, such as reified generics.) The initial Reviewers and Committers will be: * Brian Goetz * John Rose * Paul Sandoz * Maurizio Cimadamore * Paul Govereau * Dan Smith * David Chase * Mike Duigou * Vladimir Ivanov * Albert Noll The project will host at least the following mailing list: * valhalla-dev for developers and may eventually host specification lists if one or more JSRs is subsequently created. The initial source of this project will be based on a clone of a JDK 9 repository. Changes from the JDK 9 parent will be synced into Valhalla periodically. Similar to Project Lambda, we will follow a "commit first, review later" policy, as code will not flow directly from the Valhalla repositories into the JDK repositories, but instead will be done by a "curated merge" where select changes are extracted into new changesets for incorporation into JDK repositories when they are ready for inclusion. Votes are due by July 7, 2014. Only current OpenJDK Members [5] are eligible to vote on this motion. Votes must be cast in the open on the discuss list. Replying to this message is sufficient if your mail program honors the Reply-To header. For Lazy Consensus voting instructions, see [6]. [1] http://openjdk.java.net/projects/#new-project [2] http://cr.openjdk.java.net/~jrose/values/values-0.html [3] https://bugs.openjdk.java.net/browse/JDK-8046267 [4] http://openjdk.java.net/jeps/193 [5] http://openjdk.java.net/census#members [6] http://openjdk.java.net/projects/#new-project-vote From joe.darcy at oracle.com Sat Jun 21 02:29:24 2014 From: joe.darcy at oracle.com (Joe Darcy) Date: Fri, 20 Jun 2014 19:29:24 -0700 Subject: CFV: Project Valhalla In-Reply-To: <53A4E372.4070602@oracle.com> References: <53A4E372.4070602@oracle.com> Message-ID: <53A4EE04.9010508@oracle.com> Vote: yes -Joe From david.holmes at oracle.com Sat Jun 21 06:10:44 2014 From: david.holmes at oracle.com (David Holmes) Date: Sat, 21 Jun 2014 16:10:44 +1000 Subject: CFV: Project Valhalla In-Reply-To: <53A4E372.4070602@oracle.com> References: <53A4E372.4070602@oracle.com> Message-ID: <53A521E4.1030101@oracle.com> Vote: yes David On 21/06/2014 11:44 AM, Brian Goetz wrote: > I hereby propose the creation of Project Valhalla with myself as the > Lead and the HotSpot group as the sponsoring group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a venue to explore and incubate advanced Java VM and Language feature > candidates such as Value Types [2], Generic Specialization [3], enhanced > volatiles [4] (and possibly other related topics, such as reified > generics.) > > The initial Reviewers and Committers will be: > > * Brian Goetz > * John Rose > * Paul Sandoz > * Maurizio Cimadamore > * Paul Govereau > * Dan Smith > * David Chase > * Mike Duigou > * Vladimir Ivanov > * Albert Noll > > The project will host at least the following mailing list: > > * valhalla-dev for developers > > and may eventually host specification lists if one or more JSRs is > subsequently created. > > The initial source of this project will be based on a clone of a JDK 9 > repository. Changes from the JDK 9 parent will be synced into Valhalla > periodically. Similar to Project Lambda, we will follow a "commit > first, review later" policy, as code will not flow directly from the > Valhalla repositories into the JDK repositories, but instead will be > done by a "curated merge" where select changes are extracted into new > changesets for incorporation into JDK repositories when they are ready > for inclusion. > > Votes are due by July 7, 2014. > > Only current OpenJDK Members [5] are eligible to vote on this > motion. Votes must be cast in the open on the discuss list. > Replying to this message is sufficient if your mail program > honors the Reply-To header. > > For Lazy Consensus voting instructions, see [6]. > > > [1] http://openjdk.java.net/projects/#new-project > [2] http://cr.openjdk.java.net/~jrose/values/values-0.html > [3] https://bugs.openjdk.java.net/browse/JDK-8046267 > [4] http://openjdk.java.net/jeps/193 > [5] http://openjdk.java.net/census#members > [6] http://openjdk.java.net/projects/#new-project-vote From chris.hegarty at oracle.com Sat Jun 21 08:11:45 2014 From: chris.hegarty at oracle.com (Chris Hegarty) Date: Sat, 21 Jun 2014 09:11:45 +0100 Subject: CFV: Project Valhalla In-Reply-To: <53A4E372.4070602@oracle.com> References: <53A4E372.4070602@oracle.com> Message-ID: <5E9E29A5-1FEE-4367-9905-88F1C83CBD68@oracle.com> Vote: YES -Chris > On 21 Jun 2014, at 02:44, Brian Goetz wrote: > > I hereby propose the creation of Project Valhalla with myself as the Lead and the HotSpot group as the sponsoring group. > > In accordance with the OpenJDK guidelines [1], this project will provide a venue to explore and incubate advanced Java VM and Language feature candidates such as Value Types [2], Generic Specialization [3], enhanced volatiles [4] (and possibly other related topics, such as reified generics.) > > The initial Reviewers and Committers will be: > > * Brian Goetz > * John Rose > * Paul Sandoz > * Maurizio Cimadamore > * Paul Govereau > * Dan Smith > * David Chase > * Mike Duigou > * Vladimir Ivanov > * Albert Noll > > The project will host at least the following mailing list: > > * valhalla-dev for developers > > and may eventually host specification lists if one or more JSRs is subsequently created. > > The initial source of this project will be based on a clone of a JDK 9 > repository. Changes from the JDK 9 parent will be synced into Valhalla periodically. Similar to Project Lambda, we will follow a "commit first, review later" policy, as code will not flow directly from the Valhalla repositories into the JDK repositories, but instead will be done by a "curated merge" where select changes are extracted into new changesets for incorporation into JDK repositories when they are ready for inclusion. > > Votes are due by July 7, 2014. > > Only current OpenJDK Members [5] are eligible to vote on this > motion. Votes must be cast in the open on the discuss list. > Replying to this message is sufficient if your mail program > honors the Reply-To header. > > For Lazy Consensus voting instructions, see [6]. > > > [1] http://openjdk.java.net/projects/#new-project > [2] http://cr.openjdk.java.net/~jrose/values/values-0.html > [3] https://bugs.openjdk.java.net/browse/JDK-8046267 > [4] http://openjdk.java.net/jeps/193 > [5] http://openjdk.java.net/census#members > [6] http://openjdk.java.net/projects/#new-project-vote From Paul.Sandoz at oracle.com Sat Jun 21 12:21:15 2014 From: Paul.Sandoz at oracle.com (Paul Sandoz) Date: Sat, 21 Jun 2014 14:21:15 +0200 Subject: CFV: Project Valhalla In-Reply-To: <53A4E372.4070602@oracle.com> References: <53A4E372.4070602@oracle.com> Message-ID: <214F91EA-BC8A-4600-AF44-3BE31F3D5A84@oracle.com> Vote: yes. Paul. From john.r.rose at oracle.com Sat Jun 21 18:21:41 2014 From: john.r.rose at oracle.com (John Rose) Date: Sun, 22 Jun 2014 01:21:41 +0700 Subject: CFV: Project Valhalla In-Reply-To: <53A4E372.4070602@oracle.com> References: <53A4E372.4070602@oracle.com> Message-ID: <9591CD22-D7E4-466C-9687-71B6BF768912@oracle.com> Vote: yes P.S. I'm voting for a powerful edifice to be known as valor-halla, a sort of fortress, not hval-falla, which would be the fail-whale. On Jun 21, 2014, at 8:44 AM, Brian Goetz wrote: > I hereby propose the creation of Project Valhalla with myself as the Lead and the HotSpot group as the sponsoring group. From maurizio.cimadamore at oracle.com Sat Jun 21 21:24:01 2014 From: maurizio.cimadamore at oracle.com (Maurizio Cimadamore) Date: Sat, 21 Jun 2014 22:24:01 +0100 Subject: CFV: Project Valhalla In-Reply-To: <53A4E372.4070602@oracle.com> References: <53A4E372.4070602@oracle.com> Message-ID: <53A5F7F1.1040507@oracle.com> Vote: yes Maurizio On 21/06/14 02:44, Brian Goetz wrote: > I hereby propose the creation of Project Valhalla with myself as the > Lead and the HotSpot group as the sponsoring group. > > In accordance with the OpenJDK guidelines [1], this project will > provide a venue to explore and incubate advanced Java VM and Language > feature candidates such as Value Types [2], Generic Specialization > [3], enhanced volatiles [4] (and possibly other related topics, such > as reified generics.) > > The initial Reviewers and Committers will be: > > * Brian Goetz > * John Rose > * Paul Sandoz > * Maurizio Cimadamore > * Paul Govereau > * Dan Smith > * David Chase > * Mike Duigou > * Vladimir Ivanov > * Albert Noll > > The project will host at least the following mailing list: > > * valhalla-dev for developers > > and may eventually host specification lists if one or more JSRs is > subsequently created. > > The initial source of this project will be based on a clone of a JDK 9 > repository. Changes from the JDK 9 parent will be synced into > Valhalla periodically. Similar to Project Lambda, we will follow a > "commit first, review later" policy, as code will not flow directly > from the Valhalla repositories into the JDK repositories, but instead > will be done by a "curated merge" where select changes are extracted > into new changesets for incorporation into JDK repositories when they > are ready for inclusion. > > Votes are due by July 7, 2014. > > Only current OpenJDK Members [5] are eligible to vote on this > motion. Votes must be cast in the open on the discuss list. > Replying to this message is sufficient if your mail program > honors the Reply-To header. > > For Lazy Consensus voting instructions, see [6]. > > > [1] http://openjdk.java.net/projects/#new-project > [2] http://cr.openjdk.java.net/~jrose/values/values-0.html > [3] https://bugs.openjdk.java.net/browse/JDK-8046267 > [4] http://openjdk.java.net/jeps/193 > [5] http://openjdk.java.net/census#members > [6] http://openjdk.java.net/projects/#new-project-vote From laurent.daynes at oracle.com Sun Jun 22 08:51:20 2014 From: laurent.daynes at oracle.com (Laurent Daynes) Date: Sun, 22 Jun 2014 10:51:20 +0200 Subject: CFV: Project Valhalla In-Reply-To: <53A4EE04.9010508@oracle.com> References: <53A4E372.4070602@oracle.com> <53A4EE04.9010508@oracle.com> Message-ID: <53A69908.5040902@oracle.com> Vote: yes -- Laurent Daynes Oracle Labs From sproket at videotron.ca Mon Jun 23 00:56:16 2014 From: sproket at videotron.ca (Dan Howard) Date: Sun, 22 Jun 2014 20:56:16 -0400 Subject: CFV: Project Valhalla In-Reply-To: <53A4E372.4070602@oracle.com> References: <53A4E372.4070602@oracle.com> Message-ID: <53A77B30.40304@videotron.ca> Vote: yes --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com From jaroslav.bachorik at oracle.com Mon Jun 23 07:39:59 2014 From: jaroslav.bachorik at oracle.com (Jaroslav Bachorik) Date: Mon, 23 Jun 2014 09:39:59 +0200 Subject: CFV: Project Valhalla In-Reply-To: <53A4E372.4070602@oracle.com> References: <53A4E372.4070602@oracle.com> Message-ID: <53A7D9CF.4060003@oracle.com> Vote: yes -JB- On 06/21/2014 03:44 AM, Brian Goetz wrote: > I hereby propose the creation of Project Valhalla with myself as the > Lead and the HotSpot group as the sponsoring group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a venue to explore and incubate advanced Java VM and Language feature > candidates such as Value Types [2], Generic Specialization [3], enhanced > volatiles [4] (and possibly other related topics, such as reified > generics.) > > The initial Reviewers and Committers will be: > > * Brian Goetz > * John Rose > * Paul Sandoz > * Maurizio Cimadamore > * Paul Govereau > * Dan Smith > * David Chase > * Mike Duigou > * Vladimir Ivanov > * Albert Noll > > The project will host at least the following mailing list: > > * valhalla-dev for developers > > and may eventually host specification lists if one or more JSRs is > subsequently created. > > The initial source of this project will be based on a clone of a JDK 9 > repository. Changes from the JDK 9 parent will be synced into Valhalla > periodically. Similar to Project Lambda, we will follow a "commit > first, review later" policy, as code will not flow directly from the > Valhalla repositories into the JDK repositories, but instead will be > done by a "curated merge" where select changes are extracted into new > changesets for incorporation into JDK repositories when they are ready > for inclusion. > > Votes are due by July 7, 2014. > > Only current OpenJDK Members [5] are eligible to vote on this > motion. Votes must be cast in the open on the discuss list. > Replying to this message is sufficient if your mail program > honors the Reply-To header. > > For Lazy Consensus voting instructions, see [6]. > > > [1] http://openjdk.java.net/projects/#new-project > [2] http://cr.openjdk.java.net/~jrose/values/values-0.html > [3] https://bugs.openjdk.java.net/browse/JDK-8046267 > [4] http://openjdk.java.net/jeps/193 > [5] http://openjdk.java.net/census#members > [6] http://openjdk.java.net/projects/#new-project-vote From volker.simonis at gmail.com Mon Jun 23 12:18:21 2014 From: volker.simonis at gmail.com (Volker Simonis) Date: Mon, 23 Jun 2014 14:18:21 +0200 Subject: CFV: Project Valhalla In-Reply-To: <53A4E372.4070602@oracle.com> References: <53A4E372.4070602@oracle.com> Message-ID: Vote: yes On Sat, Jun 21, 2014 at 3:44 AM, Brian Goetz wrote: > I hereby propose the creation of Project Valhalla with myself as the Lead > and the HotSpot group as the sponsoring group. > > In accordance with the OpenJDK guidelines [1], this project will provide a > venue to explore and incubate advanced Java VM and Language feature > candidates such as Value Types [2], Generic Specialization [3], enhanced > volatiles [4] (and possibly other related topics, such as reified generics.) > > The initial Reviewers and Committers will be: > > * Brian Goetz > * John Rose > * Paul Sandoz > * Maurizio Cimadamore > * Paul Govereau > * Dan Smith > * David Chase > * Mike Duigou > * Vladimir Ivanov > * Albert Noll > > The project will host at least the following mailing list: > > * valhalla-dev for developers > > and may eventually host specification lists if one or more JSRs is > subsequently created. > > The initial source of this project will be based on a clone of a JDK 9 > repository. Changes from the JDK 9 parent will be synced into Valhalla > periodically. Similar to Project Lambda, we will follow a "commit first, > review later" policy, as code will not flow directly from the Valhalla > repositories into the JDK repositories, but instead will be done by a > "curated merge" where select changes are extracted into new changesets for > incorporation into JDK repositories when they are ready for inclusion. > > Votes are due by July 7, 2014. > > Only current OpenJDK Members [5] are eligible to vote on this > motion. Votes must be cast in the open on the discuss list. > Replying to this message is sufficient if your mail program > honors the Reply-To header. > > For Lazy Consensus voting instructions, see [6]. > > > [1] http://openjdk.java.net/projects/#new-project > [2] http://cr.openjdk.java.net/~jrose/values/values-0.html > [3] https://bugs.openjdk.java.net/browse/JDK-8046267 > [4] http://openjdk.java.net/jeps/193 > [5] http://openjdk.java.net/census#members > [6] http://openjdk.java.net/projects/#new-project-vote From neugens at redhat.com Mon Jun 23 12:36:31 2014 From: neugens at redhat.com (Mario Torre) Date: Mon, 23 Jun 2014 14:36:31 +0200 Subject: CFV: Project Valhalla In-Reply-To: <53A4E372.4070602@oracle.com> References: <53A4E372.4070602@oracle.com> Message-ID: <1403526991.4265.4.camel@nirvana.localdomain> Vote: Yes, Cheers, Mario On Fri, 2014-06-20 at 21:44 -0400, Brian Goetz wrote: > I hereby propose the creation of Project Valhalla with myself as the > Lead and the HotSpot group as the sponsoring group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a venue to explore and incubate advanced Java VM and Language feature > candidates such as Value Types [2], Generic Specialization [3], enhanced > volatiles [4] (and possibly other related topics, such as reified generics.) > > The initial Reviewers and Committers will be: > > * Brian Goetz > * John Rose > * Paul Sandoz > * Maurizio Cimadamore > * Paul Govereau > * Dan Smith > * David Chase > * Mike Duigou > * Vladimir Ivanov > * Albert Noll > > The project will host at least the following mailing list: > > * valhalla-dev for developers > > and may eventually host specification lists if one or more JSRs is > subsequently created. > > The initial source of this project will be based on a clone of a JDK 9 > repository. Changes from the JDK 9 parent will be synced into Valhalla > periodically. Similar to Project Lambda, we will follow a "commit > first, review later" policy, as code will not flow directly from the > Valhalla repositories into the JDK repositories, but instead will be > done by a "curated merge" where select changes are extracted into new > changesets for incorporation into JDK repositories when they are ready > for inclusion. > > Votes are due by July 7, 2014. > > Only current OpenJDK Members [5] are eligible to vote on this > motion. Votes must be cast in the open on the discuss list. > Replying to this message is sufficient if your mail program > honors the Reply-To header. > > For Lazy Consensus voting instructions, see [6]. > > > [1] http://openjdk.java.net/projects/#new-project > [2] http://cr.openjdk.java.net/~jrose/values/values-0.html > [3] https://bugs.openjdk.java.net/browse/JDK-8046267 > [4] http://openjdk.java.net/jeps/193 > [5] http://openjdk.java.net/census#members > [6] http://openjdk.java.net/projects/#new-project-vote From pbenedict at apache.org Mon Jun 23 13:47:15 2014 From: pbenedict at apache.org (Paul Benedict) Date: Mon, 23 Jun 2014 08:47:15 -0500 Subject: importing old JEPs happening Message-ID: Hopefully the JEP listing [1] links can be changed to point to the individual JIRA tickets? I presume that each will be more up-to-date than these markdown files. [1] http://openjdk.java.net/jeps/0 Cheers, Paul From jon.masamitsu at oracle.com Mon Jun 23 14:56:24 2014 From: jon.masamitsu at oracle.com (Jon Masamitsu) Date: Mon, 23 Jun 2014 07:56:24 -0700 Subject: CFV: Project Valhalla In-Reply-To: <53A4E372.4070602@oracle.com> References: <53A4E372.4070602@oracle.com> Message-ID: <53A84018.8030509@oracle.com> Vote: yes On 06/20/2014 06:44 PM, Brian Goetz wrote: > I hereby propose the creation of Project Valhalla with myself as the > Lead and the HotSpot group as the sponsoring group. > > In accordance with the OpenJDK guidelines [1], this project will > provide a venue to explore and incubate advanced Java VM and Language > feature candidates such as Value Types [2], Generic Specialization > [3], enhanced volatiles [4] (and possibly other related topics, such > as reified generics.) > > The initial Reviewers and Committers will be: > > * Brian Goetz > * John Rose > * Paul Sandoz > * Maurizio Cimadamore > * Paul Govereau > * Dan Smith > * David Chase > * Mike Duigou > * Vladimir Ivanov > * Albert Noll > > The project will host at least the following mailing list: > > * valhalla-dev for developers > > and may eventually host specification lists if one or more JSRs is > subsequently created. > > The initial source of this project will be based on a clone of a JDK 9 > repository. Changes from the JDK 9 parent will be synced into > Valhalla periodically. Similar to Project Lambda, we will follow a > "commit first, review later" policy, as code will not flow directly > from the Valhalla repositories into the JDK repositories, but instead > will be done by a "curated merge" where select changes are extracted > into new changesets for incorporation into JDK repositories when they > are ready for inclusion. > > Votes are due by July 7, 2014. > > Only current OpenJDK Members [5] are eligible to vote on this > motion. Votes must be cast in the open on the discuss list. > Replying to this message is sufficient if your mail program > honors the Reply-To header. > > For Lazy Consensus voting instructions, see [6]. > > > [1] http://openjdk.java.net/projects/#new-project > [2] http://cr.openjdk.java.net/~jrose/values/values-0.html > [3] https://bugs.openjdk.java.net/browse/JDK-8046267 > [4] http://openjdk.java.net/jeps/193 > [5] http://openjdk.java.net/census#members > [6] http://openjdk.java.net/projects/#new-project-vote From mark.reinhold at oracle.com Mon Jun 23 15:15:54 2014 From: mark.reinhold at oracle.com (mark.reinhold at oracle.com) Date: Mon, 23 Jun 2014 08:15:54 -0700 Subject: importing old JEPs happening In-Reply-To: References: Message-ID: <20140623081554.725298@eggemoggin.niobe.net> 2014/6/22 23:47 -0700, pbenedict at apache.org: > Hopefully the JEP listing [1] links can be changed to point to the > individual JIRA tickets? Yes, that will be done soon. - Mark From pdoubleya at gmail.com Mon Jun 23 15:19:23 2014 From: pdoubleya at gmail.com (Patrick Wright) Date: Mon, 23 Jun 2014 17:19:23 +0200 Subject: CFV: Project Valhalla In-Reply-To: <53A6F0C4.8020907@oracle.com> References: <53A6F0C4.8020907@oracle.com> Message-ID: Hi Brian, One quick question - how is this/will this be different from the Da Vinci Project/MLVM? Do you expect Da Vinci to continue once Valhalla kicks off? Thanks, Patrick On Sun, Jun 22, 2014 at 5:05 PM, Brian Goetz wrote: > I hereby propose the creation of Project Valhalla with myself as the Lead > and the HotSpot group as the sponsoring group. > From Alan.Bateman at oracle.com Mon Jun 23 16:13:57 2014 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Mon, 23 Jun 2014 17:13:57 +0100 Subject: CFV: Project Valhalla In-Reply-To: <53A4E372.4070602@oracle.com> References: <53A4E372.4070602@oracle.com> Message-ID: <53A85245.60400@oracle.com> On 21/06/2014 02:44, Brian Goetz wrote: > I hereby propose the creation of Project Valhalla with myself as the > Lead and the HotSpot group as the sponsoring group. Vote: yes From brent.christian at oracle.com Mon Jun 23 16:53:57 2014 From: brent.christian at oracle.com (Brent Christian) Date: Mon, 23 Jun 2014 09:53:57 -0700 Subject: CFV: Project Valhalla In-Reply-To: <53A4E372.4070602@oracle.com> References: <53A4E372.4070602@oracle.com> Message-ID: <53A85BA5.2020705@oracle.com> Vote: Yes On 6/20/14 6:44 PM, Brian Goetz wrote: > I hereby propose the creation of Project Valhalla with myself as the > Lead and the HotSpot group as the sponsoring group. From john.r.rose at oracle.com Mon Jun 23 17:24:55 2014 From: john.r.rose at oracle.com (John Rose) Date: Mon, 23 Jun 2014 12:24:55 -0500 Subject: CFV: Project Valhalla In-Reply-To: References: <53A6F0C4.8020907@oracle.com> Message-ID: On Jun 23, 2014, at 10:19 AM, Patrick Wright wrote: > Hi Brian, > > One quick question - how is this/will this be different from the Da Vinci > Project/MLVM? Do you expect Da Vinci to continue once Valhalla kicks off? Good question. The charter for Da Vinci is to incubate JVM features for languages other than Java (tail call), or for general language support without associated Java language changes (invokedynamic). It envisions value types, but those are now properly part of Valhalla. Valhalla is intended to support the evolution of Java itself. ? John > Thanks, > Patrick > > > On Sun, Jun 22, 2014 at 5:05 PM, Brian Goetz wrote: > >> I hereby propose the creation of Project Valhalla with myself as the Lead >> and the HotSpot group as the sponsoring group. >> From roger.riggs at oracle.com Mon Jun 23 17:27:24 2014 From: roger.riggs at oracle.com (roger riggs) Date: Mon, 23 Jun 2014 13:27:24 -0400 Subject: CFV: Project Valhalla In-Reply-To: <53A4E372.4070602@oracle.com> References: <53A4E372.4070602@oracle.com> Message-ID: <53A8637C.7020105@oracle.com> Vote: Yes On 6/20/2014 9:44 PM, Brian Goetz wrote: > I hereby propose the creation of Project Valhalla with myself as the > Lead and the HotSpot group as the sponsoring group. From omajid at redhat.com Mon Jun 23 18:53:47 2014 From: omajid at redhat.com (Omair Majid) Date: Mon, 23 Jun 2014 14:53:47 -0400 Subject: CFV: Project Valhalla In-Reply-To: <53A6F0C4.8020907@oracle.com> References: <53A6F0C4.8020907@oracle.com> Message-ID: <20140623185346.GH2372@redhat.com> Vote: Yes From huizhe.wang at oracle.com Mon Jun 23 19:05:51 2014 From: huizhe.wang at oracle.com (huizhe wang) Date: Mon, 23 Jun 2014 12:05:51 -0700 Subject: JDK9 project: XML/JAXP Approachability / Ease of Use Message-ID: <53A87A8F.4030401@oracle.com> Hi, We're planning on a jaxp project to address usability issues in the JAXP API. One of the complaints about the JAXP API is the number of lines of code that are needed to implement a simple task. Tasks that should take one or two lines often take ten or twelve lines instead. Consider the following example: File file = new File(FILEPATH + "results.xml"); DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance(); factory.setNamespaceAware(true); XPathFactory xf = XPathFactory.newInstance(); XPath xp = xf.newXPath(); xp.setNamespaceContext(new NamespaceContext() { @Override public String getNamespaceURI(String prefix) { return "http://example.com/users/"; } @Override public String getPrefix(String namespaceURI) { return "ns1"; } @Override public Iterator getPrefixes(String namespaceURI) { ArrayList list = new ArrayList(); list.add("ns1"); return list.iterator(); } }); try { DocumentBuilder builder = factory.newDocumentBuilder(); Document document = builder.parse(file); String s = (String) xp.evaluate( "/ns1:Results/ns1:Row[ns1:USERID=2]/ns1:NAME[text()]", document, XPathConstants.STRING); System.out.println("Company: " + s); } catch (ParserConfigurationException e) { //creating DocumentBuilder } catch (SAXException ex) { //parsing } catch (IOException ex) { //parsing } catch (XPathExpressionException ex) { //xpath evaluation } The issues reflected in the above sample include: *1. Too many abstractions* As shown in the above sample, there are multiple layers of abstraction in the DOM and Xpath API: factory, builder, and document, XPathFactory and XPath. *2. Unnecessary Pluggability* The pluggability layer allows easily plugging in third party implementations. However, in many use cases where pluggability is not needed, it becomes the performance bottleneck for the applications. *3. Too many unrelated checked exceptions* There are four unrelated checked exceptions in the above example. None of them is recoverable. ParserConfigurationException actually reflects a design flaw in the DocumentBuilderFactory that allowed setting both a Schema and Schema Language. In practice, Exception is often used to avoid having to catch each of the checked exceptions. *4. Lack of integration* JAXP is an umbrella of several libraries. The sample code above demonstrated the lack of integration among them. First of all, A DOM Document and XPath have to be created separately. Secondly, as in the above case, the Document may be either namespace-aware or unaware, depending on the setting on the DOM Factory, which is unknown to XPath created later. This project may have two aspects: one to provide APIs to get straight to the objects such as DOM Document, and another to provide convenient methods for some common use cases. (*Note that, there is no intention to replace the existing API nor duplicate all of the features.) For the example above, it could potentially be done in a couple of lines (this is just an illustration on how existing APIs could be simplified and may not reflect what the API would look like): String company = XMLDocument.fromFile(FILEPATH + "results.xml") .evalXPath("/Results/Row[USERID=2]/NAME[text()]"); System.out.printf("Company: %s%n", company); We would love to hear from you. Any thoughts, concerns, experiences/complaints would be very welcome. Thanks, Joe From brian.goetz at oracle.com Tue Jun 24 00:48:22 2014 From: brian.goetz at oracle.com (Brian Goetz) Date: Mon, 23 Jun 2014 20:48:22 -0400 Subject: Result: New Project: Panama In-Reply-To: <63A0CDCE-EE00-40EE-B2A1-66C1D7F963FF@oracle.com> References: <63A0CDCE-EE00-40EE-B2A1-66C1D7F963FF@oracle.com> Message-ID: <53A8CAD6.2030001@oracle.com> http://www.youtube.com/watch?v=w-NshzYK9y0 On 6/23/2014 4:23 PM, John Rose wrote: > Voting for Project Panama [1] is now closed. > > Yes: 19 > Veto: 0 > Abstain: 0 > > According to the Bylaws definition of Lazy Consensus [2], this is sufficient to approve the creation of this project. > > ? John > > P.S. This is a resend with corrected subject line. > > [1] http://mail.openjdk.java.net/pipermail/announce/2014-June/000172.html > [2] http://openjdk.java.net/bylaws#lazy-consensus > From mandy.chung at oracle.com Tue Jun 24 21:12:09 2014 From: mandy.chung at oracle.com (Mandy Chung) Date: Tue, 24 Jun 2014 14:12:09 -0700 Subject: CFV: Project Valhalla In-Reply-To: <53A6F0C4.8020907@oracle.com> References: <53A6F0C4.8020907@oracle.com> Message-ID: <53A9E9A9.8020100@oracle.com> Vote: yes Mandy From dalibor.topic at oracle.com Tue Jun 24 21:25:12 2014 From: dalibor.topic at oracle.com (dalibor topic) Date: Tue, 24 Jun 2014 23:25:12 +0200 Subject: CFV: Project Valhalla In-Reply-To: <53A6F0C4.8020907@oracle.com> References: <53A6F0C4.8020907@oracle.com> Message-ID: <53A9ECB8.404@oracle.com> Vote: Yes. -- Dalibor Topic | Principal Product Manager Phone: +494089091214 | Mobile: +491737185961 ORACLE Deutschland B.V. & Co. KG | K?hneh?fe 5 | 22761 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 Oracle is committed to developing practices and products that help protect the environment From lukas.eder at datageekery.com Wed Jun 25 07:18:25 2014 From: lukas.eder at datageekery.com (Lukas Eder) Date: Wed, 25 Jun 2014 07:18:25 +0000 Subject: JDK9 project: XML/JAXP Approachability / Ease of Use Message-ID: Hello, At Data Geekery GmbH, we've been trying to tackle the problems you're outlining with our jQuery port "jOOX" - https://code.google.com/p/joox/ - https://github.com/jOOQ/jOOX Unfortunately, we hadn't pushed this very much so far, which is why the API is not very well documented. The idea is that jQuery is a great way to manipulate the HTML DOM, so we thought why don't we create a similar API for the XML DOM. Our main focus was to: - Stick with the standards, i.e. not to create any "improved" DOM API like other libraries - Integrate with XSLT, XPath, JAXB - Implement all the functional aspects of jQuery This allows for using jOOX just as a thin wrapper around all the existing, rock-solid libraries. So, the suggestion you've made in your previous E-Mail: String company = XMLDocument.fromFile(FILEPATH + "results.xml") .evalXPath("/Results/Row[USERID=2]/NAME[text()]"); System.out.printf("Company: %s%n", company); Would translate to this jOOX statement: String company = $("results.xml") .xpath("/Results/Row[USERID=2]/NAME[text()]") .text(); In our opinion, the strengths of jOOX appear specifically compelling when working with Java 8, as we've outlined in this blog post: http://blog.jooq.org/2014/01/17/java-8-friday-goodies-lambdas-and-xml/ Some code examples: // Example 1 $(new File("./pom.xml")).find("groupId") .each(ctx -> { System.out.println( $(ctx).text() + ":" + $(ctx).siblings("artifactId").text() + ":" + $(ctx).siblings("version").text() ); }); // Example 2 $(new File("./pom.xml")) .find("groupId") .filter(ctx -> $(ctx).siblings("version") .matchText(".*-SNAPSHOT") .isEmpty()) .each(ctx -> { System.out.println( $(ctx).text() + ":" + $(ctx).siblings("artifactId").text() + ":" + $(ctx).siblings("version").text()); }); // Example 3 $(new File("./pom.xml")) .find("groupId") .filter(ctx -> $(ctx).siblings("version") .matchText(".*-SNAPSHOT") .isEmpty()) .content(ctx -> $(ctx).text() + ":" + $(ctx).siblings("artifactId").text() + ":" + $(ctx).siblings("version").text() ) .rename("artifact") .each(ctx -> System.out.println(ctx)); If this is interesting for the JAXP maintainers, I'll be happy to provide more information. Best Regards, Lukas -- Lukas Eder - Head of R&D | lukas.eder at datageekery.com | +41 44 586 82 56 Data Geekery GmbH | Binzstrasse 23 | CH-8045 Z?rich | Switzerland http://www.datageekery.com | Get back in control of your SQLT From ahmetaa at gmail.com Wed Jun 25 11:15:09 2014 From: ahmetaa at gmail.com (Ahmet A. Akin) Date: Wed, 25 Jun 2014 14:15:09 +0300 Subject: Speed difference between EA versions and official distributions. Message-ID: Hello, I hope this is the correct place to ask. Recently I tested our Java speech recognition engine speed with several Java versions. Two JDK 8 EA builds ( 1.8.0-ea-b109 and 1.8.0_20-ea-b19 ) One Stable Oracle JDK 8 release: ( 1.8.0_05-b13 ) One Stable Open JDK 7 release: ( IcedTea 7u55-2.4.7 ) And I observed that both Java-8 EA versions runs %6-8 faster than the stable Oracle JDK 8 and Open JDK 7 releases. What can be the reason? Do EA builds and Oracle official releases use different compilers? Or is there something else I should be checking? What do you suggest? Environment: Ubuntu 12.04 64-bit, Intel i7-3770 3.4Ghz x 8 Best, Ahmet From david.holmes at oracle.com Wed Jun 25 11:40:19 2014 From: david.holmes at oracle.com (David Holmes) Date: Wed, 25 Jun 2014 21:40:19 +1000 Subject: Speed difference between EA versions and official distributions. In-Reply-To: References: Message-ID: <53AAB523.8080709@oracle.com> Hi Ahmet, On 25/06/2014 9:15 PM, Ahmet A. Akin wrote: > Hello, > > I hope this is the correct place to ask. No, the discuss list is for "General discussion about the OpenJDK Community": http://mail.openjdk.java.net/mailman/listinfo I've cc'd the hotspot-dev list as a better starting point, and the discuss list should be dropped from replies. > Recently I tested our Java speech > recognition engine speed with several Java versions. > > Two JDK 8 EA builds ( 1.8.0-ea-b109 and 1.8.0_20-ea-b19 ) > One Stable Oracle JDK 8 release: ( 1.8.0_05-b13 ) > One Stable Open JDK 7 release: ( IcedTea 7u55-2.4.7 ) > > And I observed that both Java-8 EA versions runs %6-8 faster than the > stable Oracle JDK 8 and Open JDK 7 releases. What can be the reason? Do EA > builds and Oracle official releases use different compilers? Or is there > something else I should be checking? What do you suggest? There can be a lot of factors involved but EA releases are not deliberately different other than they are, by their nature, not as complete as the GA release will be. The compiler might be different if a compiler update is planned for a release and you happen to have taken an EA build from before the change. Sometimes problems are discovered with code that requires a fix that lowers performance prior to GA. Developers then look for ways to get the performance back while maintaining correctness. So, as a purely hypothetical example, 8-b109 may have had a fast but incorrect piece of code, 8-b132 (the GA build) may have had a correct but slower version of the code, and then for 8u20 a new fix was found that improved the performance. An EA build may have a partially implemented feature, and once the feature is complete, the performance has changed. To know exactly what the differences are would require a lot of detailed benchmarking of each build to create a performance profile for the release and then try to see what changes may have contributed to the performance deltas. Cheers, David > Environment: Ubuntu 12.04 64-bit, Intel i7-3770 3.4Ghz x 8 > > Best, > > Ahmet > From omajid at redhat.com Thu Jun 26 14:56:57 2014 From: omajid at redhat.com (Omair Majid) Date: Thu, 26 Jun 2014 10:56:57 -0400 Subject: A pkg-config file for OpenJDK Message-ID: <20140626145657.GA2761@redhat.com> Hi, Over in Fedora, we have received requests from developers asking that compiling JNI programs and liking against the JVM be made easier [0] [1]. Some of the current difficulties include that the VM type (server, client) is not known by other programs and so they have to fall back to guessing where the libjvm.so that they should link against is. One standard approach on Linux for making linking against programs easier is to use pkg-config [1] files. A pkg-config file essentially describes the CFLAGS and LDFLAGS that need to be passed to the compiler and the linker to compile and link a program successfully, without knowing anything other than the name of the program or library to compile/link against. On Fedora/x86_64, such a file might look like (for OpenJDK 8): > jdk=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.5.x86_64 > jre=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.5.x86_64/jre > lib_arch=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.5.x86_64/jre/lib/amd64 > Name: java-1.8.0-openjdk > Description: OpenJDK 8 > Version: 1.8.0.5 > Cflags: -I${jdk}/include -I${jdk}/include/linux > Libs: -L${lib_arch} -L${lib_arch}/server -ljvm -ljava Rather than doing something Fedora-specific, I would like to propose carrying a template of this file upstream as part of the OpenJDK project. Then, each distribution could modify it and change only the bits that are specific to that distribution, and clients can rely on having common or well-known names for everything else. One nice-to-have feature would be keep this file somewhat generic, so other JPackage-style non-OpenJDK JDKs could adapt it too. That's why I have used `java-1.8.0-openjdk` as the name above, but I am open to changing it to whatever the consensus is. Does anyone else have any thoughts or comments about this? Thanks, Omair [0] https://bugzilla.redhat.com/show_bug.cgi?id=449456 [1] https://bugzilla.redhat.com/show_bug.cgi?id=740762 [2] http://people.freedesktop.org/~dbn/pkg-config-guide.html -- PGP Key: 66484681 (http://pgp.mit.edu/) Fingerprint = F072 555B 0A17 3957 4E95 0056 F286 F14F 6648 4681 From martijnverburg at gmail.com Thu Jun 26 15:16:38 2014 From: martijnverburg at gmail.com (Martijn Verburg) Date: Thu, 26 Jun 2014 16:16:38 +0100 Subject: A pkg-config file for OpenJDK In-Reply-To: <20140626145657.GA2761@redhat.com> References: <20140626145657.GA2761@redhat.com> Message-ID: Hi Omair, Looks like a good idea to me, we've had a number of issues with this in practice (we have a desktop tool on Linux) - could probably be backported to 7u as well...? Cheers, Martijn On 26 June 2014 15:56, Omair Majid wrote: > Hi, > > Over in Fedora, we have received requests from developers asking that > compiling JNI programs and liking against the JVM be made easier [0] > [1]. Some of the current difficulties include that the VM type (server, > client) is not known by other programs and so they have to fall back to > guessing where the libjvm.so that they should link against is. > > One standard approach on Linux for making linking against programs > easier is to use pkg-config [1] files. > > A pkg-config file essentially describes the CFLAGS and LDFLAGS that need > to be passed to the compiler and the linker to compile and link a > program successfully, without knowing anything other than the name of > the program or library to compile/link against. > > On Fedora/x86_64, such a file might look like (for OpenJDK 8): > > > jdk=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.5.x86_64 > > jre=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.5.x86_64/jre > > lib_arch=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.5.x86_64/jre/lib/amd64 > > > Name: java-1.8.0-openjdk > > Description: OpenJDK 8 > > Version: 1.8.0.5 > > Cflags: -I${jdk}/include -I${jdk}/include/linux > > Libs: -L${lib_arch} -L${lib_arch}/server -ljvm -ljava > > Rather than doing something Fedora-specific, I would like to propose > carrying a template of this file upstream as part of the OpenJDK > project. Then, each distribution could modify it and change only the > bits that are specific to that distribution, and clients can rely on > having common or well-known names for everything else. > > One nice-to-have feature would be keep this file somewhat generic, so > other JPackage-style non-OpenJDK JDKs could adapt it too. That's why I > have used `java-1.8.0-openjdk` as the name above, but I am open to > changing it to whatever the consensus is. > > Does anyone else have any thoughts or comments about this? > > Thanks, > Omair > > [0] https://bugzilla.redhat.com/show_bug.cgi?id=449456 > [1] https://bugzilla.redhat.com/show_bug.cgi?id=740762 > [2] http://people.freedesktop.org/~dbn/pkg-config-guide.html > > -- > PGP Key: 66484681 (http://pgp.mit.edu/) > Fingerprint = F072 555B 0A17 3957 4E95 0056 F286 F14F 6648 4681 > From neugens at redhat.com Thu Jun 26 16:04:20 2014 From: neugens at redhat.com (Mario Torre) Date: Thu, 26 Jun 2014 18:04:20 +0200 Subject: A pkg-config file for OpenJDK In-Reply-To: References: <20140626145657.GA2761@redhat.com> Message-ID: <1403798660.24742.0.camel@nirvana.localdomain> On Thu, 2014-06-26 at 16:16 +0100, Martijn Verburg wrote: > Hi Omair, > > Looks like a good idea to me, we've had a number of issues with this in > practice (we have a desktop tool on Linux) - could probably be backported > to 7u as well...? > > Cheers, > Martijn I support this too, this is a much needed and welcomed enhancement. Cheers, Mario From jonathan.gibbons at oracle.com Fri Jun 27 00:08:26 2014 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Thu, 26 Jun 2014 17:08:26 -0700 Subject: CFV: Project Valhalla In-Reply-To: <53A4E372.4070602@oracle.com> References: <53A4E372.4070602@oracle.com> Message-ID: <53ACB5FA.1040001@oracle.com> Vote: yes From david.holmes at oracle.com Fri Jun 27 07:10:01 2014 From: david.holmes at oracle.com (David Holmes) Date: Fri, 27 Jun 2014 17:10:01 +1000 Subject: A pkg-config file for OpenJDK In-Reply-To: <20140626145657.GA2761@redhat.com> References: <20140626145657.GA2761@redhat.com> Message-ID: <53AD18C9.7070405@oracle.com> On 27/06/2014 12:56 AM, Omair Majid wrote: > Hi, > > Over in Fedora, we have received requests from developers asking that > compiling JNI programs and liking against the JVM be made easier [0] > [1]. Some of the current difficulties include that the VM type (server, > client) is not known by other programs and so they have to fall back to > guessing where the libjvm.so that they should link against is. > > One standard approach on Linux for making linking against programs > easier is to use pkg-config [1] files. > > A pkg-config file essentially describes the CFLAGS and LDFLAGS that need > to be passed to the compiler and the linker to compile and link a > program successfully, without knowing anything other than the name of > the program or library to compile/link against. > > On Fedora/x86_64, such a file might look like (for OpenJDK 8): > >> jdk=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.5.x86_64 >> jre=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.5.x86_64/jre >> lib_arch=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.5.x86_64/jre/lib/amd64 > >> Name: java-1.8.0-openjdk >> Description: OpenJDK 8 >> Version: 1.8.0.5 >> Cflags: -I${jdk}/include -I${jdk}/include/linux >> Libs: -L${lib_arch} -L${lib_arch}/server -ljvm -ljava So you need one pkg-config file per VM type? David > Rather than doing something Fedora-specific, I would like to propose > carrying a template of this file upstream as part of the OpenJDK > project. Then, each distribution could modify it and change only the > bits that are specific to that distribution, and clients can rely on > having common or well-known names for everything else. > > One nice-to-have feature would be keep this file somewhat generic, so > other JPackage-style non-OpenJDK JDKs could adapt it too. That's why I > have used `java-1.8.0-openjdk` as the name above, but I am open to > changing it to whatever the consensus is. > > Does anyone else have any thoughts or comments about this? > > Thanks, > Omair > > [0] https://bugzilla.redhat.com/show_bug.cgi?id=449456 > [1] https://bugzilla.redhat.com/show_bug.cgi?id=740762 > [2] http://people.freedesktop.org/~dbn/pkg-config-guide.html > From aph at redhat.com Fri Jun 27 07:55:29 2014 From: aph at redhat.com (Andrew Haley) Date: Fri, 27 Jun 2014 08:55:29 +0100 Subject: A pkg-config file for OpenJDK In-Reply-To: <53AD18C9.7070405@oracle.com> References: <20140626145657.GA2761@redhat.com> <53AD18C9.7070405@oracle.com> Message-ID: <53AD2371.10702@redhat.com> On 27/06/14 08:10, David Holmes wrote: > On 27/06/2014 12:56 AM, Omair Majid wrote: >> Hi, >> >> Over in Fedora, we have received requests from developers asking that >> compiling JNI programs and liking against the JVM be made easier [0] >> [1]. Some of the current difficulties include that the VM type (server, >> client) is not known by other programs and so they have to fall back to >> guessing where the libjvm.so that they should link against is. >> >> One standard approach on Linux for making linking against programs >> easier is to use pkg-config [1] files. >> >> A pkg-config file essentially describes the CFLAGS and LDFLAGS that need >> to be passed to the compiler and the linker to compile and link a >> program successfully, without knowing anything other than the name of >> the program or library to compile/link against. >> >> On Fedora/x86_64, such a file might look like (for OpenJDK 8): >> >>> jdk=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.5.x86_64 >>> jre=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.5.x86_64/jre >>> lib_arch=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.5.x86_64/jre/lib/amd64 >> >>> Name: java-1.8.0-openjdk >>> Description: OpenJDK 8 >>> Version: 1.8.0.5 >>> Cflags: -I${jdk}/include -I${jdk}/include/linux >>> Libs: -L${lib_arch} -L${lib_arch}/server -ljvm -ljava > > So you need one pkg-config file per VM type? Per VM, certainly. I'm not sure there's any real need to be able, for example, to link against the x86 client VM. I suppose it would be nice if such a thing could be accommodated, but hardly necessary. Andrew. From mark.reinhold at oracle.com Fri Jun 27 15:35:10 2014 From: mark.reinhold at oracle.com (mark.reinhold at oracle.com) Date: Fri, 27 Jun 2014 08:35:10 -0700 Subject: CFV: Project Valhalla In-Reply-To: <53A6F0C4.8020907@oracle.com> References: <53A6F0C4.8020907@oracle.com> Message-ID: <20140627083510.24775@eggemoggin.niobe.net> Vote: yes - Mark From kumar.x.srinivasan at oracle.com Fri Jun 27 18:00:35 2014 From: kumar.x.srinivasan at oracle.com (Kumar Srinivasan) Date: Fri, 27 Jun 2014 11:00:35 -0700 Subject: CFV: Project Valhalla In-Reply-To: <53A6F0C4.8020907@oracle.com> References: <53A6F0C4.8020907@oracle.com> Message-ID: <53ADB143.2000807@oracle.com> Vote: yes Kumar On 6/22/2014 8:05 AM, Brian Goetz wrote: > I hereby propose the creation of Project Valhalla with myself as the > Lead and the HotSpot group as the sponsoring group. > > In accordance with the OpenJDK guidelines [1], this project will > provide a venue to explore and incubate advanced Java VM and Language > feature candidates such as Value Types [2], Generic Specialization > [3], enhanced volatiles [4] (and possibly other related topics, such > as reified generics.) > > The initial Reviewers and Committers will be: > > * Brian Goetz > * John Rose > * Paul Sandoz > * Maurizio Cimadamore > * Paul Govereau > * Dan Smith > * David Chase > * Mike Duigou > * Vladimir Ivanov > * Albert Noll > > The project will host at least the following mailing list: > > * valhalla-dev for developers > > and may eventually host specification lists if one or more JSRs is > subsequently created. > > The initial source of this project will be based on a clone of a JDK 9 > repository. Changes from the JDK 9 parent will be synced into > Valhalla periodically. Similar to Project Lambda, we will follow a > "commit first, review later" policy, as code will not flow directly > from the Valhalla repositories into the JDK repositories, but instead > will be done by a "curated merge" where select changes are extracted > into new changesets for incorporation into JDK repositories when they > are ready for inclusion. > > Votes are due by July 7, 2014, 9A GMT. > > Only current OpenJDK Members [5] are eligible to vote on this > motion. Votes must be cast in the open on the discuss list. > Replying to this message is sufficient if your mail program > honors the Reply-To header. > > For Lazy Consensus voting instructions, see [6]. > > > [1] http://openjdk.java.net/projects/#new-project > [2] http://cr.openjdk.java.net/~jrose/values/values-0.html > [3] https://bugs.openjdk.java.net/browse/JDK-8046267 > [4] http://openjdk.java.net/jeps/193 > [5] http://openjdk.java.net/census#members > [6] http://openjdk.java.net/projects/#new-project-vote From paul.sandoz at oracle.com Mon Jun 30 09:37:26 2014 From: paul.sandoz at oracle.com (Paul Sandoz) Date: Mon, 30 Jun 2014 11:37:26 +0200 Subject: CFV: Project Annotations Pipeline 2.0 In-Reply-To: <53ADD7CC.6050507@oracle.com> References: <53ADD7CC.6050507@oracle.com> Message-ID: Vote: yes Paul. From dalibor.topic at oracle.com Mon Jun 30 11:09:17 2014 From: dalibor.topic at oracle.com (dalibor topic) Date: Mon, 30 Jun 2014 13:09:17 +0200 Subject: A pkg-config file for OpenJDK In-Reply-To: <53AD2371.10702@redhat.com> References: <20140626145657.GA2761@redhat.com> <53AD18C9.7070405@oracle.com> <53AD2371.10702@redhat.com> Message-ID: <53B1455D.2000201@oracle.com> On 27.06.2014 09:55, Andrew Haley wrote: > On 27/06/14 08:10, David Holmes wrote: >> So you need one pkg-config file per VM type? > > Per VM, certainly. I'm not sure there's any real need to be able, for > example, to link against the x86 client VM. I suppose it would be nice > if such a thing could be accommodated, but hardly necessary. How would this work for compact profiles? A separate pkg-config file per profile? cheers, dalibor topic -- Dalibor Topic | Principal Product Manager Phone: +494089091214 | Mobile: +491737185961 ORACLE Deutschland B.V. & Co. KG | K?hneh?fe 5 | 22761 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 Oracle is committed to developing practices and products that help protect the environment From david.holmes at oracle.com Mon Jun 30 11:29:06 2014 From: david.holmes at oracle.com (David Holmes) Date: Mon, 30 Jun 2014 21:29:06 +1000 Subject: A pkg-config file for OpenJDK In-Reply-To: <53B1455D.2000201@oracle.com> References: <20140626145657.GA2761@redhat.com> <53AD18C9.7070405@oracle.com> <53AD2371.10702@redhat.com> <53B1455D.2000201@oracle.com> Message-ID: <53B14A02.9050905@oracle.com> On 30/06/2014 9:09 PM, dalibor topic wrote: > > > On 27.06.2014 09:55, Andrew Haley wrote: >> On 27/06/14 08:10, David Holmes wrote: > >>> So you need one pkg-config file per VM type? >> >> Per VM, certainly. I'm not sure there's any real need to be able, for >> example, to link against the x86 client VM. I suppose it would be nice >> if such a thing could be accommodated, but hardly necessary. > > How would this work for compact profiles? A separate pkg-config file per > profile? I don't see a need to have compact profile information in the pkg-config file (it's already in the release file). This is really just about locating the JRE in a given distribution. David > cheers, > dalibor topic > From dalibor.topic at oracle.com Mon Jun 30 11:55:42 2014 From: dalibor.topic at oracle.com (dalibor topic) Date: Mon, 30 Jun 2014 13:55:42 +0200 Subject: A pkg-config file for OpenJDK In-Reply-To: <53B14A02.9050905@oracle.com> References: <20140626145657.GA2761@redhat.com> <53AD18C9.7070405@oracle.com> <53AD2371.10702@redhat.com> <53B1455D.2000201@oracle.com> <53B14A02.9050905@oracle.com> Message-ID: <53B1503E.7000302@oracle.com> There was some chatter about packaging OpenJDK 8 profiles on the debian-java mailing list a few weeks ago.[0] Assuming a pkg-config file gets included and installed as part of an OpenJDK build, I'm just curious if that would cause additional issues to consider in the case of compact profiles (which may end up being dpkg/rpm installed in different locations, for example - I can't really say, since Debian packages haven't hit the repos yet). There is also the side question of how/if this would (need to) work on other platforms (Solaris, OS X, Windows) which pkg-config claims to work on. [1] cheers, dalibor topic [0] https://lists.debian.org/debian-java/2014/06/msg00012.html [1] http://www.freedesktop.org/wiki/Software/pkg-config/ On 30.06.2014 13:29, David Holmes wrote: > On 30/06/2014 9:09 PM, dalibor topic wrote: >> >> >> On 27.06.2014 09:55, Andrew Haley wrote: >>> On 27/06/14 08:10, David Holmes wrote: >> >>>> So you need one pkg-config file per VM type? >>> >>> Per VM, certainly. I'm not sure there's any real need to be able, for >>> example, to link against the x86 client VM. I suppose it would be nice >>> if such a thing could be accommodated, but hardly necessary. >> >> How would this work for compact profiles? A separate pkg-config file per >> profile? > > I don't see a need to have compact profile information in the pkg-config > file (it's already in the release file). This is really just about > locating the JRE in a given distribution. > > David > > >> cheers, >> dalibor topic >> -- Dalibor Topic | Principal Product Manager Phone: +494089091214 | Mobile: +491737185961 ORACLE Deutschland B.V. & Co. KG | K?hneh?fe 5 | 22761 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 Oracle is committed to developing practices and products that help protect the environment From dalibor.topic at oracle.com Mon Jun 30 12:30:01 2014 From: dalibor.topic at oracle.com (dalibor topic) Date: Mon, 30 Jun 2014 14:30:01 +0200 Subject: CFV: Project Annotations Pipeline 2.0 In-Reply-To: <53ADD7CC.6050507@oracle.com> References: <53ADD7CC.6050507@oracle.com> Message-ID: <53B15849.3010606@oracle.com> Vote: Yes. -- Dalibor Topic | Principal Product Manager Phone: +494089091214 | Mobile: +491737185961 ORACLE Deutschland B.V. & Co. KG | K?hneh?fe 5 | 22761 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 Oracle is committed to developing practices and products that help protect the environment From iris.clark at oracle.com Mon Jun 30 17:47:57 2014 From: iris.clark at oracle.com (Iris Clark) Date: Mon, 30 Jun 2014 10:47:57 -0700 (PDT) Subject: CFV: Project Valhalla In-Reply-To: <53A6F0C4.8020907@oracle.com> References: <53A6F0C4.8020907@oracle.com> Message-ID: <81b89db5-1bdf-46e5-a2ec-9d3473dc1c07@default> Vote: yes iris From alex.buckley at oracle.com Mon Jun 30 18:20:44 2014 From: alex.buckley at oracle.com (Alex Buckley) Date: Mon, 30 Jun 2014 11:20:44 -0700 Subject: CFV: Project Annotations Pipeline 2.0 In-Reply-To: <53ADD7CC.6050507@oracle.com> References: <53ADD7CC.6050507@oracle.com> Message-ID: <53B1AA7C.60900@oracle.com> Vote: Yes Alex On 6/27/2014 1:45 PM, Jonathan Gibbons wrote: > JDK 8 saw the introduction of three separate language features affecting > annotations and annotation processing. > > * Annotations on Java Types [1] > * Repeating Annotations [2] > * Lambda Expressions [3], which introduced new positions for annotations > > Although these features were developed independently, there is > non-trivial overlap between them, such as repeated type annotations on a > parameter type in a lambda expression. In addition, these features all > have to work well together with existing features such as the Annotation > Processing API, Language Model API, and javadoc. > > The machinery within javac to handle these features needs to be improved. > > Therefore, I hereby propose the creation of Project Annotations Pipeline > 2.0 with Joel Borggr?n-Franck as the Lead and the Compiler group as the > sponsoring group. > > In accordance with the OpenJDK guidelines [4], this project will provide > a venue to explore improvements to the overall handling of annotations > within the javac compilation pipeline. The project will be entirely > focussed on improving the implementation of the existing language and > API specifications, and is not intended as a venue to change or enhance > these specifications. > > The initial Reviewers and Committers will be: > > * Jonathan Gibbons > * Joel Borggr?n-Franck > * Maurizio Cimadamore > * Eric McCorkle > * Jan Lahoda > * Alex Buckley > > Initial Authors will be > > * Werner Dietl > * Steve Sides > * Andrey Eremeev > > The project will host the following mailing list for developers: > > * anno-pipeline-dev > > The initial source of this project will be based on a clone of a JDK 9 > repository. Changes from the JDK 9 parent will be synced into > Annotations Pipeline 2.0 periodically. Similar to Project Lambda, we > will follow a "commit first, review later" policy, as code will not flow > directly from the Annotations Pipeline 2.0 repositories into the JDK > repositories, but instead will be done by a "curated merge" where select > changes are extracted into new changesets for incorporation into JDK > repositories when they are ready for inclusion. > > Votes are due by July 11, 2014, 5PM PDT. > > Only current OpenJDK Members [5] are eligible to vote on this > motion. Votes must be cast in the open on the discuss list. > Replying to this message is sufficient if your mail program > honors the Reply-To header. > > For Lazy Consensus voting instructions, see [6]. > > > [1] https://www.jcp.org/en/jsr/detail?id=308 > [2] http://openjdk.java.net/jeps/120 > [3] https://jcp.org/en/jsr/detail?id=335 > [4] http://openjdk.java.net/projects/#new-project > [5] http://openjdk.java.net/census#members > [6] http://openjdk.java.net/projects/#new-project-vote From neugens at redhat.com Mon Jun 30 18:29:27 2014 From: neugens at redhat.com (Mario Torre) Date: Mon, 30 Jun 2014 20:29:27 +0200 Subject: CFV: Project Annotations Pipeline 2.0 In-Reply-To: <53ADD7CC.6050507@oracle.com> References: <53ADD7CC.6050507@oracle.com> Message-ID: <1404152967.3561.11.camel@nirvana.localdomain> On Fri, 2014-06-27 at 13:45 -0700, Jonathan Gibbons wrote: Vote: Yes, Cheers, Mario > JDK 8 saw the introduction of three separate language features affecting > annotations and annotation processing. > > * Annotations on Java Types [1] > * Repeating Annotations [2] > * Lambda Expressions [3], which introduced new positions for annotations > > Although these features were developed independently, there is > non-trivial overlap between them, such as repeated type annotations on a > parameter type in a lambda expression. In addition, these features all > have to work well together with existing features such as the Annotation > Processing API, Language Model API, and javadoc. > > The machinery within javac to handle these features needs to be improved. > > Therefore, I hereby propose the creation of Project Annotations Pipeline > 2.0 with Joel Borggr?n-Franck as the Lead and the Compiler group as the > sponsoring group. > > In accordance with the OpenJDK guidelines [4], this project will provide > a venue to explore improvements to the overall handling of annotations > within the javac compilation pipeline. The project will be entirely > focussed on improving the implementation of the existing language and > API specifications, and is not intended as a venue to change or enhance > these specifications. > > The initial Reviewers and Committers will be: > > * Jonathan Gibbons > * Joel Borggr?n-Franck > * Maurizio Cimadamore > * Eric McCorkle > * Jan Lahoda > * Alex Buckley > > Initial Authors will be > > * Werner Dietl > * Steve Sides > * Andrey Eremeev > > The project will host the following mailing list for developers: > > * anno-pipeline-dev > > The initial source of this project will be based on a clone of a JDK 9 > repository. Changes from the JDK 9 parent will be synced into > Annotations Pipeline 2.0 periodically. Similar to Project Lambda, we > will follow a "commit first, review later" policy, as code will not flow > directly from the Annotations Pipeline 2.0 repositories into the JDK > repositories, but instead will be done by a "curated merge" where select > changes are extracted into new changesets for incorporation into JDK > repositories when they are ready for inclusion. > > Votes are due by July 11, 2014, 5PM PDT. > > Only current OpenJDK Members [5] are eligible to vote on this > motion. Votes must be cast in the open on the discuss list. > Replying to this message is sufficient if your mail program > honors the Reply-To header. > > For Lazy Consensus voting instructions, see [6]. > > > [1] https://www.jcp.org/en/jsr/detail?id=308 > [2] http://openjdk.java.net/jeps/120 > [3] https://jcp.org/en/jsr/detail?id=335 > [4] http://openjdk.java.net/projects/#new-project > [5] http://openjdk.java.net/census#members > [6] http://openjdk.java.net/projects/#new-project-vote From maurizio.cimadamore at oracle.com Mon Jun 30 23:08:53 2014 From: maurizio.cimadamore at oracle.com (Maurizio Cimadamore) Date: Tue, 01 Jul 2014 00:08:53 +0100 Subject: CFV: Project Annotations Pipeline 2.0 In-Reply-To: <53ADD7CC.6050507@oracle.com> References: <53ADD7CC.6050507@oracle.com> Message-ID: <53B1EE05.8090003@oracle.com> Vote: yes Maurizio On 27/06/14 21:45, Jonathan Gibbons wrote: > JDK 8 saw the introduction of three separate language features > affecting annotations and annotation processing. > > * Annotations on Java Types [1] > * Repeating Annotations [2] > * Lambda Expressions [3], which introduced new positions for annotations > > Although these features were developed independently, there is > non-trivial overlap between them, such as repeated type annotations on > a parameter type in a lambda expression. In addition, these features > all have to work well together with existing features such as the > Annotation Processing API, Language Model API, and javadoc. > > The machinery within javac to handle these features needs to be improved. > > Therefore, I hereby propose the creation of Project Annotations > Pipeline 2.0 with Joel Borggr?n-Franck as the Lead and the Compiler > group as the sponsoring group. > > In accordance with the OpenJDK guidelines [4], this project will > provide a venue to explore improvements to the overall handling of > annotations within the javac compilation pipeline. The project will be > entirely focussed on improving the implementation of the existing > language and API specifications, and is not intended as a venue to > change or enhance these specifications. > > The initial Reviewers and Committers will be: > > * Jonathan Gibbons > * Joel Borggr?n-Franck > * Maurizio Cimadamore > * Eric McCorkle > * Jan Lahoda > * Alex Buckley > > Initial Authors will be > > * Werner Dietl > * Steve Sides > * Andrey Eremeev > > The project will host the following mailing list for developers: > > * anno-pipeline-dev > > The initial source of this project will be based on a clone of a JDK 9 > repository. Changes from the JDK 9 parent will be synced into > Annotations Pipeline 2.0 periodically. Similar to Project Lambda, we > will follow a "commit first, review later" policy, as code will not > flow directly from the Annotations Pipeline 2.0 repositories into the > JDK repositories, but instead will be done by a "curated merge" where > select changes are extracted into new changesets for incorporation > into JDK repositories when they are ready for inclusion. > > Votes are due by July 11, 2014, 5PM PDT. > > Only current OpenJDK Members [5] are eligible to vote on this > motion. Votes must be cast in the open on the discuss list. > Replying to this message is sufficient if your mail program > honors the Reply-To header. > > For Lazy Consensus voting instructions, see [6]. > > > [1] https://www.jcp.org/en/jsr/detail?id=308 > [2] http://openjdk.java.net/jeps/120 > [3] https://jcp.org/en/jsr/detail?id=335 > [4] http://openjdk.java.net/projects/#new-project > [5] http://openjdk.java.net/census#members > [6] http://openjdk.java.net/projects/#new-project-vote