Re: Which issue do you MOST want to fix

[Basil Peace]

Hi, Daniel!

Nice to hear that!
Thanks.

-- 
Best regards,
Basil Peace


17.02.2019, 07:08, "Daniel.Sun" :
> Hi Basil,
>
>   We plan to re-write Groovydoc from scratch to gain better maintenance
> and fix all the existing issues. It is targeted to Groovy 3.0.0.
>
> Cheers,
> Daniel.Sun
>
> -
> Apache Groovy committer
> Blog: http://blog.sunlan.me
> Twitter: @daniel_sun
>
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html

Re: Groovy file associations on Windows

[Keegan Witt]

Actually, for Gpars, that's in the Groovy binary zip, so that's
included already.

On Sun, Feb 17, 2019 at 6:42 PM Keegan Witt  wrote:
>
> I hear you.  But where do you draw the line?
>
> There are a lot of popular libraries we also could include besides Gpars and 
> Scriptom (e.g. Geb, Spock, groovy-wslite, http-builder-ng, Gru, gstorm, dru, 
> GroovyServ, Gaiden, shoogr, etc) -- and those are just some ones with commits 
> in the last year that aren't for building or hosting web stuff.  There are 
> many more besides this.  And because it's just a bundle including whatever 
> the latest versions were at the time of a Groovy release for a specific 
> selection of projects (and not a project like sdkman), there's no way to mix 
> & match versions or upgrade independent of a Groovy release.
> Although I guess if we want the installer to include a bunch of different 
> library options, maybe we could have the installer fetch the requested jars 
> from the internet, I suppose.  Though I'm not sure how the file GUIDs would 
> work if we did that.  MSIs I've seen that do that (like have .NET Framework 
> as a dependency) usually invoke a separate MSI for each dependency.
>
> -Keegan
>
>
> On Tue, Feb 12, 2019 at 2:13 AM Daniel Sun  wrote:
>>
>> Yep. e.g. banks usually does not allow employees access Internet. Luckily
>> some of them will setup maven server.
>>
>> Cheers,
>> Daniel.Sun
>>
>>
>>
>>
>> --
>> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html

Re: New Groovy Windows installer

[Keegan Witt]

And the Quick Launch toolbar was removed in Windows 7 (although it can
be added back manually), so I think I won't bother with those
shortcuts.  I never noticed it was removed because I never used it.

On Sun, Feb 17, 2019 at 6:56 PM Keegan Witt  wrote:
>
> Update: The documentation directory on the start menu actually does
> get created -- Windows 10 just doesn't show subdirectories on start
> menu folders like previous versions of Windows did.
>
> On Sun, Feb 10, 2019 at 11:07 PM Keegan Witt  wrote:
> >
> > Oh, and one important note for those playing with the new installer:
> > uninstall the NSIS based Groovy first and make sure GROOVY_HOME,
> > %PROGRAM_FILES%\Groovy, and PATH are free from references to the old
> > installation before proceeding.
> >
> > On Sun, Feb 10, 2019 at 9:26 PM Keegan Witt  wrote:
> > >
> > > Oh, one more item
> > >
> > > Is 200 the installer version I should use?
> > >
> > >
> > > On Sun, Feb 10, 2019 at 9:24 PM Keegan Witt  wrote:
> > >>
> > >> I'm working on a new installer for Windows using WIX to create an MSI 
> > >> installer, which should be more robust for things like altering 
> > >> environment variables and make it easier to do corporate installations.
> > >>
> > >> I'm a total noob when it comes to Windows Installer and WIX, so I'm sure 
> > >> I've done some dumb things, but I hacked together a basic working 
> > >> installer this weekend.  I've put the initial version of the installer 
> > >> here.  Your feedback is appreciated.
> > >>
> > >> Some things I'm still thinking about or working on:
> > >>
> > >> The start menu shortcuts for documentation don't go into a subfolder, 
> > >> I'm not sure why.
> > >> Heat will generate new GUIDs for the binaries and docs folders every 
> > >> time the project is built -- I'm not sure if that's the correct thing to 
> > >> do.
> > >> Would you ever want to set GROOVY_HOME without adding to PATH?  Or add 
> > >> to PATH without setting GROOVY_HOME?  Currently the installer groups 
> > >> these together in a single feature.
> > >> We should use registry entries to remember which features the user 
> > >> selected to install, so those are automatically selected during upgrades.
> > >> Desktop shortcuts.
> > >> Quick launch shortcuts.  I don't think people use these much anymore, 
> > >> but I can throw them in -- maybe disabled by default?
> > >> Should I create an exe version of the installer as well as the msi?
> > >>
> > >> -Keegan

