Re: org.apache.zest.io an org.apache.zest.functional

Most (all?) Iterables in Core was replaced before. For exceptions, first of all, I think almost all exceptions in Zest are RuntimeExceptions and should not cause much problem. For IOException and such, I typically wrap in UndeclaredThrowableException if the cause/use is unclear and catch that in

Jenkins build is back to normal : Zest(JavaEdition)-develop-java9-check #33

See

Build failed in Jenkins: Zest(JavaEdition)-develop-java9-check #32

See Changes: [paulmerlin] build: upgrade Gradle to 3.2.1 [paulmerlin] build: use mavenCentral() instead of jcenter() in buildSrc [paulmerlin] build: set task desc & group for performance tests [paulmerlin]

Re: org.apache.zest.io an org.apache.zest.functional

Niclas Hedhman a écrit : > These two modules and their classes are largely replaced with the Java 8 > Stream API already. I will try to get rid of the completely, as the code > with Input/Output/Sender/Receiver is significantly more verbose and more > complex than equivalent code using the Stream

Re: Name finding... Again..

Niclas Hedhman a écrit : > Ok, so we need to figure out if a name is feasible before tossing it into > the ring of names. > > Starting over, I would like to propose the following two names, that seem > eligible; > > * Apache Aardworx > (114 hits, but effectively only one Facebook profile) I