Fix bug for absolute paths from parser tokens. #85
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While adding a new language, generating reports crashed on not finding the submitted files, even though it had parsed them successfully in the analysis phase.
After several hours digging, I found that the cause was that Jplag assumes that tokens contain relative paths while generating reports. That doesn't hold for my parser. Instead, it did:
which then outputs paths like
fpath = /path/to/exercise1/path/to/exercise1/stud1/x.y
That of course has no hope of ever finding the file, so I patched the Submission code to deal with absolute paths from tokens.