-
Notifications
You must be signed in to change notification settings - Fork 939
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incremental compilation recompiles all the files every time #923
Comments
Hi, I believe the culprit is first few lines line:
Not how first set of files uses fully qualified paths and the other doesn't. Are you running using some uncommon filesystem setup (e.g. are symlinks or network file system involved)? |
It is on the freaking win7, so no symlinks I suppose... |
that was it!: Now how do we go about it - I dont want everybody to hate me for changing the project directory structure. And this is clearly an oversight in the guts of sbt... :) |
it's an oversight because we probably should always convert all paths to canonical from. @harrah, can you confirm if this is true? However, you can easily work-around your problem by saying |
Thank you Grzegorz - this worked!:) You dont need the |
We do not convert relative paths because we don't have the information about the base directory. The current working directory is not the right one to use because that can change. At best, we can generate an error or provide some wrapper macro |
What about generating a runtime error whenever we see relative file like in the example above? |
Yeah, that's what I meant by generating an error. The problem is you have to insert that check a bunch of places. Since this particular failure mode seems somewhat common, putting them in for sources might be a good start. |
…rce files. Fixes #923. Review by @gkossakowski
…rce files. Fixes #923. Review by @gkossakowski Conflicts: sbt/src/sbt-test/source-dependencies/relative-source-error/test
…. Ref #923. Conflicts: sbt/src/sbt-test/source-dependencies/relative-source-error/test
This is what I do:
No. 3 recompiles all the sources, even though I haven't touched the files.
I am on scala 2.10.2, sbt 0.13.0 (but it happens on the 0.12.4 and 0.13.Beta2 too)
See my build.sbt:
And this is the sbt log when I do the step 3 (so the sources are fully compiled by this time):
The text was updated successfully, but these errors were encountered: