Re: Possible Problem
Looks like the problem is with the compound assignment using an attribute and not related to synchronized. I created issue GROOVY-8648 [1] for this problem. [1] https://issues.apache.org/jira/browse/GROOVY-8648 On Fri, Jun 15, 2018 at 6:59 AM Russel Winder wrote: > I have been tinkering a bit with GPars,mostly as a reaction to JCP 1.1.0 > being > released (to replace my jcsp-1.1-rc-5 artefact). I amusing JDK11 and JDK10 > with Groovy 2.5.0. > > In this example programme: > > > https://github.com/GPars/GPars/blob/master/src/test/groovy/groovyx/gpars/samples/collections/DemoSynchronizedAccountTransfer.groovy > > It seems the synchronized keyword on the function credit line 29 is cause a > problem during compilation: > > Error:Groovyc: ASM reporting processing error for > groovyx.gpars.samples.collections.Account#credit with signature void > credit(int) in DemoSynchronizedAccountTransfer.groovy:29 > > > -- > Russel. > === > Dr Russel Winder t: +44 20 7585 2200 > 41 Buckmaster Roadm: +44 7770 465 077 > London SW11 1EN, UK w: www.russel.org.uk >
Re: module information creation for Groovy 3
- Mail original - > De: "Jochen Theodorou" > À: "dev" > Envoyé: Vendredi 15 Juin 2018 17:38:29 > Objet: Re: module information creation for Groovy 3 > Am 15.06.2018 um 08:58 schrieb Remi Forax: >> Hi, >> moditech provides two different things, >> - if you are an application, you can add the module-info to your >> dependencies, >> from the POV of the VM, it means all your code will be modular so you can use >> jlink to create a minimal docker file >> - you can add module-info to your own jar >> >> The first case is fully valid, i do the same thing but fully automatically >> (doing a static analysis) with pro [1], it's great but only works if you are >> the final application, not a library, >> the second case adds maintenance burden because the module-info doesn't get >> updated when you change the code source or the pom.xml, so you can have the >> pom >> and the module-info disagreeing on the dependency, a package you have just >> added being exported by default exported (instead of been non-exported by >> default), a service being declared in the META-INF but not in the module-info >> etc. >> >> So it means that you have to test your produced jars twice, with the >> classpath >> and with the module-path to catch the regressions you may have introduced by >> not updating the moditech plugin configuration to the changes done in the >> source code. Without modifying the test to run twice, you will get nasty >> surprises :( > > that might be true, but don't I have to do this anyway? And not only > that. I have to test as a system module as well. yes ! > > bye Jochen Rémi
Re: 3.0.0-alpha-3
On Fri, 2018-06-15 at 14:15 -0700, Daniel.Sun wrote: > Hi Russel, > > There are some annoying bugs in 2.5.0, so it is better to release > 3.0.0-beta-3 after 2.5.1 is out. > OK. The 2.5 series is higher priority just now, so I'll wait. The workaround is to remove Groovy 3.0.0 from the Gant build, or just not fiddle with Gant till there is a 3.0.0-alpha-3 release. I, and the world, can cope with the latter. :-) -- Russel. === Dr Russel Winder t: +44 20 7585 2200 41 Buckmaster Roadm: +44 7770 465 077 London SW11 1EN, UK w: www.russel.org.uk signature.asc Description: This is a digitally signed message part
