groovy-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Laforge <glafo...@gmail.com>
Subject Re: Native Launcher [was Scriptom]
Date Wed, 22 Jul 2015 05:54:43 GMT
I've enabled issues for both Scriptom and groovy-native-launcher.
It's important to be able to raise issues! :-)

On Wed, Jul 22, 2015 at 7:02 AM, Keegan Witt <keeganwitt@gmail.com> wrote:

> Awesome!  Should Github issue tracking be enabled on it and the scriptom
> repo?  If not, should we disable issue tracking on the windows installer
> repo?
>
> -Keegan
>
> On Tue, Jul 21, 2015 at 6:33 PM, Guillaume Laforge <glaforge@gmail.com>
> wrote:
>
>> It's now here!
>>
>> https://github.com/groovy/groovy-native-launcher
>>
>> I've updated the readme (from text to asciidoc) and removed the reference
>> to the old content from the Groovy wiki.
>> Whenever we have a pointer for a new home for its doc, we should add that
>> back in the description.
>>
>> Guillaume
>>
>>
>> On Wed, Jul 22, 2015 at 12:14 AM, Keegan Witt <keeganwitt@gmail.com>
>> wrote:
>>
>>> That'd be the way to avoid creating any work for Ben :)  I don't think
>>> it matters too much either way.  Unless you think it'd be confusing for
>>> users to see a read-only repo as the apparent "upstream" repo.  It's
>>> probably pretty obvious though.
>>>
>>> -Keegan
>>>
>>> On Tue, Jul 21, 2015 at 5:54 PM, Guillaume Laforge <glaforge@gmail.com>
>>> wrote:
>>>
>>>> Ah right, as it wasn't in a module in the old groovy repo, it's still
>>>> there through the codehaus->github migration!
>>>> Should we fork it under the groovy github repo? I guess that's the way
>>>> to go?
>>>>
>>>> On Tue, Jul 21, 2015 at 11:52 PM, Keegan Witt <keeganwitt@gmail.com>
>>>> wrote:
>>>>
>>>>> https://github.com/codehaus/groovy-native-launcher unless I'm
>>>>> misinformed.
>>>>>
>>>>> -Keegan
>>>>> On Jul 21, 2015 5:47 PM, "Guillaume Laforge" <glaforge@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Where is the native launcher repo?
>>>>>> I'm happy to help as long as someone helps maintain it :-)
>>>>>>
>>>>>> On Tue, Jul 21, 2015 at 11:28 PM, Keegan Witt <keeganwitt@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Also, how are we going to handle the Native Launcher repo?  Do
we
>>>>>>> want to transfer from codehaus to groovy?  Or have groovy fork
the codehaus
>>>>>>> repo?
>>>>>>>
>>>>>>> -Keegan
>>>>>>>
>>>>>>> On Tue, Jul 21, 2015 at 5:23 PM, Keegan Witt <keeganwitt@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Cool.  I transferred my repo to the groovy org.  Should we
create a
>>>>>>>> new team under the groovy org for this?
>>>>>>>>
>>>>>>>> -Keegan
>>>>>>>>
>>>>>>>> On Tue, Jul 21, 2015 at 4:58 PM, Guillaume Laforge <
>>>>>>>> glaforge@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> The empty groovy-windows-installer is now gone, Keegan.
>>>>>>>>>
>>>>>>>>> On Tue, Jul 21, 2015 at 4:46 PM, Keegan Witt <keeganwitt@gmail.com
>>>>>>>>> > wrote:
>>>>>>>>>
>>>>>>>>>> Actually, if you look at the Windows installer (
>>>>>>>>>> https://github.com/keeganwitt/groovy-windows-installer),
you'll
>>>>>>>>>> see it's including binaries from the native installer.
 I believe this was
>>>>>>>>>> done for Windows file-association purposes.
>>>>>>>>>>
>>>>>>>>>> Speaking of which, if you remove the empty repo currently
under
>>>>>>>>>> the org (https://github.com/groovy/groovy-windows-installer),
>>>>>>>>>> I'll transfer ownership of aforementioned repo to
replace it.
>>>>>>>>>>
>>>>>>>>>> -Keegan
>>>>>>>>>>
>>>>>>>>>> On Mon, Jul 20, 2015 at 12:09 PM, Russel Winder <
>>>>>>>>>> russel@winder.org.uk> wrote:
>>>>>>>>>>
>>>>>>>>>>> On Sat, 2015-07-18 at 10:36 +0200, Guillaume
Laforge wrote:
>>>>>>>>>>> > With GroovyServ (https://kobo.github.io/groovyserv/)
I don't
>>>>>>>>>>> think we
>>>>>>>>>>> > need
>>>>>>>>>>> > a native launcher, do we?
>>>>>>>>>>>
>>>>>>>>>>> I have never used either, but then I am not actually
using
>>>>>>>>>>> Groovy.
>>>>>>>>>>>
>>>>>>>>>>> I'll hang on to the repository for a while in
case we want to do
>>>>>>>>>>> something with it later.
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Russel.
>>>>>>>>>>>
>>>>>>>>>>> =============================================================================
>>>>>>>>>>> Dr Russel Winder      t: +44 20 7585 2200   voip:
>>>>>>>>>>> sip:russel.winder@ekiga.net
>>>>>>>>>>> 41 Buckmaster Road    m: +44 7770 465 077   xmpp:
>>>>>>>>>>> russel@winder.org.uk
>>>>>>>>>>> London SW11 1EN, UK   w: www.russel.org.uk  skype:
russel_winder
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Guillaume Laforge
>>>>>>>>> Groovy Project Manager
>>>>>>>>> Product Ninja & Advocate at Restlet <http://restlet.com>
>>>>>>>>>
>>>>>>>>> Blog: http://glaforge.appspot.com/
>>>>>>>>> Social: @glaforge <http://twitter.com/glaforge>
/ Google+
>>>>>>>>> <https://plus.google.com/u/0/114130972232398734985/posts>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Guillaume Laforge
>>>>>> Groovy Project Manager
>>>>>> Product Ninja & Advocate at Restlet <http://restlet.com>
>>>>>>
>>>>>> Blog: http://glaforge.appspot.com/
>>>>>> Social: @glaforge <http://twitter.com/glaforge> / Google+
>>>>>> <https://plus.google.com/u/0/114130972232398734985/posts>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Guillaume Laforge
>>>> Groovy Project Manager
>>>> Product Ninja & Advocate at Restlet <http://restlet.com>
>>>>
>>>> Blog: http://glaforge.appspot.com/
>>>> Social: @glaforge <http://twitter.com/glaforge> / Google+
>>>> <https://plus.google.com/u/0/114130972232398734985/posts>
>>>>
>>>
>>>
>>
>>
>> --
>> Guillaume Laforge
>> Apache Groovy committer & PMC member
>> Product Ninja & Advocate at Restlet <http://restlet.com>
>>
>> Blog: http://glaforge.appspot.com/
>> Social: @glaforge <http://twitter.com/glaforge> / Google+
>> <https://plus.google.com/u/0/114130972232398734985/posts>
>>
>
>


-- 
Guillaume Laforge
Apache Groovy committer & PMC member
Product Ninja & Advocate at Restlet <http://restlet.com>

Blog: http://glaforge.appspot.com/
Social: @glaforge <http://twitter.com/glaforge> / Google+
<https://plus.google.com/u/0/114130972232398734985/posts>

Mime
View raw message