On 06.03.2018 16:51, Russel Winder wrote:
Hi,
Currently the GPars build system assumes one and only one version of
Groovy. Currently we have four, most likely incompatible, versions of
Groovy on the boil: 2.4.14, 2.5.0-beta-3, 2.6.0-alpha-3, 3.0.0-alpha-1.
Should GPars be build specially for eac
I've double checked this and the compilation fails also locally using
`2.5.0-SNAPSHOT`.
I've managed to compile successfully using `2.5.0-beta-3` instead.
Cheers,
Paolo
On Tue, Mar 6, 2018 at 2:29 PM, Paul King wrote:
> I temporarily set CI_GROOVY_VERSION for that joint build to 2.5.0-beta-3
Thanks to you for this -
Does this mean that GPars will no longer work on JDK1.7 ? What is the minimum
jdk that we require for GPars, please ?
Thx
Jim
> On 6 Mar 2018, at 18:04, Russel Winder wrote:
>
> On Tue, 2018-03-06 at 16:43 +, Kerridge, Jon wrote:
>> Hi,
>
> Hi Jon,
>
>> I am hav
On Tue, 2018-03-06 at 16:43 +, Kerridge, Jon wrote:
> Hi,
Hi Jon,
> I am having the same problems with the JCSP and GroovyJCSP libraries
> as well!
It has been a very long while since I created the JCSP-1.1-rc5 artefact
and put it into Maven Central. I can't remember which Java I used to
bui
Hi,
I am having the same problems with the JCSP and GroovyJCSP libraries as well!
Currently I have compilations for 2.4.14 and 2.5.x
I am then coping with the various versions of Java as well J8, 9 10 and 11
before the end of this year!
Any advice would be gratefully received.
Jon
Profe
Hi,
Currently the GPars build system assumes one and only one version of
Groovy. Currently we have four, most likely incompatible, versions of
Groovy on the boil: 2.4.14, 2.5.0-beta-3, 2.6.0-alpha-3, 3.0.0-alpha-1.
Should GPars be build specially for each version of Groovy?
--
Russel.
=
Is there any reason why implementations of GroovyObject methods which are
injected into Groovy classes are marked with ACC_SYNTHETIC?
This causes all sorts of confusion:
class GroovyClass {}
class JavaClass extends GroovyClass {} // compiles ok
class JavaClass extends GroovyClass implements G
I temporarily set CI_GROOVY_VERSION for that joint build to 2.5.0-beta-3
but it seems to have been set to 2.4.13 regardless. Do you get the same
errors locally as we are seeing on the CI server?
On Tue, Mar 6, 2018 at 10:51 PM, Paolo Di Tommaso wrote:
> The nextflow joint build is failing badly
The nextflow joint build is failing badly with the current snapshot :
http://ci.groovy-lang.org/viewLog.html?buildId=47703&tab=buildResultsDiv&;
buildTypeId=JointBuilds_Nextflow_Groovy25xJointBuild#
It seems it's unable static compiled classes are unable to resolve
extension methods such the ones
I am hoping to do the first RC release of 2.5.0 late this week or next
week. The plan being for a release in time for or during Greach. I still
have a bunch of bugs on my list to be fixed before then, so I can't narrow
it down more than that at this stage. Please work on any changes you want
in for
10 matches
Mail list logo
