On 29.01.2016 18:05, Clark Richey wrote:
[...]
What do you think about having a page on the web site that
provides at least basic information about the status of on-going Groovy
development? This will serve the dual purpose of letting people know
that Groovy development isn’t dead and heighten a
When you put the antlr v4 parser, you also mean the Java 8 constructs, I
guess?
Because otherwise, that's really my wish list too :-)
On Sat, Jan 30, 2016 at 9:16 AM, Jochen Theodorou wrote:
> On 29.01.2016 18:05, Clark Richey wrote:
> [...]
>
>> What do you think about having a page on the web
yes
On 30.01.2016 09:31, Guillaume Laforge wrote:
When you put the antlr v4 parser, you also mean the Java 8 constructs, I
guess?
Because otherwise, that's really my wish list too :-)
On Sat, Jan 30, 2016 at 9:16 AM, Jochen Theodorou mailto:blackd...@gmx.org>> wrote:
On 29.01.2016 18:05,
As a side note, I'd like to conclude the decision about what to do with
regards to backwards compatibility in "next major groovy version", in
particular the decision about how to organize modules for jigsaw. I will
dig into my archives and revive the discussion :-)
Le 30 janv. 2016 10:18, "Jochen T
It still does not work. There are 490 pending build for this job. :(
@Cédric, @Paul: I guess you are the only ones with access to the build
server. It would be nice if you could check what is wrong.
Thanks,
Pascal
Am 28.01.2016 um 18:32 schrieb John Wagenleitner:
The TC builds for JDK7 haven'
There was a hung job that I killed. I also got rid of incubator from
the repo url. Master seems to have built. Just waiting for the CI
server to catch up on the 2_4_X branch.
Cheers, Paul.
On Sat, Jan 30, 2016 at 8:40 PM, Pascal Schumacher
wrote:
> It still does not work. There are 490 pending b
Everything is fine again. :)
Thank you very much!
Am 30.01.2016 um 12:16 schrieb Paul King:
There was a hung job that I killed. I also got rid of incubator from
the repo url. Master seems to have built. Just waiting for the CI
server to catch up on the 2_4_X branch.
Cheers, Paul.
On Sat, Jan
I think having that on the site would be great. I think you should also add the
simple explanation you provided in this thread as to why development has slowed.
Sent from my iPhone
>
--
Clark Richey
CHIEF TECHNOLOGY OFFICER
240.252.7507
cl...@factgem.com
WWW.FACTGEM.COM
This message and any in
I wouldn't include any comment on a slow down.
I'd see a comment like that on any OSS project page, I'd shy away from
using it.
If you look at the commit logs, there are very regular commits.
We just don't work on huge / big news-worthy features right now, but it's
still significant effort towards
Fair enough
Sent from my iPhone
>
--
Clark Richey
CHIEF TECHNOLOGY OFFICER
240.252.7507
cl...@factgem.com
WWW.FACTGEM.COM
This message and any included attachments are property of FactGem and its
affiliates, and are intended only for the addressee(s). The information
contained herein may inc
As one of the people who helped Groovy with the incubation, I don't see such
statement as anything even vaguely resembling the situation. What I see is a
tremendous growth in the community, project popularity, and very active
development. Considering that this "simple explanation" doesn't seem to b
11 matches
Mail list logo
