It's indeed usually pretty flawless and effective.
Now, I don't fully understand what the ASF is using, but it involved "DNS
slaves", whatever that means.
On Sun, May 22, 2016 at 10:25 PM, Jim Northrop <
james.b.north...@googlemail.com> wrote:
> Just did 2 DNS name changes this afternoon using
Would love to see a mirror groovy doc.s site like say, groovy-lang.net so if
one is down we have a spare. Doc.s publish would push to two targets but quite
do-able.
Sent from my iPad
> On 22 May 2016, at 20:36, Mario Garcia wrote:
>
> Thanks for the explanation
Just did 2 DNS name changes this afternoon using goDaddy and worked flawlessly
with no changed required to my internal server. So i'm a bit puzzled why this
should be a biggie
Sent from my iPad
> On 22 May 2016, at 20:20, Guillaume Laforge wrote:
>
> And... it's back
> On May 22, 2016, at 11:20 AM, Guillaume Laforge wrote:
>
> And... it's back now!
YAY!
>
> Sorry again for the inconvenience, but this was really beyond our control
> unfortunately.
>
> Regarding your points, Steve:
>
> 1) If a company is stupid to "abandon" a
Thanks for the explanation Guillaume.
Just a quick question. I was wondering if, the same way Groovy has a mirror
in Github, could it be possible to have the Groovy site published as a
gh-pages? That would work as a possible documentation back-up in the
future. Of course I don't mean to do it any
And... it's back now!
Sorry again for the inconvenience, but this was really beyond our control
unfortunately.
Regarding your points, Steve:
1) If a company is stupid to "abandon" a great language like Groovy, too
bad for them ;-)
2) Well, we can't control perception obviously, and I didn't
On 22.05.2016 18:10, Steve Byrne wrote:
[...]
You can add
148.251.23.208 groovy-lang.org
to your hosts file to get the DNS entry right. It is important to mention its
temporary nature though. This bypasses the DNS system, and the IP will change
in the future.
maybe notwrorthy...
> On May 22, 2016, at 8:58 AM, Jochen Theodorou wrote:
>
> On 22.05.2016 16:40, Steve Byrne wrote:
>> [Copying from dev@groovy]
>>
>> What about backing out the change for now? This is looking really
>> bad...think about how it looks from the outside:
>>
>> 1) Pivotal
I'm debugging now *Groovy7316Bug*
So far, the test passes if we assume that the AST should be correct in a
later phase:
void testTypeCheckingBypassUsingExplicitTypeHint() {
assertScript '''
public T getSomething() { null }
public List getList() {
What about backing out the change for now? This is looking really bad...think
about how it looks from the outside:
1) Pivotal appears to "abandon" Groovy as a language -- does not send a
positive signal about the language's future prospects
2) _Without warning_ the groovy-lang.org
You might want to ping Sergei, Groovy Macro's creator.
I've added Sergei in CC.
Guillaume
On Sun, May 22, 2016 at 3:29 PM, Mario Garcia wrote:
> Yep, that's what I thought, but I was hoping somebody telling me It was my
> fault :P
>
> I'll take a further look to see if
Hi Mario,
as far as I remember groovy-macro is global ast-transformation. I guess
here is some side-effect/bug which causes the test failures. Sadly I
lack the necessary knowledge to investigate further.
-Pascal
Am 22.05.2016 um 14:33 schrieb Mario Garcia:
Hi:
I'm trying to write some
BTW I'm using
Linux Debian
open-jdk 1.8.0_72
2016-05-22 14:33 GMT+02:00 Mario Garcia :
> Hi:
>
> I'm trying to write some examples about the new features coming in the new
> 'groovy-macro' but I'm experiencing some issues.
>
> In order to use 'groovy-macro' in the specs
13 matches
Mail list logo