groovy-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nelson, Erick" <>
Subject Re: What's the status of the Gpars library ?
Date Sun, 15 Oct 2017 16:06:55 GMT
I¡¯m curious, how is gpars better than Java  concurrency. I do most of my  development with
Greclipse, which doesn¡¯t come with G pars so ive never really tried it. Is there some link
out there that I can check out that compares both?

Sent from my iPhone

On Oct 15, 2017, at 5:02 AM, David Dawson <<>>

Sounds like you have a volunteer Russel ;-)

  Original Message
Sent: 14 October 2017 20:15
Reply to:<>
Subject: Re: What's the status of the Gpars library ?

On 2017-10-14 13:31, David Dawson wrote:

I recently went through the process of artifact deploy/ promotion to maven
central using a self hosted OSS artifactory and bintray.  Its a process
with a few manual steps, which could be automated (except for the last
promotion to central I think) but it seems low impact enough not to bother.

I'd be happy to replicate that for gpars if that would be helpful?

It sounds good, however, there is also a way to completely automatically
release to Maven Central directly from Travis with Git commit messages
such as "[#DO_RELEASE]" or "[#DO_RELEASE][#2.0.0]". I've been using it
to release my projects in the Continuous Delivery process for a year or
so (and in general it works :) ).

Sample configuration:
(in fact just a few lines are required for the release process, others
are to satisfy Maven Central requirements, e.g. generated pom.xml elements).

I could also provide the release support as a backup plan.

Nevertheless, those are not the only possible way in the Gradle universe.


On 14 October 2017 at 08:54, Russel Winder <<>>

On Fri, 2017-10-13 at 21:07 +0200, Christian Sperandio wrote:

I want to learn more about concurrency programming in Groovy and I¡¯ve
the Gpars library.
But in the maven repository, the last version dates on 2014.
Is this project live anymore ? Or this library is so stable and it
need more changes.

GPars project is far from dead. However it is suffering from a lack of
programmers and documentors actively working on it.

The GPars 1.X series is basically done and in "not really being maintained"
mode, though a last release is required. This version of GPars pre-dates
uses tools and techniques of implementation that are now out of date, and
has no future as an implementation of concurrency.

The GPars 2.X series will rely on JDK8 or later. However, I have not been
to get it ready for release (long, probably boring, story) and no-one else
seems interested enough in GPars getting a new release to join in and
help. I
am hoping to be able to get back to this is 2018, making a JDK8 and JDK9
compatible version, i.e. plan on GPars being a module.

A core question is how to get a release onto Maven Central, possibly via
Bintray. The observant will notice there hasn't been a GPars release since
demise of Cohehaus ¨C the single biggest reason being no-one associated with
GPars has had the time/inclination to find out how to get it done.

Schalk Cronj¨¦ and myself have had a couple of goes at this, but run out of
time, and Bintray has moved on since then. So if someone can step up to
with the release process, a final 1.X release can be made and the first 2.0
one as well.

Help with the documentation as well as the implementation and release would
also be welcome, the 1.X ¡ú 2.X change will need quite a lot of work to get
documentation up to scratch. There is nothing worse than a great library
crap documentation.

In the end GPars is a volunteer project with no paid support, the people
like and/or use it are most welcome to give back by helping out.

Dr Russel Winder      t: +44 20 7585 2200
41 Buckmaster Road    m: +44 7770 465 077
London SW11 1EN, UK   w:<>

- Working code is not enough
View raw message