-
Notifications
You must be signed in to change notification settings - Fork 29
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
Fix execution of DSpot maven plugin on test example #395
Comments
fix InputConfiguration getRelativePath conversion
the execution of dspot from maven plugin returns this error:
If I execute the plugin from junit test it works. |
I would like to help you, but could please give more information? Like the command line you used. Also, I suggest you to update ( Thank you! |
I merged the changes of the branch with the master.
If you execute the test dspot/dspot-maven/src/test/java/eu/stamp_project/DSpotMojoTest.java from JUnit, it works. |
Okay thank you, I'm gonna have a look ASAP. I think it might come from a wrong classpath or something like this. |
Hi, The problem come from the test runner. It seems that the way that I found the classes to run the test does not work with the maven plugin. I am working on it. |
I just fixed the problem, opened a PR on testrunner project see STAMP-project/test-runner#18 I'm gonna release the new testrunner, and update dependencies of DSpot right after the merge. I'll ping you when it is done. Thank you. |
DSpot depends now on the new test-runner. You will have to rebase with the master branch:
And then, reinstall everything by running I was able to amplify the test-projects using the maven plugin. Cheers! |
it works!! |
fix InputConfiguration getRelativePath conversion
Characteristics
Description
The execution of mvn from dspot/src/test/resources/test-projects doesn't produce the same output of the execution from command line (java -jar target/dspot-LATEST-jar-with-dependencies.jar --example)
Steps to reproduce
Help on issue template
Preview to follow the link or open file .github/ISSUE_DOC.md
The text was updated successfully, but these errors were encountered: