Re: [scala-tools] Can we improve the Eclipse REPL?

The point is that if they were "working out" the details a few months ago, it's probably "worked out" by now.  Either way, an email to Jevgeni would clear up the whole cloud of uncertainty (assuming he's not already on the list).

As to the more fundamental issue on whether or not we should be giving JavaRebel "free advertising", I think that is a legitimate question.  The hang-up is that if we don't have JavaRebel integration baked into the plugin, then there is no way to get that functionality within SDT, even for developers who want it.  Would it be essentially saying that JavaRebel is an expected part of every Scala developer's toolset?  Yes, probably, but is that such a bad thing?  It comes down to the philosophical question of whether or not commercial tools should be encouraged from within OSS.  I'm sure Stallman would say "no", but to refuse to acknowledge commercial software severely limits the usefulness (and thus, the adoption) of open-source.  There are plenty of examples of real-world OSS which has integration with proprietary software.  For example, when you use Firefox to navigate to a .mp4 file, does that file open in the QuickTime plugin, or do you suffer through embedded VLC?  Isn't that just Firefox giving free advertising to Apple?

Coming back to JavaRebel, I think that this is a feature that enough developers have asked for -- including our Fearless Leader -- that it merits some serious attention.  If it were possible for JavaRebel users to just enable the functionality separately without impacting the rest of the user-base (in other words, without the obvious "JavaRebel License Here" type of hooks), I would agree that the obvious endorsement should be avoided.  However, that just isn't the case.  If SDT does not implement this functionality within the core plugin, it's not going to happen for anyone.

Daniel