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

Fixed absolute path calculation for workspace resources #148

Merged
merged 1 commit into from
Oct 15, 2018

Conversation

Boereck
Copy link
Contributor

@Boereck Boereck commented Oct 15, 2018

  • Previously it was assumed that projects are physically stored below
    the workspace directory. When projects are located e.g. in a git
    repository and imported into the workspace this assumption does not
    hold. This was fixed with a proper lookup.

  • Changed API of the convertToAbsolutePath method to take a string
    instead of a file, since all callers had to create a file from a
    string anyway.

* Previously it was assumed that projects are physically stored below
  the workspace directory. When projects are located e.g. in a git
  repository and imported into the workspace this assumption does not
  hold. This was fixed with a proper lookup.

* Changed API of the convertToAbsolutePath method to take a string
  instead of a file, since all callers had to create a file from a
  string anyway.

Signed-off-by: Max Bureck <[email protected]>
@mickaelistria mickaelistria merged commit 37fff49 into eclipse-corrosion:master Oct 15, 2018
Boereck added a commit to Boereck/corrosion that referenced this pull request Oct 15, 2018
convertToAbsolutePath is now taking path directly in relative path case
instead of converting file back to a relative path string.

Signed-off-by: Max Bureck <[email protected]>
mickaelistria pushed a commit that referenced this pull request Oct 15, 2018
convertToAbsolutePath is now taking path directly in relative path case
instead of converting file back to a relative path string.

Signed-off-by: Max Bureck <[email protected]>
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.

2 participants