Just a general reminder: Not every company using Groovy has unrestricted
internet access... :-)
On 11/02/2019 14:11, Keegan Witt wrote:
Do folks using it really need it to be in the lib directory with all
the other jars? Or could they just use Grapes/Grab?
If it's truly helpful, I can keep it. I'm just wondering if it's
On Mon, Feb 11, 2019, 2:19 AM Paul King <pa...@asert.com.au
I'd be inclined to keep GPars in the mix for now. It isn't
actively maintained but is still very useful in its current form
and I hope to put some time into it at some stage.
On Mon, Feb 11, 2019 at 12:24 PM Keegan Witt <keeganw...@gmail.com
In addition to removing projects that are no longer developed
from the Groovy Windows installer (Gpars, Gaelyk, Scriptom,
EasyB, Gant, GMock), I'm considering removing the exe files
haven't been compiled in quite a while and are just another
thing to maintain. As I see it, there are two primary
benefits these provide.
1. Provide a way to create file associations so you can
double click a Groovy file, or run myFile.groovy instead
of groovy myFile.groovy.
2. Hide the command window when launching GroovyConsole.
For #2, I can work around this with a VBScript file (or
NirCmd). #1 doesn't have a good way to solve other than the
current native binary solution since Launch4J doesn't support
<https://sourceforge.net/p/launch4j/bugs/162/>. My question
is, do many folks need this functionality? It's something I've
never personally used. Please weigh in with your thoughts.