JShell: source in langtools vs JDK?

[Brian Goetz]

One additional comment: because jshell is so tightly coupled to javac, 
every time we add new node types to javac, we're going to have to add 
support to them for jshell.  While this does not mean it must be in 
langtools, it does seem we're more likely to remember to update both 
together if they share a repo and a test base.  (Of course, if 
langtools+jdk merge, this issue goes away.)

On 9/16/2015 6:06 PM, Robert Field wrote:
> As part of the JShell code review, Maurizio made the case that JShell should be in the JDK repo rather than langtools repo (where it is in the Kulla workspace).  We would like additional feedback on this before proceeding --
>
>> On Sep 11, 2015, at 8:25 AM, Maurizio Cimadamore <maurizio.cimadamore at oracle.com> wrote:
>>
>> One general high-level comment, which I also pointed out elsewhere, is that I'm not sure jshell really belongs in langtools; while it's semantically (obviously) related to langtools - it is a rather different beasts w.r.t. all other tools in langtools-land; the fact that it depends on the JDK (for jline, and for JDI in general) makes it very hard to run on top of a random JDK and then bootstrapping classes - which is a technique widely used to be able to run langtools tools w/o having to do a full build cycle. More specifically, talking about IDE integration, I don't see how IntelliJ/Netbeans langtools projects (and the langtools internal developer ant build) could be updated to be able to run/debug jshell w/o a full build.
>
>
>