Would someone kindly assign this to Antti Karanta, whom I'm hoping will test/review this for me.

Thanks,
Chris

USAGE: java -jar groovy-installer.jar

I guess the name of the .jar file should be changed. It isn't a "groovy" installer, but rather a "native launcher" installer.

> I guess the name of the .jar file should be changed. It isn't a "groovy" installer, but rather a "native launcher" installer.

Well, it seems to install the whole groovy distribution (I did not try it, just looked at the contents), so I would call it groovy installer. It just contains the native launcher (which the normal distro does not) and does the windows registry manipulations (again, did not try it).

I would still like you to add the simple groovy scriptom script to the native launcher page. I don't like to add code I did not write and have not tested, so I request you as the author of the code to do that.

Having an installer for groovy is something that has come up on the mailing list a few times, so if you take up the task of creating one, I think you should ask if the people on the mailing list have an opinion on how it should work, what it should do etc.

On the other hand, if you are only addressing the native launcher, I think the scriptom script you provided is sufficient - ATM native launcher is a separate download anyway, so someone getting that can as well run the scriptom script to manipulate his registry. On the other hand, I don't think anyone will want to download and install a full groovy distro just to get the registry settings correct for the native launcher.

The installer can be downloaded on the normal download pages.

The installer does not set PATHEXT yet. If this is really necessary, please reopen the issue.

Guillaume deems PATHEXT to be of importance

Added PATHEXT

PATHEXT is implemented.