Re: New Groovy Windows installer

[Keegan Witt]

Update: The documentation directory on the start menu actually does
get created -- Windows 10 just doesn't show subdirectories on start
menu folders like previous versions of Windows did.

On Sun, Feb 10, 2019 at 11:07 PM Keegan Witt  wrote:
>
> Oh, and one important note for those playing with the new installer:
> uninstall the NSIS based Groovy first and make sure GROOVY_HOME,
> %PROGRAM_FILES%\Groovy, and PATH are free from references to the old
> installation before proceeding.
>
> On Sun, Feb 10, 2019 at 9:26 PM Keegan Witt  wrote:
> >
> > Oh, one more item
> >
> > Is 200 the installer version I should use?
> >
> >
> > On Sun, Feb 10, 2019 at 9:24 PM Keegan Witt  wrote:
> >>
> >> I'm working on a new installer for Windows using WIX to create an MSI 
> >> installer, which should be more robust for things like altering 
> >> environment variables and make it easier to do corporate installations.
> >>
> >> I'm a total noob when it comes to Windows Installer and WIX, so I'm sure 
> >> I've done some dumb things, but I hacked together a basic working 
> >> installer this weekend.  I've put the initial version of the installer 
> >> here.  Your feedback is appreciated.
> >>
> >> Some things I'm still thinking about or working on:
> >>
> >> The start menu shortcuts for documentation don't go into a subfolder, I'm 
> >> not sure why.
> >> Heat will generate new GUIDs for the binaries and docs folders every time 
> >> the project is built -- I'm not sure if that's the correct thing to do.
> >> Would you ever want to set GROOVY_HOME without adding to PATH?  Or add to 
> >> PATH without setting GROOVY_HOME?  Currently the installer groups these 
> >> together in a single feature.
> >> We should use registry entries to remember which features the user 
> >> selected to install, so those are automatically selected during upgrades.
> >> Desktop shortcuts.
> >> Quick launch shortcuts.  I don't think people use these much anymore, but 
> >> I can throw them in -- maybe disabled by default?
> >> Should I create an exe version of the installer as well as the msi?
> >>
> >> -Keegan

Re: Groovy file associations on Windows

[Keegan Witt]

I hear you.  But where do you draw the line?

There are a lot of popular libraries we also could include besides Gpars
and Scriptom (e.g. Geb , Spock
, groovy-wslite
, http-builder-ng
, Gru
, gstorm
, dru ,
GroovyServ , Gaiden
, shoogr
, etc) -- and those are just some ones
with commits in the last year that aren't for building or hosting web
stuff.  There are many more besides this.  And because it's just a bundle
including whatever the latest versions were at the time of a Groovy release
for a specific selection of projects (and not a project like sdkman),
there's no way to mix & match versions or upgrade independent of a Groovy
release.
Although I guess if we want the installer to include a bunch of different
library options, maybe we could have the installer fetch the requested jars
from the internet, I suppose.  Though I'm not sure how the file GUIDs would
work if we did that.  MSIs I've seen that do that (like have .NET Framework
as a dependency) usually invoke a separate MSI for each dependency.

-Keegan


On Tue, Feb 12, 2019 at 2:13 AM Daniel Sun  wrote:

> Yep. e.g. banks usually does not allow employees access Internet. Luckily
> some of them will setup maven server.
>
> Cheers,
> Daniel.Sun
>
>
>
>
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html
>