Le 2016-09-03 18:27, Prince Arora a écrit :
I am not using scala. This happens when i use gradle to build zest but
working fine ./gradlew
Hey,
This must be caused by your local gradle installation being a different
version than the one we use for Zest.
Using ./gradlew enforce that you use the same Gradle version as
everybody working on Zest.
Some changes have been made into Gradle around Scala compilation lately.
I'll have a look at upgrading our build to the latest Gradle.
Long story short, as long as you use ./gradlew everything should build!
:)
Cheers
I have attached patch for ZEST-174 on jira. Please let me know if any
changes or improvements needed.
On Sun, Sep 4, 2016 at 4:54 AM, Niclas Hedhman <[email protected]>
wrote:
Thanks Sandro,
I am awake again, and installing JDK on my Linux box (so much Java dev
on
that one).
The Scala effort in Zest kind of died off, for primarily two reasons I
think.
Firstly, personally I am very disappointed with Scala. It is too
complex
and I think it promotes "cleverness" in code writing, leading to
obscure
code. Reminds me a bit of Perl, that it is possible to write nice
Perl, but
most people don't.
Secondly, since the experiment was done by Rickard, to support two-way
Mixin's and more, Scala has made a couple of major release cycles, and
they
are notorious for breaking compatibility. This makes it difficult to
expense the effort to hook into the language for us, since next
release may
invalidate every single bit and we need to start over (or get stuck).
So, I am a bit ambivalent on how to view future support for Scala.
BUT, I don't think Prince is using Scala per se, it is just showing up
during the regular Zest build.
Cheers
<trim src="few hundred lines"/>
--
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java
