Skip to content
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

consistently canonicalize paths #47

Merged
merged 1 commit into from
May 12, 2016
Merged

consistently canonicalize paths #47

merged 1 commit into from
May 12, 2016

Conversation

mberndt123
Copy link
Contributor

Fixes this issue:
sbt/sbt-jshint#33

@huntc huntc merged commit ce1abdd into sbt:master May 12, 2016
@iadcode
Copy link

iadcode commented Aug 30, 2016

Is there a particular reason why .getCanonicalPath() is used instead of .getAbsolutePath()?

I have a subproject referenced via a symbolic link outside of the base directory of the main project. .getCanonicalPath() is resolving the symbolic link in a UNIX environment. This results in errors when attempting to map source files to their outputs, since the source files are not relative to the base directory.

@mberndt123
Copy link
Contributor Author

mberndt123 commented Aug 30, 2016

I don't remember the details about this bug fix since it's been a few months since then. I don't think there was any particular reason. I guess you should create an example project to reproduce the issue and create a separate bug report though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants