Groovy 5 is much like Java 6 and Java 7, it does not introduce many new
language features, but existing features have been polished a lot.
+1 for releasing Groovy 5 beta.
Cheers,
Daniel Sun
On 2025/05/09 13:24:56 Paul King wrote:
> Hi folks,
>
> We are due for some more releases shortly. We ju
Hi folks,
Eric did spot a couple of regressions that crept into the releases
despite our best efforts, but we think they shouldn't impact most
users. I'll go ahead with releases as planned but we'll probably do
another round of releases in a couple of weeks. Please do try out the
releases and shou
The 5.0.0-alpha-5 release is delayed. One of the few tasks I didn't
check when we upgraded to Gradle 8.5 was maven publishing. That isn't
working, e.g.:
* What went wrong:
Execution failed for task ':publishMavenPublicationToLocalFileRepository'.
> Failed to publish publication 'maven' to reposito
On 11.12.23 22:11, Paul King wrote:
Hi folks,
I was planning to do one more round of releases before the end of the
year. Let me know what might need to be done before I hit the go
button. It would need to be done in about a week (to get in before
Christmas) or I'd probably aim for around the 27
Our build process is impacted by:
https://status.gradle.com/incidents/7x4wqd7zv715
Investigating - Without any prior announcement, it looks like JCenter is
> now redirecting to Maven Central instead of serving artifacts.
> Builds that have build logic that relies on artifacts available only on
> J
I have no major changes for the branches listed.
Cheers,
Daniel Sun
On 2022/11/21 02:26:29 Paul King wrote:
> Hi folks,
>
> I plan to do some more releases soon (2.5, 3.0 and 4.0 branches). Time
> to get in any fixes you need or let me know if there is something we
> should be waiting for.
>
>
I was hoping to progress releases this week but I have numerous things
still to check, so I'll continue checking next week and start the
releases after that.
Cheers, Paul.
On Mon, Nov 21, 2022 at 12:26 PM Paul King wrote:
>
> Hi folks,
>
> I plan to do some more releases soon (2.5, 3.0 and 4.0 b
Will the next 3.0.x release support Java 17? Specifically GROOVY-10201 is still
open.
/peter
-Original Message-
From: Paul King
Sent: Monday, February 28, 2022 6:44 AM
To: Groovy_Developers
Subject: Next releases
Hi folks,
I was looking to do a 4.0.1 release and bumps for the 3.0.x
Is there something like a 4.0.1-rc-1 or similar artifact I could try?
On Mon, Feb 28, 2022 at 3:13 PM Lóránt Pintér wrote:
> I'm about to run another test with the latest to see if it works for
> Gradle. I'll be able to say if the fixes so far have resolved all the
> problems we encountered with
I'm about to run another test with the latest to see if it works for
Gradle. I'll be able to say if the fixes so far have resolved all the
problems we encountered with our upgrade in a couple hours.
On Mon, Feb 28, 2022 at 12:44 PM Paul King wrote:
> Hi folks,
>
> I was looking to do a 4.0.1 rel
Great, thanks!
On Tue, Sep 22, 2020 at 11:19 PM wrote:
> Hi Paul,
> ASM 9.0 have been released this morning.
>
> regards,
> Rémi
>
> --
>
> *De: *"paulk"
> *À: *"Remi Forax"
> *Cc: *"dev"
> *Envo
Hi Paul,
ASM 9.0 have been released this morning.
regards,
Rémi
> De: "paulk"
> À: "Remi Forax"
> Cc: "dev"
> Envoyé: Lundi 21 Septembre 2020 08:19:47
> Objet: Re: Next releases
> Thanks for the update Rémi. I saw the version number comm
Thanks for the update Rémi. I saw the version number commit, and figured it
must be close.
On Mon, Sep 21, 2020 at 4:10 PM Remi Forax wrote:
> ASM 9 should have been released this week end but we have an issue with
> our nexus requiring human intervention on the hardware,
> hopefully, this shoul
ASM 9 should have been released this week end but we have an issue with our
nexus requiring human intervention on the hardware,
hopefully, this should be fixed soon.
Rémi
> De: "paulk"
> À: "dev"
> Envoyé: Lundi 21 Septembre 2020 03:47:13
> Objet: Next releases
> Hi everyone,
> I hope to
Forgot to mention, please ignore any test deployments to the staging area.
I need to test out some jarjar changes and maven coordinate changes in the
release scripts and will be rolling them back until we are ready for a
real release.
Cheers, Paul.
On Mon, Sep 21, 2020 at 11:47 AM Paul King wrot
Hi Paul,
I have no more commits for the two releases.
Cheers,
Daniel Sun
On 2020/07/01 22:41:28, Paul King wrote:
> Hi everyone,
>
> I'd like to do another 2.5 and 3 release late this week or early next week.
> Time to work on any bug fixes that you want included or let me know if the
> tim
g
Subject: Re: next releases
This issue causes a horrible experience with IntelliJ and groovy code annotated
for bytecode generation with (e.g. Grails GORM, Micronaut, etc).
https://issues.apache.org/jira/projects/GROOVY/issues/GROOVY-9209<https://nam02.safelinks.protection.outlook.com/?ur
This issue causes a horrible experience with IntelliJ and groovy code
annotated for bytecode generation with (e.g. Grails GORM, Micronaut, etc).
https://issues.apache.org/jira/projects/GROOVY/issues/GROOVY-9209
🙏
On Thu, Jul 2, 2020 at 12:41 AM Paul King wrote:
>
> Hi everyone,
>
> I'd like t
Il 14/05/20 03:58, Paul King ha scritto:
Time to get in any bug fixes you want for those releases. Please also
let me know if you have any issues with the proposed timeframe.
Is it possible to backport GROOVY-9518 to 2.5.x?
And maybe have a look at GROOVY-9523 and GROOVY-9524?
Thanks,
Mauro
Yes, there is no rush on the 4 alpha release - as you say, we know there
are parts incomplete - but I figure the sooner we have something more
concrete the more feedback we'll get on what is still to do.
For your 1 and 2a fixes, if you have a partial fix but no time, perhaps try
to make it availabl
On 14.05.20 03:58, Paul King wrote:
Hi everyone,
I was going to volunteer to prepare the next releases in a couple of
days. Definitely 3.0.4, probably 2.5.12 and maybe our first alpha of 4.0
if I get time (or I may kick that off immediately after the others are
complete).
Time to get in any bu
Hi Paul,
It's OK to me.
Cheers,
Daniel.Sun
-
Apache Groovy committer & PMC member
Blog: http://blog.sunlan.me
Twitter: @daniel_sun
--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
Alternatively, groovy-antlr4 could be a separate jar.
If I understand correctly, then we are very confident that the new parser
accepts all programs that the old parser accepted, because that is easy to
test. But we do not know if it rejects all programs that the old parser
rejected, because that
Hi Daniel,
Other comments have kind of superseded this one. The only thing I'll
add is that I am not averse to finding a way to let 2.5 users try the
new parser somehow - but as Cédric said, not at the expensive of
overcomplicating our normal release.
Cheers, Paul.
On Tue, Jan 17, 2017 at 6:48
On Tue, Jan 17, 2017 at 1:04 AM, Cédric Champeau
wrote:
> My take is simpler than this. If Parrot should be included in 2.5, then
> remove the old parser and use it. If it's for 3.0, then it should not belong
> to the 2.5 beta, or it should be an external dependency (possibly tested by
> adding a
On Mon, Jan 16, 2017 at 6:09 PM, Paul King wrote:
> I am thinking we should do a 2.5.0-beta-1 release and possibly a 2.4.9
> in a couple of weeks time. For 2.5.0-beta-1, it would be nice to have
> the groovy macro PR reviewed and added (I know several of us have a
> review on our TODO lists) but I
On 17.01.2017 16:30, John Wagenleitner wrote:
On Tue, Jan 17, 2017 at 1:55 AM, Daniel Sun mailto:realblue...@hotmail.com>> wrote:
Hi Andres,
> I'd suggest to release 2.5.0-beta and 3.0-ea together. Just like the JDK
> team has been posting JDK9 EA releases, we could do the same.
On Tue, Jan 17, 2017 at 1:55 AM, Daniel Sun wrote:
> Hi Andres,
>
> > I'd suggest to release 2.5.0-beta and 3.0-ea together. Just like the JDK
> > team has been posting JDK9 EA releases, we could do the same. We know for
> > a fact we're going to break things, so let's make sure the public has
>
Hi Andres,
> I'd suggest to release 2.5.0-beta and 3.0-ea together. Just like the JDK
> team has been posting JDK9 EA releases, we could do the same. We know for
> a fact we're going to break things, so let's make sure the public has
> ample time to test out the changes.
I like your idea :)
Hello all,
Given the explanations made by Jochen and Cédric, we may be looking at the
following:
- 2.4.9: possible the latest release of the 2.4.x branch. Semantic
versioning dictates there should be only fixes.
- 2.5.x: new features and fixes. Requires old parser. No breaking changes
- 3.0-ea
It's not a simple decision. A beta isn't something to play with. There are
users, and companies, using Groovy. You cannot simply say "this is new,
let's try this". There are backwards compatibility concerns, as well as
deployment issues. We agreed, a few months ago, to make 3.0 the breaking
release
On 17.01.2017 10:17, Russel Winder wrote:
[...]
The 2.5 build still creates jars and indy jars. Isn't it about time we
settle this so there are only one set of jars in a build?
right, we should also change to indy by default for the betas
bye jochen
On 17.01.2017 10:04, Cédric Champeau wrote:
My take is simpler than this. If Parrot should be included in 2.5, then
remove the old parser and use it. If it's for 3.0, then it should not
belong to the 2.5 beta, or it should be an external dependency (possibly
tested by adding a jar manually).
On Tue, 2017-01-17 at 10:04 +0100, Cédric Champeau wrote:
> My take is simpler than this. If Parrot should be included in 2.5,
> then
> remove the old parser and use it. If it's for 3.0, then it should not
> belong to the 2.5 beta, or it should be an external dependency
> (possibly
> tested by addi
My take is simpler than this. If Parrot should be included in 2.5, then
remove the old parser and use it. If it's for 3.0, then it should not
belong to the 2.5 beta, or it should be an external dependency (possibly
tested by adding a jar manually).
2017-01-17 9:57 GMT+01:00 Søren Berg Glasius :
>
Can the parrot be packaged as separate jar that can be a dependency? That
way it can be included at will
On Tue, 17 Jan 2017 at 09:56 Guillaume Laforge wrote:
> This is a beta, not the final release, though.
>
> On Tue, Jan 17, 2017 at 9:54 AM, Cédric Champeau <
> cedric.champ...@gmail.com> wrot
This is a beta, not the final release, though.
On Tue, Jan 17, 2017 at 9:54 AM, Cédric Champeau
wrote:
> I'm reluctant on adding the experimental parser in a release. It requires
> a different version of antlr, which means more dependencies than we really
> need. We should keep the distribution
I'm reluctant on adding the experimental parser in a release. It requires a
different version of antlr, which means more dependencies than we really
need. We should keep the distribution as clean as possible. Not saying that
the new parser is dirty, but that the size and dependencies of the
distrib
It should definitely be included, so users can play with Parrot and report
their findings!
Guillaume
On Tue, Jan 17, 2017 at 9:48 AM, Daniel Sun wrote:
> Hi Paul,
>
> Will the new parser Parrot be included in 2.5.x releases as an
> optional parser? If developers want to give it a try, jus
Hi Paul,
Will the new parser Parrot be included in 2.5.x releases as an
optional parser? If developers want to give it a try, just turn on the
switch "-Dgroovy.antlr4=true".
Cheers,
Daniel.Sun
--
View this message in context:
http://groovy.329449.n5.nabble.com/next-releases-tp5737758p57
+1 on all this :-)
I'm impatient to have a beta of 2.5 out!
Guillaume
On Tue, Jan 17, 2017 at 3:09 AM, Paul King wrote:
> I am thinking we should do a 2.5.0-beta-1 release and possibly a 2.4.9
> in a couple of weeks time. For 2.5.0-beta-1, it would be nice to have
> the groovy macro PR reviewe
41 matches
Mail list logo
