Vavr: Please release vavr 1.0.0-alpha built with Java 8 targetCompatibility

[yvolk]

@danieldietrich I'm very excited that I can introduce Vavr 1.0.0 (alpha) library to my colleagues starting at least with Try only - as a first step of "step-by-step" Functional programming education :-)
Unfortunately, existing "1.0.0-alpha-1" artifact is built at Java 11 compatibility level, which prevents the artifact's usage in our Java 8 project. Although _current_ source code in "v1.0.0" branch _is_ already fixed to be Java 8 compatible.

Please, publish next alpha release based on current source code, so we could start using it! (Inserting source code of Vavr 1.0.0 directly in our custom project looks ugly and I'm afraid that my attempt to introduce FP may be rejected based on this only...)

[danieldietrich]

Thx! I will prepare an alpha-2 release this day.

[danieldietrich]

Hi, just wanted to give you an update.

I polished the alpha-2 a bit and wanted to release it. However, I'm stuck with the net.researchgate.release plugin for Gradle. Version 2.7.0 does not allow me to perform a release based on a non-master git branch. It seems to be solved in 2.8.0, but it isn't released, yet.

See also researchgate/gradle-release#195

[yvolk]

@danieldietrich Thank you for update. Very strange restriction...
As a workaround, you could try this: fork your own repository and make vavr 1.0 be in a master branch of _that_ repository. And release from _that_ repository?!

...Anyway, we are not in a hurry :-)
Happy New Year!

[danieldietrich]

Finally done.

It was already released on Bintray JCenter but I had several issues syncing the release to Maven Central. So I changed the Gradle build and release now directly to Sonatype.

For the users, this is transparent, because Maven Central is automatically synced to JCenter.

Note: It may take a few hours until vavr-1.0.0-alpha-2 is visible on Maven Central. The release notes will follow today here on Github.

[yvolk]

Thank you, @danieldietrich
I was able to use the new artifact, but it appeared that its artifactId changed since alpha-1
The new artifactId is "vavr", not "vavr-control" as previously. Please correct README.md

[danieldietrich]

@yvolk Great to hear!

Yes, the name change was intended and has to do with the rollback of Jigsaw modules.

Vavr 1.0 will stay to be one module for

• io.vavr
• io.vavr.collection
• io.vavr.concurrent
• io.vavr.control

I will update the README. Thanks for the hint!