You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@groovy.apache.org by Paul King <pa...@apache.org> on 2018/04/09 06:07:53 UTC
[ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Dear community,
The Apache Groovy team is pleased to announce version 2.5.0-rc-1 of
Apache Groovy.
Apache Groovy is a multi-faceted programming language for the JVM.
Further details can be found at the http://groovy.apache.org website.
This is a pre-release of a new version of Groovy.
We greatly appreciate any feedback you can give us when using this version.
This release includes 18 bug fixes/improvements as outlined in the changelog:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12342817
Sources, convenience binaries, downloadable documentation and an SDK
bundle can be found at: http://www.groovy-lang.org/download.html
We recommend you verify your installation using the information on that page.
Jars are also available within the major binary repositories.
We welcome your help and feedback and in particular want
to thank everyone who contributed to this release.
For more information on how to report problems, and to get involved,
visit the project website at https://groovy.apache.org/
Best regards,
The Apache Groovy team.
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by Marcin Erdmann <ma...@proxerd.pl>.
https://issues.apache.org/jira/browse/GROOVY-8541
I took the liberty to set priority and fix version.
On Tue, Apr 10, 2018 at 10:55 AM, Cédric Champeau <cedric.champeau@gmail.com
> wrote:
>
>
> 2018-04-10 11:52 GMT+02:00 Marcin Erdmann <ma...@proxerd.pl>:
>
>> Yeah, I've noticed the zip packaging in pom but wasn't sure if that's the
>> reason why Gradle tries to resolve the jar for that artifact. Should I
>> create an issue for it?
>>
>
> Yes, please :) Note that Maven behaves the same and tries to download the
> jar too.
>
>
>
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by Marcin Erdmann <ma...@proxerd.pl>.
https://issues.apache.org/jira/browse/GROOVY-8541
I took the liberty to set priority and fix version.
On Tue, Apr 10, 2018 at 10:55 AM, Cédric Champeau <cedric.champeau@gmail.com
> wrote:
>
>
> 2018-04-10 11:52 GMT+02:00 Marcin Erdmann <ma...@proxerd.pl>:
>
>> Yeah, I've noticed the zip packaging in pom but wasn't sure if that's the
>> reason why Gradle tries to resolve the jar for that artifact. Should I
>> create an issue for it?
>>
>
> Yes, please :) Note that Maven behaves the same and tries to download the
> jar too.
>
>
>
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by Cédric Champeau <ce...@gmail.com>.
2018-04-10 11:52 GMT+02:00 Marcin Erdmann <ma...@proxerd.pl>:
> Yeah, I've noticed the zip packaging in pom but wasn't sure if that's the
> reason why Gradle tries to resolve the jar for that artifact. Should I
> create an issue for it?
>
Yes, please :) Note that Maven behaves the same and tries to download the
jar too.
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by Cédric Champeau <ce...@gmail.com>.
2018-04-10 11:52 GMT+02:00 Marcin Erdmann <ma...@proxerd.pl>:
> Yeah, I've noticed the zip packaging in pom but wasn't sure if that's the
> reason why Gradle tries to resolve the jar for that artifact. Should I
> create an issue for it?
>
Yes, please :) Note that Maven behaves the same and tries to download the
jar too.
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by Marcin Erdmann <ma...@proxerd.pl>.
Yeah, I've noticed the zip packaging in pom but wasn't sure if that's the
reason why Gradle tries to resolve the jar for that artifact. Should I
create an issue for it?
I'll assume that this will be fixed in rc-2 and I will try again when it's
released.
On Tue, Apr 10, 2018 at 8:20 AM, Cédric Champeau <ce...@gmail.com>
wrote:
> There's a bug in the published pom: it says <packaging>zip</packaging>
> instead of <packaging>pom</packaging>. We should fix this, thanks for the
> report!
>
>
>
> 2018-04-09 23:15 GMT+02:00 Marcin Erdmann <ma...@proxerd.pl>:
>
>> Paul,
>>
>> I'm having a go at giving this release a spin by updating Geb's build to
>> use it but unfortunately I'm not having any luck with trying to use the
>> groovy-all artifact. I understand from the earlier thread about updates to
>> the build on the dev list that the jar for that artifact is not published
>> and it's supposed to just be a dependency only aritfact which will be
>> useful for resolving all of Groovy's modules.
>>
>> To quote you:
>>
>> > The idea (once finished) is that you can still depend on a groovy-all dependency
>> via Maven or Gradle and you'll automatically get the multiple required
>> equivalent jars of the current single groovy-all jar.
>>
>> Unfortunately this is not the case. Given a simple build like:
>>
>>
>> plugins {
>> id 'groovy'
>> }
>>
>> repositories {
>> mavenCentral()
>> }
>>
>> dependencies {
>> compile 'org.codehaus.groovy:groovy-all:2.5.0-rc-1'
>> }
>>
>>
>> and an empty Groovy class in the main source set when running `gradle
>> build` I'm getting:
>>
>>
>> Could not resolve all dependencies for configuration ':compileClasspath'.
>> > Could not find groovy-all.jar (org.codehaus.groovy:groovy-al
>> l:2.5.0-rc-1).
>> Searched in the following locations:
>> https://repo1.maven.org/maven2/org/codehaus/groovy/groovy-
>> all/2.5.0-rc-1/groovy-all-2.5.0-rc-1.jar
>>
>>
>> I tried changing the dependency to 'org.codehaus.groovy:groovy-al
>> l:2.5.0-rc-1@pom' but while in that case dependency resolution phase succeeds
>> the build itself then fails with:
>>
>>
>> Cannot infer Groovy class path because no Groovy Jar was found on class
>> path: configuration ':compileClasspath'
>>
>>
>> I do not see any of the modules apart from groovy-all itself being added
>> to the configuration when running `gradle dependencies --configuration
>> compile`:
>>
>>
>> compile - Dependencies for source set 'main'.
>> \--- org.codehaus.groovy:groovy-all:2.5.0-rc-1
>>
>>
>> Am I doing something wrong or is the way forward not using groovy-all
>> anymore and explicitly depending on only the used modules?
>>
>> Cheers,
>> Marcin
>>
>> On Mon, Apr 9, 2018 at 7:07 AM, Paul King <pa...@apache.org> wrote:
>>
>>> Dear community,
>>>
>>> The Apache Groovy team is pleased to announce version 2.5.0-rc-1 of
>>> Apache Groovy.
>>> Apache Groovy is a multi-faceted programming language for the JVM.
>>> Further details can be found at the http://groovy.apache.org website.
>>>
>>> This is a pre-release of a new version of Groovy.
>>> We greatly appreciate any feedback you can give us when using this
>>> version.
>>>
>>> This release includes 18 bug fixes/improvements as outlined in the
>>> changelog:
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>>> ctId=12318123&version=12342817
>>>
>>> Sources, convenience binaries, downloadable documentation and an SDK
>>> bundle can be found at: http://www.groovy-lang.org/download.html
>>> We recommend you verify your installation using the information on that
>>> page.
>>>
>>> Jars are also available within the major binary repositories.
>>>
>>> We welcome your help and feedback and in particular want
>>> to thank everyone who contributed to this release.
>>>
>>> For more information on how to report problems, and to get involved,
>>> visit the project website at https://groovy.apache.org/
>>>
>>> Best regards,
>>>
>>> The Apache Groovy team.
>>>
>>
>>
>
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by Marcin Erdmann <ma...@proxerd.pl>.
Yeah, I've noticed the zip packaging in pom but wasn't sure if that's the
reason why Gradle tries to resolve the jar for that artifact. Should I
create an issue for it?
I'll assume that this will be fixed in rc-2 and I will try again when it's
released.
On Tue, Apr 10, 2018 at 8:20 AM, Cédric Champeau <ce...@gmail.com>
wrote:
> There's a bug in the published pom: it says <packaging>zip</packaging>
> instead of <packaging>pom</packaging>. We should fix this, thanks for the
> report!
>
>
>
> 2018-04-09 23:15 GMT+02:00 Marcin Erdmann <ma...@proxerd.pl>:
>
>> Paul,
>>
>> I'm having a go at giving this release a spin by updating Geb's build to
>> use it but unfortunately I'm not having any luck with trying to use the
>> groovy-all artifact. I understand from the earlier thread about updates to
>> the build on the dev list that the jar for that artifact is not published
>> and it's supposed to just be a dependency only aritfact which will be
>> useful for resolving all of Groovy's modules.
>>
>> To quote you:
>>
>> > The idea (once finished) is that you can still depend on a groovy-all dependency
>> via Maven or Gradle and you'll automatically get the multiple required
>> equivalent jars of the current single groovy-all jar.
>>
>> Unfortunately this is not the case. Given a simple build like:
>>
>>
>> plugins {
>> id 'groovy'
>> }
>>
>> repositories {
>> mavenCentral()
>> }
>>
>> dependencies {
>> compile 'org.codehaus.groovy:groovy-all:2.5.0-rc-1'
>> }
>>
>>
>> and an empty Groovy class in the main source set when running `gradle
>> build` I'm getting:
>>
>>
>> Could not resolve all dependencies for configuration ':compileClasspath'.
>> > Could not find groovy-all.jar (org.codehaus.groovy:groovy-al
>> l:2.5.0-rc-1).
>> Searched in the following locations:
>> https://repo1.maven.org/maven2/org/codehaus/groovy/groovy-
>> all/2.5.0-rc-1/groovy-all-2.5.0-rc-1.jar
>>
>>
>> I tried changing the dependency to 'org.codehaus.groovy:groovy-al
>> l:2.5.0-rc-1@pom' but while in that case dependency resolution phase succeeds
>> the build itself then fails with:
>>
>>
>> Cannot infer Groovy class path because no Groovy Jar was found on class
>> path: configuration ':compileClasspath'
>>
>>
>> I do not see any of the modules apart from groovy-all itself being added
>> to the configuration when running `gradle dependencies --configuration
>> compile`:
>>
>>
>> compile - Dependencies for source set 'main'.
>> \--- org.codehaus.groovy:groovy-all:2.5.0-rc-1
>>
>>
>> Am I doing something wrong or is the way forward not using groovy-all
>> anymore and explicitly depending on only the used modules?
>>
>> Cheers,
>> Marcin
>>
>> On Mon, Apr 9, 2018 at 7:07 AM, Paul King <pa...@apache.org> wrote:
>>
>>> Dear community,
>>>
>>> The Apache Groovy team is pleased to announce version 2.5.0-rc-1 of
>>> Apache Groovy.
>>> Apache Groovy is a multi-faceted programming language for the JVM.
>>> Further details can be found at the http://groovy.apache.org website.
>>>
>>> This is a pre-release of a new version of Groovy.
>>> We greatly appreciate any feedback you can give us when using this
>>> version.
>>>
>>> This release includes 18 bug fixes/improvements as outlined in the
>>> changelog:
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>>> ctId=12318123&version=12342817
>>>
>>> Sources, convenience binaries, downloadable documentation and an SDK
>>> bundle can be found at: http://www.groovy-lang.org/download.html
>>> We recommend you verify your installation using the information on that
>>> page.
>>>
>>> Jars are also available within the major binary repositories.
>>>
>>> We welcome your help and feedback and in particular want
>>> to thank everyone who contributed to this release.
>>>
>>> For more information on how to report problems, and to get involved,
>>> visit the project website at https://groovy.apache.org/
>>>
>>> Best regards,
>>>
>>> The Apache Groovy team.
>>>
>>
>>
>
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by Cédric Champeau <ce...@gmail.com>.
There's a bug in the published pom: it says <packaging>zip</packaging>
instead of <packaging>pom</packaging>. We should fix this, thanks for the
report!
2018-04-09 23:15 GMT+02:00 Marcin Erdmann <ma...@proxerd.pl>:
> Paul,
>
> I'm having a go at giving this release a spin by updating Geb's build to
> use it but unfortunately I'm not having any luck with trying to use the
> groovy-all artifact. I understand from the earlier thread about updates to
> the build on the dev list that the jar for that artifact is not published
> and it's supposed to just be a dependency only aritfact which will be
> useful for resolving all of Groovy's modules.
>
> To quote you:
>
> > The idea (once finished) is that you can still depend on a groovy-all dependency
> via Maven or Gradle and you'll automatically get the multiple required
> equivalent jars of the current single groovy-all jar.
>
> Unfortunately this is not the case. Given a simple build like:
>
>
> plugins {
> id 'groovy'
> }
>
> repositories {
> mavenCentral()
> }
>
> dependencies {
> compile 'org.codehaus.groovy:groovy-all:2.5.0-rc-1'
> }
>
>
> and an empty Groovy class in the main source set when running `gradle
> build` I'm getting:
>
>
> Could not resolve all dependencies for configuration ':compileClasspath'.
> > Could not find groovy-all.jar (org.codehaus.groovy:groovy-
> all:2.5.0-rc-1).
> Searched in the following locations:
> https://repo1.maven.org/maven2/org/codehaus/groovy/
> groovy-all/2.5.0-rc-1/groovy-all-2.5.0-rc-1.jar
>
>
> I tried changing the dependency to 'org.codehaus.groovy:groovy-
> all:2.5.0-rc-1@pom' but while in that case dependency resolution phase succeeds
> the build itself then fails with:
>
>
> Cannot infer Groovy class path because no Groovy Jar was found on class
> path: configuration ':compileClasspath'
>
>
> I do not see any of the modules apart from groovy-all itself being added
> to the configuration when running `gradle dependencies --configuration
> compile`:
>
>
> compile - Dependencies for source set 'main'.
> \--- org.codehaus.groovy:groovy-all:2.5.0-rc-1
>
>
> Am I doing something wrong or is the way forward not using groovy-all
> anymore and explicitly depending on only the used modules?
>
> Cheers,
> Marcin
>
> On Mon, Apr 9, 2018 at 7:07 AM, Paul King <pa...@apache.org> wrote:
>
>> Dear community,
>>
>> The Apache Groovy team is pleased to announce version 2.5.0-rc-1 of
>> Apache Groovy.
>> Apache Groovy is a multi-faceted programming language for the JVM.
>> Further details can be found at the http://groovy.apache.org website.
>>
>> This is a pre-release of a new version of Groovy.
>> We greatly appreciate any feedback you can give us when using this
>> version.
>>
>> This release includes 18 bug fixes/improvements as outlined in the
>> changelog:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>> ctId=12318123&version=12342817
>>
>> Sources, convenience binaries, downloadable documentation and an SDK
>> bundle can be found at: http://www.groovy-lang.org/download.html
>> We recommend you verify your installation using the information on that
>> page.
>>
>> Jars are also available within the major binary repositories.
>>
>> We welcome your help and feedback and in particular want
>> to thank everyone who contributed to this release.
>>
>> For more information on how to report problems, and to get involved,
>> visit the project website at https://groovy.apache.org/
>>
>> Best regards,
>>
>> The Apache Groovy team.
>>
>
>
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by Cédric Champeau <ce...@gmail.com>.
There's a bug in the published pom: it says <packaging>zip</packaging>
instead of <packaging>pom</packaging>. We should fix this, thanks for the
report!
2018-04-09 23:15 GMT+02:00 Marcin Erdmann <ma...@proxerd.pl>:
> Paul,
>
> I'm having a go at giving this release a spin by updating Geb's build to
> use it but unfortunately I'm not having any luck with trying to use the
> groovy-all artifact. I understand from the earlier thread about updates to
> the build on the dev list that the jar for that artifact is not published
> and it's supposed to just be a dependency only aritfact which will be
> useful for resolving all of Groovy's modules.
>
> To quote you:
>
> > The idea (once finished) is that you can still depend on a groovy-all dependency
> via Maven or Gradle and you'll automatically get the multiple required
> equivalent jars of the current single groovy-all jar.
>
> Unfortunately this is not the case. Given a simple build like:
>
>
> plugins {
> id 'groovy'
> }
>
> repositories {
> mavenCentral()
> }
>
> dependencies {
> compile 'org.codehaus.groovy:groovy-all:2.5.0-rc-1'
> }
>
>
> and an empty Groovy class in the main source set when running `gradle
> build` I'm getting:
>
>
> Could not resolve all dependencies for configuration ':compileClasspath'.
> > Could not find groovy-all.jar (org.codehaus.groovy:groovy-
> all:2.5.0-rc-1).
> Searched in the following locations:
> https://repo1.maven.org/maven2/org/codehaus/groovy/
> groovy-all/2.5.0-rc-1/groovy-all-2.5.0-rc-1.jar
>
>
> I tried changing the dependency to 'org.codehaus.groovy:groovy-
> all:2.5.0-rc-1@pom' but while in that case dependency resolution phase succeeds
> the build itself then fails with:
>
>
> Cannot infer Groovy class path because no Groovy Jar was found on class
> path: configuration ':compileClasspath'
>
>
> I do not see any of the modules apart from groovy-all itself being added
> to the configuration when running `gradle dependencies --configuration
> compile`:
>
>
> compile - Dependencies for source set 'main'.
> \--- org.codehaus.groovy:groovy-all:2.5.0-rc-1
>
>
> Am I doing something wrong or is the way forward not using groovy-all
> anymore and explicitly depending on only the used modules?
>
> Cheers,
> Marcin
>
> On Mon, Apr 9, 2018 at 7:07 AM, Paul King <pa...@apache.org> wrote:
>
>> Dear community,
>>
>> The Apache Groovy team is pleased to announce version 2.5.0-rc-1 of
>> Apache Groovy.
>> Apache Groovy is a multi-faceted programming language for the JVM.
>> Further details can be found at the http://groovy.apache.org website.
>>
>> This is a pre-release of a new version of Groovy.
>> We greatly appreciate any feedback you can give us when using this
>> version.
>>
>> This release includes 18 bug fixes/improvements as outlined in the
>> changelog:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>> ctId=12318123&version=12342817
>>
>> Sources, convenience binaries, downloadable documentation and an SDK
>> bundle can be found at: http://www.groovy-lang.org/download.html
>> We recommend you verify your installation using the information on that
>> page.
>>
>> Jars are also available within the major binary repositories.
>>
>> We welcome your help and feedback and in particular want
>> to thank everyone who contributed to this release.
>>
>> For more information on how to report problems, and to get involved,
>> visit the project website at https://groovy.apache.org/
>>
>> Best regards,
>>
>> The Apache Groovy team.
>>
>
>
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by Marcin Erdmann <ma...@proxerd.pl>.
Paul,
I'm having a go at giving this release a spin by updating Geb's build to
use it but unfortunately I'm not having any luck with trying to use the
groovy-all artifact. I understand from the earlier thread about updates to
the build on the dev list that the jar for that artifact is not published
and it's supposed to just be a dependency only aritfact which will be
useful for resolving all of Groovy's modules.
To quote you:
> The idea (once finished) is that you can still depend on a groovy-all dependency
via Maven or Gradle and you'll automatically get the multiple required
equivalent jars of the current single groovy-all jar.
Unfortunately this is not the case. Given a simple build like:
plugins {
id 'groovy'
}
repositories {
mavenCentral()
}
dependencies {
compile 'org.codehaus.groovy:groovy-all:2.5.0-rc-1'
}
and an empty Groovy class in the main source set when running `gradle
build` I'm getting:
Could not resolve all dependencies for configuration ':compileClasspath'.
> Could not find groovy-all.jar (org.codehaus.groovy:groovy-all:2.5.0-rc-1).
Searched in the following locations:
https://repo1.maven.org/maven2/org/codehaus/groovy/groovy-all/2.5.0-rc-1/groovy-all-2.5.0-rc-1.jar
I tried changing the dependency to '
org.codehaus.groovy:groovy-all:2.5.0-rc-1@pom' but while in that case
dependency resolution phase succeeds the build itself then fails with:
Cannot infer Groovy class path because no Groovy Jar was found on class
path: configuration ':compileClasspath'
I do not see any of the modules apart from groovy-all itself being added to
the configuration when running `gradle dependencies --configuration
compile`:
compile - Dependencies for source set 'main'.
\--- org.codehaus.groovy:groovy-all:2.5.0-rc-1
Am I doing something wrong or is the way forward not using groovy-all
anymore and explicitly depending on only the used modules?
Cheers,
Marcin
On Mon, Apr 9, 2018 at 7:07 AM, Paul King <pa...@apache.org> wrote:
> Dear community,
>
> The Apache Groovy team is pleased to announce version 2.5.0-rc-1 of
> Apache Groovy.
> Apache Groovy is a multi-faceted programming language for the JVM.
> Further details can be found at the http://groovy.apache.org website.
>
> This is a pre-release of a new version of Groovy.
> We greatly appreciate any feedback you can give us when using this version.
>
> This release includes 18 bug fixes/improvements as outlined in the
> changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12318123&version=12342817
>
> Sources, convenience binaries, downloadable documentation and an SDK
> bundle can be found at: http://www.groovy-lang.org/download.html
> We recommend you verify your installation using the information on that
> page.
>
> Jars are also available within the major binary repositories.
>
> We welcome your help and feedback and in particular want
> to thank everyone who contributed to this release.
>
> For more information on how to report problems, and to get involved,
> visit the project website at https://groovy.apache.org/
>
> Best regards,
>
> The Apache Groovy team.
>
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by Cédric Champeau <ce...@gmail.com>.
Thanks, I indeed missed this page.
2018-04-09 11:50 GMT+02:00 Paul King <pa...@asert.com.au>:
> We have the "by hand" release note summary (though I observe that it needs
> further updates):
>
> http://groovy-lang.org/releasenotes/groovy-2.5.html
>
> We can certainly also list the aggregate Jira issues (but with over 250
> issues it is a little hard to understand at a glance):
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20GROOVY%20AND%
> 20fixVersion%20in%20%282.5.0-alpha-1%2C%202.5.0-beta-1%2C%
> 202.5.0-beta-2%2C%202.5.0-beta-3%2C%202.5.0-rc-1%29
>
> I couldn't see an easy way to produce the "release note" format using
> multiple versions but if someone can let me know if that can be done, we
> can add that instead.
>
> Cheers, Paul.
>
> On Mon, Apr 9, 2018 at 5:20 PM, Cédric Champeau <cedric.champeau@gmail.com
> > wrote:
>
>> Hi Paul,
>>
>> Thanks for making this release. It would be nice to have _cummulative_
>> change log/release notes since 2.4. As they are now, the notes are pretty
>> useless as it doesn't indicate what changes from the last major release.
>>
>> WDYT?
>>
>> 2018-04-09 8:07 GMT+02:00 Paul King <pa...@apache.org>:
>>
>>> Dear community,
>>>
>>> The Apache Groovy team is pleased to announce version 2.5.0-rc-1 of
>>> Apache Groovy.
>>> Apache Groovy is a multi-faceted programming language for the JVM.
>>> Further details can be found at the http://groovy.apache.org website.
>>>
>>> This is a pre-release of a new version of Groovy.
>>> We greatly appreciate any feedback you can give us when using this
>>> version.
>>>
>>> This release includes 18 bug fixes/improvements as outlined in the
>>> changelog:
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>>> ctId=12318123&version=12342817
>>>
>>> Sources, convenience binaries, downloadable documentation and an SDK
>>> bundle can be found at: http://www.groovy-lang.org/download.html
>>> We recommend you verify your installation using the information on that
>>> page.
>>>
>>> Jars are also available within the major binary repositories.
>>>
>>> We welcome your help and feedback and in particular want
>>> to thank everyone who contributed to this release.
>>>
>>> For more information on how to report problems, and to get involved,
>>> visit the project website at https://groovy.apache.org/
>>>
>>> Best regards,
>>>
>>> The Apache Groovy team.
>>>
>>
>>
>
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by Cédric Champeau <ce...@gmail.com>.
Thanks, I indeed missed this page.
2018-04-09 11:50 GMT+02:00 Paul King <pa...@asert.com.au>:
> We have the "by hand" release note summary (though I observe that it needs
> further updates):
>
> http://groovy-lang.org/releasenotes/groovy-2.5.html
>
> We can certainly also list the aggregate Jira issues (but with over 250
> issues it is a little hard to understand at a glance):
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20GROOVY%20AND%
> 20fixVersion%20in%20%282.5.0-alpha-1%2C%202.5.0-beta-1%2C%
> 202.5.0-beta-2%2C%202.5.0-beta-3%2C%202.5.0-rc-1%29
>
> I couldn't see an easy way to produce the "release note" format using
> multiple versions but if someone can let me know if that can be done, we
> can add that instead.
>
> Cheers, Paul.
>
> On Mon, Apr 9, 2018 at 5:20 PM, Cédric Champeau <cedric.champeau@gmail.com
> > wrote:
>
>> Hi Paul,
>>
>> Thanks for making this release. It would be nice to have _cummulative_
>> change log/release notes since 2.4. As they are now, the notes are pretty
>> useless as it doesn't indicate what changes from the last major release.
>>
>> WDYT?
>>
>> 2018-04-09 8:07 GMT+02:00 Paul King <pa...@apache.org>:
>>
>>> Dear community,
>>>
>>> The Apache Groovy team is pleased to announce version 2.5.0-rc-1 of
>>> Apache Groovy.
>>> Apache Groovy is a multi-faceted programming language for the JVM.
>>> Further details can be found at the http://groovy.apache.org website.
>>>
>>> This is a pre-release of a new version of Groovy.
>>> We greatly appreciate any feedback you can give us when using this
>>> version.
>>>
>>> This release includes 18 bug fixes/improvements as outlined in the
>>> changelog:
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>>> ctId=12318123&version=12342817
>>>
>>> Sources, convenience binaries, downloadable documentation and an SDK
>>> bundle can be found at: http://www.groovy-lang.org/download.html
>>> We recommend you verify your installation using the information on that
>>> page.
>>>
>>> Jars are also available within the major binary repositories.
>>>
>>> We welcome your help and feedback and in particular want
>>> to thank everyone who contributed to this release.
>>>
>>> For more information on how to report problems, and to get involved,
>>> visit the project website at https://groovy.apache.org/
>>>
>>> Best regards,
>>>
>>> The Apache Groovy team.
>>>
>>
>>
>
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by Paul King <pa...@asert.com.au>.
We have the "by hand" release note summary (though I observe that it needs
further updates):
http://groovy-lang.org/releasenotes/groovy-2.5.html
We can certainly also list the aggregate Jira issues (but with over 250
issues it is a little hard to understand at a glance):
https://issues.apache.org/jira/issues/?jql=project%20%3D%20GROOVY%20AND%20fixVersion%20in%20%282.5.0-alpha-1%2C%202.5.0-beta-1%2C%202.5.0-beta-2%2C%202.5.0-beta-3%2C%202.5.0-rc-1%29
I couldn't see an easy way to produce the "release note" format using
multiple versions but if someone can let me know if that can be done, we
can add that instead.
Cheers, Paul.
On Mon, Apr 9, 2018 at 5:20 PM, Cédric Champeau <ce...@gmail.com>
wrote:
> Hi Paul,
>
> Thanks for making this release. It would be nice to have _cummulative_
> change log/release notes since 2.4. As they are now, the notes are pretty
> useless as it doesn't indicate what changes from the last major release.
>
> WDYT?
>
> 2018-04-09 8:07 GMT+02:00 Paul King <pa...@apache.org>:
>
>> Dear community,
>>
>> The Apache Groovy team is pleased to announce version 2.5.0-rc-1 of
>> Apache Groovy.
>> Apache Groovy is a multi-faceted programming language for the JVM.
>> Further details can be found at the http://groovy.apache.org website.
>>
>> This is a pre-release of a new version of Groovy.
>> We greatly appreciate any feedback you can give us when using this
>> version.
>>
>> This release includes 18 bug fixes/improvements as outlined in the
>> changelog:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>> ctId=12318123&version=12342817
>>
>> Sources, convenience binaries, downloadable documentation and an SDK
>> bundle can be found at: http://www.groovy-lang.org/download.html
>> We recommend you verify your installation using the information on that
>> page.
>>
>> Jars are also available within the major binary repositories.
>>
>> We welcome your help and feedback and in particular want
>> to thank everyone who contributed to this release.
>>
>> For more information on how to report problems, and to get involved,
>> visit the project website at https://groovy.apache.org/
>>
>> Best regards,
>>
>> The Apache Groovy team.
>>
>
>
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by Paul King <pa...@asert.com.au>.
We have the "by hand" release note summary (though I observe that it needs
further updates):
http://groovy-lang.org/releasenotes/groovy-2.5.html
We can certainly also list the aggregate Jira issues (but with over 250
issues it is a little hard to understand at a glance):
https://issues.apache.org/jira/issues/?jql=project%20%3D%20GROOVY%20AND%20fixVersion%20in%20%282.5.0-alpha-1%2C%202.5.0-beta-1%2C%202.5.0-beta-2%2C%202.5.0-beta-3%2C%202.5.0-rc-1%29
I couldn't see an easy way to produce the "release note" format using
multiple versions but if someone can let me know if that can be done, we
can add that instead.
Cheers, Paul.
On Mon, Apr 9, 2018 at 5:20 PM, Cédric Champeau <ce...@gmail.com>
wrote:
> Hi Paul,
>
> Thanks for making this release. It would be nice to have _cummulative_
> change log/release notes since 2.4. As they are now, the notes are pretty
> useless as it doesn't indicate what changes from the last major release.
>
> WDYT?
>
> 2018-04-09 8:07 GMT+02:00 Paul King <pa...@apache.org>:
>
>> Dear community,
>>
>> The Apache Groovy team is pleased to announce version 2.5.0-rc-1 of
>> Apache Groovy.
>> Apache Groovy is a multi-faceted programming language for the JVM.
>> Further details can be found at the http://groovy.apache.org website.
>>
>> This is a pre-release of a new version of Groovy.
>> We greatly appreciate any feedback you can give us when using this
>> version.
>>
>> This release includes 18 bug fixes/improvements as outlined in the
>> changelog:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>> ctId=12318123&version=12342817
>>
>> Sources, convenience binaries, downloadable documentation and an SDK
>> bundle can be found at: http://www.groovy-lang.org/download.html
>> We recommend you verify your installation using the information on that
>> page.
>>
>> Jars are also available within the major binary repositories.
>>
>> We welcome your help and feedback and in particular want
>> to thank everyone who contributed to this release.
>>
>> For more information on how to report problems, and to get involved,
>> visit the project website at https://groovy.apache.org/
>>
>> Best regards,
>>
>> The Apache Groovy team.
>>
>
>
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by Cédric Champeau <ce...@gmail.com>.
Hi Paul,
Thanks for making this release. It would be nice to have _cummulative_
change log/release notes since 2.4. As they are now, the notes are pretty
useless as it doesn't indicate what changes from the last major release.
WDYT?
2018-04-09 8:07 GMT+02:00 Paul King <pa...@apache.org>:
> Dear community,
>
> The Apache Groovy team is pleased to announce version 2.5.0-rc-1 of
> Apache Groovy.
> Apache Groovy is a multi-faceted programming language for the JVM.
> Further details can be found at the http://groovy.apache.org website.
>
> This is a pre-release of a new version of Groovy.
> We greatly appreciate any feedback you can give us when using this version.
>
> This release includes 18 bug fixes/improvements as outlined in the
> changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12318123&version=12342817
>
> Sources, convenience binaries, downloadable documentation and an SDK
> bundle can be found at: http://www.groovy-lang.org/download.html
> We recommend you verify your installation using the information on that
> page.
>
> Jars are also available within the major binary repositories.
>
> We welcome your help and feedback and in particular want
> to thank everyone who contributed to this release.
>
> For more information on how to report problems, and to get involved,
> visit the project website at https://groovy.apache.org/
>
> Best regards,
>
> The Apache Groovy team.
>
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by Cédric Champeau <ce...@gmail.com>.
Hi Paul,
Thanks for making this release. It would be nice to have _cummulative_
change log/release notes since 2.4. As they are now, the notes are pretty
useless as it doesn't indicate what changes from the last major release.
WDYT?
2018-04-09 8:07 GMT+02:00 Paul King <pa...@apache.org>:
> Dear community,
>
> The Apache Groovy team is pleased to announce version 2.5.0-rc-1 of
> Apache Groovy.
> Apache Groovy is a multi-faceted programming language for the JVM.
> Further details can be found at the http://groovy.apache.org website.
>
> This is a pre-release of a new version of Groovy.
> We greatly appreciate any feedback you can give us when using this version.
>
> This release includes 18 bug fixes/improvements as outlined in the
> changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12318123&version=12342817
>
> Sources, convenience binaries, downloadable documentation and an SDK
> bundle can be found at: http://www.groovy-lang.org/download.html
> We recommend you verify your installation using the information on that
> page.
>
> Jars are also available within the major binary repositories.
>
> We welcome your help and feedback and in particular want
> to thank everyone who contributed to this release.
>
> For more information on how to report problems, and to get involved,
> visit the project website at https://groovy.apache.org/
>
> Best regards,
>
> The Apache Groovy team.
>
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by Marcin Erdmann <ma...@proxerd.pl>.
Paul,
I'm having a go at giving this release a spin by updating Geb's build to
use it but unfortunately I'm not having any luck with trying to use the
groovy-all artifact. I understand from the earlier thread about updates to
the build on the dev list that the jar for that artifact is not published
and it's supposed to just be a dependency only aritfact which will be
useful for resolving all of Groovy's modules.
To quote you:
> The idea (once finished) is that you can still depend on a groovy-all dependency
via Maven or Gradle and you'll automatically get the multiple required
equivalent jars of the current single groovy-all jar.
Unfortunately this is not the case. Given a simple build like:
plugins {
id 'groovy'
}
repositories {
mavenCentral()
}
dependencies {
compile 'org.codehaus.groovy:groovy-all:2.5.0-rc-1'
}
and an empty Groovy class in the main source set when running `gradle
build` I'm getting:
Could not resolve all dependencies for configuration ':compileClasspath'.
> Could not find groovy-all.jar (org.codehaus.groovy:groovy-all:2.5.0-rc-1).
Searched in the following locations:
https://repo1.maven.org/maven2/org/codehaus/groovy/groovy-all/2.5.0-rc-1/groovy-all-2.5.0-rc-1.jar
I tried changing the dependency to '
org.codehaus.groovy:groovy-all:2.5.0-rc-1@pom' but while in that case
dependency resolution phase succeeds the build itself then fails with:
Cannot infer Groovy class path because no Groovy Jar was found on class
path: configuration ':compileClasspath'
I do not see any of the modules apart from groovy-all itself being added to
the configuration when running `gradle dependencies --configuration
compile`:
compile - Dependencies for source set 'main'.
\--- org.codehaus.groovy:groovy-all:2.5.0-rc-1
Am I doing something wrong or is the way forward not using groovy-all
anymore and explicitly depending on only the used modules?
Cheers,
Marcin
On Mon, Apr 9, 2018 at 7:07 AM, Paul King <pa...@apache.org> wrote:
> Dear community,
>
> The Apache Groovy team is pleased to announce version 2.5.0-rc-1 of
> Apache Groovy.
> Apache Groovy is a multi-faceted programming language for the JVM.
> Further details can be found at the http://groovy.apache.org website.
>
> This is a pre-release of a new version of Groovy.
> We greatly appreciate any feedback you can give us when using this version.
>
> This release includes 18 bug fixes/improvements as outlined in the
> changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12318123&version=12342817
>
> Sources, convenience binaries, downloadable documentation and an SDK
> bundle can be found at: http://www.groovy-lang.org/download.html
> We recommend you verify your installation using the information on that
> page.
>
> Jars are also available within the major binary repositories.
>
> We welcome your help and feedback and in particular want
> to thank everyone who contributed to this release.
>
> For more information on how to report problems, and to get involved,
> visit the project website at https://groovy.apache.org/
>
> Best regards,
>
> The Apache Groovy team.
>
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by Jochen Theodorou <bl...@gmx.org>.
On 09.04.2018 16:50, Daniel.Sun wrote:
> Hi Jochen,
>
> Do you mean some classes' groovydoc files are missing in the 2.5.0 rc-1
> release?
yes, the list of classes to choose from in the html, seems to be much
shorter
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by "Daniel.Sun" <su...@apache.org>.
Hi Jochen,
Do you mean some classes' groovydoc files are missing in the 2.5.0 rc-1
release?
Cheers,
Daniel.Sun
--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by Jochen Theodorou <bl...@gmx.org>.
Am 09.04.2018 um 14:16 schrieb Daniel.Sun:
> Nice!
>
> P.S. I plan to release 3.0.0 alpha 2 this week :-)
can you guys btw check groovydoc? I think there are some classes missing
compared to 2.4.x
bye Jochen
Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-1 released
Posted by "Daniel.Sun" <su...@apache.org>.
Nice!
P.S. I plan to release 3.0.0 alpha 2 this week :-)
Cheers,
Daniel.Sun
--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html