Hi David,
On Wed, May 25, 2016 at 11:12 PM, David Dawson <
david.daw...@simplicityitself.com> wrote:
> if I can suggest, this will take in the order of months of dedicated
> effort from a small team to get running smoothly.
>
I understand that part - It is not going to be dedicated full time. But I
can promise a very sincere best possible effort.
>
> The core groovy team don't have the ability (ie, time) to organise this,
> which is why it's gone by the wayside.
>
> My suggestion is that those who are asking how to help should look to self
> organise. Set up a mailing list and dedicated slack channel, get all those
> who are involved in there and start to grind through setting up the
> environment, making small fixes etc. Bring in the core team when you can't
> progress.
>
>
This is going to be a couple of people for now. But yes, mailing
lists and IRCs will all be there eventually.
> it's going to be a chunk of work. The eclipse api and how to integrate
> with it will be te rub. Groovy eclipse has a bunch of patches that dig into
> the compiler to catch errors, handle failures and present that into the UI,
> so you'll need to start understanding the groovy compiler, and also the
> eclipse api.
>
>
This is roughly what I was expecting for. Thanks.
> I'd say, get the code and start beating the crap out of it over a weekend
> with anyone else that shows an interest, see where you get?
>
>
Agreed. Sometimes, brute force kick start and then streamlining does
work :) Thanks again for hinting.
> David.
>
>
> On 25 May 2016 at 18:22, Balachandran Sivakumar <benignb...@gmail.com>
> wrote:
>
>> Hi,
>>
>> On Mon, May 23, 2016 at 10:02 PM, Balachandran Sivakumar <
>> benignb...@gmail.com> wrote:
>>
>>> Hi Cedric,
>>>
>>> On Mon, May 23, 2016 at 5:27 PM, Cédric Champeau <
>>> cedric.champ...@gmail.com> wrote:
>>>
>>>> there's absolutely no need for an external DSL descriptor: all the
>>>>> constructs of the language, like extension methods or static builders are
>>>>> first class language features. The issue is, IDE support for Groovy is
>>>>> lacking (Groovy Eclipse is dead, IntelliJ needs to know specifics of
>>>>> static
>>>>> Gradle/Groovy scripts, ...)
>>>>
>>>>
>>> If we have to resurrect it, what would it take ? I mean, what skill
>>> set/knowledge should someone have to work on it and resurrect it ? Also,
>>> can someone here help with that effort ? Thanks
>>>
>>>
>> Can someone please help with this ? What would it take for someone
>> with reasonable Groovy/Java knowledge to pick up Goovy Eclipse and maintain
>> it ? Thanks
>>
>> --
>> Thank you
>> Balachandran Sivakumar
>>
>>
>
>
> --
>
>
> David Dawson | CEO | Simplicity Itself
>
> Tel +44 7866 011 256
> Skype: davidadawson
> david.daw...@simplicityitself.com
> http://www.simplicityitself.com
>
--
Thank you
Balachandran Sivakumar
