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

NiCad 4 reports absolute paths, causing problem in parsing its results #61

Open
dmazinanian opened this issue Oct 17, 2017 · 0 comments
Assignees

Comments

@dmazinanian
Copy link
Collaborator

I recently run NiCad 4 on a project and tried to import the results into JDeodorant for refactoring, and ran into ICompilationUnitNotFound exceptions.

Apparently this is because NiCad 3 reported absolute paths for files containing clones (with which we tested the implementation of the clone output parsers), while NiCad 4 returns relative paths. Unfortunately, in the generated XML files from NiCad 4 it still reads processor="nicad3", but with a little tweaking in the code we should be able to support both versions at the same time...

@dmazinanian dmazinanian self-assigned this Oct 17, 2017
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

No branches or pull requests

1 participant