CFV: New Project: Detroit

Magnus Ihse Bursie magnus.ihse.bursie at
Tue Feb 6 10:54:48 UTC 2018

 From a build perspective, I'm highly skeptical of build changes that 
"acquite sources" during the build process. I think the proper way to 
connect OpenJDK and the V8 sources is an implementation detail that can 
be solved as part of the Detroit project together with the Build Team, 
and not be decided upfront before the creation of the project.

If this is what you really meant, I'm all for a "yes" vote.


On 2018-01-31 17:38, Jim Laskey wrote:
> I hereby propose the creation of the Detroit Project with Hannes
> Wallnöfer as the Lead and the Compiler Group as the sponsoring Group.
> In accordance with the OpenJDK guidelines [1], this project will provide
> the home for the development of a native implementation of the
> javax.script package based on the Chrome V8 JavaScript engine [2]. Our
> starting point is the prototype presented by James Laskey at JVMLS 2017 [3].
> The resulting implementation will contain V8 itself together with the
> necessary Java and JavaScript bindings.  When loaded by a JVM process it
> provides a new javax.script.ScriptEngine [4] called "V8" that allows
> loading and execution of JavaScript code via V8.
> We also want to support a significant subset of the JavaScript
> extensions implemented in Nashorn [5], including accessing,
> instantiating, and extending or implementing Java types from JavaScript.
> The initially targeted platforms are Linux and Mac OS X. V8 sources are
> acquired by build processes. We do not plan to modify the V8 sources in
> any way.  Thus, maintenance and updating to new upstream releases will
> be straightforward.
> While the initial implementation will be based on JNI, the project could
> act as a platform for new technologies developed in Project Panama [6]
> in the future.
> The initial list of reviewers and committers will be based on the
> current reviewers and committers of the Nashorn team:
> James Laskey (reviewer)
> Sundararajan Athijegannathan (reviewer)
> Hannes Wallnöfer (reviewer)
> Srinivas Dama (committer)
> Priya Lakshmi Muthuswamy (committer)
> Votes are due by the end of Wednesday, February 7, 2018.
> Only current OpenJDK Members [7] 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 [8].
> Jim Laskey
> [1]
> [2]
> [3]
> [4]
> [5]
> [6]
> [7]
> [8]

More information about the discuss mailing list