Re: Groovy and semicolon at EOL

[Michael Brohl]

Same here. I'm not even sure if we really have clean groovy in the project, I assume it is mixed up with Java code in some areas.

I see the following directions:

But I agree to have a consistent style and we should use the Groovy language as it shoul be used (even if I would have get used to it and like a a defined code line ending better). 1. actively migrate to pure groovy and remove the semicolons (where applicable, it seems there are some cases where you need them, see https://dzone.com/articles/groovy-sometimes-you-still)

2. activeley put semicolons everywhere for consistency





Am 13.09.16 um 08:49 schrieb Taher Alkhateeb:

3. do 1., but only when a groovy file is edited anyway. This would slowly migrate groovy files. I'd be in favor for 3., as long as there are other more important things to do or there is a volunteer to do it.

Okay I missed the historical context.

Like Jacopo I also do not have a strong opinion, if it is easier and faster
to keep them, then keep them. The important thing is to take a direction
and stay with it.

smime.p7s
Description: S/MIME Cryptographic Signature