[GRADLE-2548] scalaCompile task is not correctly incremental wrt javaCompile Created: 06/Nov/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Szczepan Faber Assignee: Unassigned
Resolution: Won't Fix Votes: 0


It might not be a huge deal because nobody has reported it yet. I'm about to add an integ test case (ignored) for this scenario. Please look it up in the codebase (Issue annotation).

Steps to reproduce (typing from memory, I might be wrong with some details):

1. use the mixed scala sample project
2. build the project
3. build again, make sure everything is up-to-date
4. change the java source the scala class depends on. For example, add a new method to the interface
5. build the project. Note that javaCompile runs but scalaCompile task is considered up-to-date even though the scala class implements the interface from the java code. The expected result is both: javaCompile and scalaCompile tasks run and the latter fails.

Comment by Adam Murdoch [ 06/Nov/12 ]

Which compiler integration are you using?

Comment by Szczepan Faber [ 07/Nov/12 ]

Good question - I just use the defaults (nothing extra is configured in the build).

The root cause of the problem seems to be that scalaCompile just depends on the javaCompile task, without depending on javaCompile's outputs. However, putting javaCompile outputs on scalaCompile inputs is tricky because both tasks compile stuff to the same directory.

Comment by Peter Niederwieser [ 07/Nov/12 ]

I'm consistently seeing a different behavior. With 1.2 and Ant based Scala compiler, `compileScala` gets run in step 5, but doesn't fail. Only after the next clean build does it fail. With 1.3 (release branch) and Ant based compiler, step 5 fails consistently (as it should). Not sure what to make of this. Used --no-daemon in all my tests.

Comment by Peter Niederwieser [ 07/Nov/12 ]

I take that back, already had the workaround for GRADLE-2549 enabled. I'm now getting the same behavior as Szczepan for all three setups (1.2 with Ant based compiler, 1.3 with Ant based compiler, 1.3 with Zinc based compiler).

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:24:57 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.