Steps towards integrating Kulla into JDK9

[Brian Goetz]

I guess we've got us a bikeshed :)

> As to the name of the package, that depends where the center is.  For
> someone wanting to look at how the tool is implemented jdk.jshell would
> be right. For an IDE using the evaluation API, jdk.eval or something
> like that would be appropriate. I think eval applies to both, but jshell
> only applies to the tool.

While this argument would surely hold up in court, I think the notion of 
"tool backed by a library" is one that is entirely understandable to 
people, and "jdk.jshell" is much more evocative of what it does than 
"jdk.eval".  I worry that we're sacrificing usability for correctness in 
this choice of name.  We want people to be able to look at the module 
names in the module graph and be able to have an idea of what it does.