jimkont
commented
3 years ago Thanks a lot for your contribution @mgns !
The whitespace changes makes it hard to review this change, I trust this is good and would be happy to merge as is but would make git history better to read if it would be easy to separate the whitespace changes with the new features.
one possible way could be the following, take the latest master and run the whole project with the same tool you used to create the whitespace changes and make a merge request with that alone. Once we merge that, rerun the same tool again on your branch and then rebase / merge on latest master. We can do a squash merge in the last step to make the current changes visible.
If this approach doesn't work we could merge it as is, wdyt?
mgns
In this branch I implemented the possibility to generate test case descriptions from an ontology. I switched from apache command line parser to picocli, bumped dependencies and (that might be problematic) did some code reformat (in an attempt to clean-up the code I used the Intellij Reformat Code feature).
Description
Almost every file has been touched in this branch, as I run code reformat on the project, which changed indentation of lines (quite a lot whitespace-only changes) and order of imports. Let me know, how we could handle this.
Following changes have been made:
Fixes (partly due to dependency updates):
Motivation and Context
Generation of test case description needed for a customer.
How Has This Been Tested?
The command line args for validate work as before, a new subcommand has been introduced for the feature. shell scripts have been adapted accordingly, so there is no change.
Screenshots (if appropriate):
Types of changes
Checklist: