-
Notifications
You must be signed in to change notification settings - Fork 58
gradle and zinc 3.x #44
Comments
Looks like a binary compatibility breakage. The addition of the "fork java method": https://github.com/typesafehub/zinc/blob/master/src/main/scala/com/typesafe/zinc/Setup.scala#L114 @pvlugter Just curious, is 0.3.1 meant to be binary compatible? |
That's a mistake. It should stay compatible. It looks like 0.3.1 final was never released, so could be fixed there. In the future the Java APIs could use a builder pattern and be easier to extend: #40 |
Hey guys, Thanks for the comments. I'm trying to come up with some plan about this issue. Here's the state of things:
Some questions:
Cheers! |
One more question: we use Inputs.create() method: https://github.com/gradle/gradle/blob/master/subprojects/scala/src/main/groovy/org/gradle/api/internal/tasks/scala/jdk6/ZincScalaCompiler.java#L64 Now this method also requires IncOptions instance. Can you point me to some docs/code that I could inspire on when creating the IncOptions? The constructor expects a bunch of parameters that I don't have much clue about :) |
It turns out that there is one more binary compatibility issue that has been not fixed by #55. This time it's related to zinc's version of
Binary compatibility has been broken by 6f74673. |
The issue with IncOptions has been fixed by #59. |
I still get the same exception with zinc 0.3.5.3. Any idea?
This problem seems only to occur when I use gradle with zinc. |
Hey guys,
There seem to be some breaking changes in the zinc api. Here's the error I get from upgrading a sample gradle build to use scala 2.10.3 and zinc 0.3.1-RC1. Can you shed some light on this issue: https://gist.github.com/szczepiq/9601aa06ab4be5d4fe64
Apologize if this is not the right place to raise this question / problem.
Thanks!
The text was updated successfully, but these errors were encountered: