Hi Svata, thanks for the update... will try to do a comparison of 11 command line JShell and the actual integration layer and let you know about my findings.
Do you think it may be necessary to detect the version of JShell we are running on or even support multiple versions based ob the selected runtime platform version of a project? Thanks -Sven Svata Dedic <[email protected]> schrieb am Di., 24. Juli 2018, 08:55: > Hi, > > On 07/23/2018 05:19 PM, Sven Reimers wrote: > > Hi, > > > > I just tried to use the JShell integration in NetBeans for creating a > demo > > using an external jar, which has to be on the classpath. > > > the easiest way to access your JAR's classes is to create a project and > add that JAR as a library to the project. You can then invoke JShell > from the project's context menu - and the shell instance will be > configured with classpath from the project = your JAR. > > > Comparing my steps from within and without I recognized that not all > > commands seem to be available inside NetBeans and some are named > > differently.... > > > > NetBeans replace the 'command' layer of the JShell: the engine itself is > more or less embeddable, but the command interpreter is not; at least > not to the degree required by proper integration. Module system support > is limited (thanks for the reminder). > > Some of the commands were disabled (i.e. formats) since the IDE needs to > interpret shell's output somewhat. But an important command is missing, > please file a bug, the IDE should be kept consistent with the > commandline tool as much as possible. > > -Svata > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
