RE: Remembering imports between script invocations

Sounds more like the Groovy Shell or Groovy Console. Not too sure myself how the javax.script stuff is tied in. From: David Ekholm [mailto:da...@jalbum.net] Sent: Thursday, February 08, 2018 2:47 PM To: dev@groovy.apache.org Subject: Re: Remembering imports between script invocations How do I

Re: Remembering imports between script invocations

How do I do that via the javax.script API? Even if this is possible via the javax.script API, chances are that a user wishes to ad-hoc add another import, but as they are forgotten between script invocations, it makes it hard to use Groovy to interactively create, say a Swing or JavaFX UI one

RE: Remembering imports between script invocations

You can add all the imports you want to your compiler configuration and they will be consistently available for all scripts. From: David Ekholm [mailto:da...@jalbum.net] Sent: Thursday, February 08, 2018 2:12 PM To: dev@groovy.apache.org Subject: Remembering imports between script invocations

Remembering imports between script invocations

We're considering supporting Groovy as an additional scripting language to our web gallery software jAlbum (http://jalbum.net ), but one aspect bugs me: It doesn't seem like import statements are remembered between script invocations. This makes it far harder to use Groovy

Re: Parser version

Hi Russel, ANTLR-4 parser(i.e. the Parrot parser) is the default one for master, and ANTLR-2 parser is default for other branches. Cheers, Daniel.Sun -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Parser version

Is the ANTLR-2 parser really still the default one for Git master/HEAD? -- Russel. === Dr Russel Winder t: +44 20 7585 2200 41 Buckmaster Roadm: +44 7770 465 077 London SW11 1EN, UK w: www.russel.org.uk signature.asc Description: This is a