Closed jacosro closed 3 years ago
Suggestions:
-i
to be repeated, and even rename it to -c
for "classpath" instead of -i
for "include" or "input". Make it work similarly to the Java classpath: load all those folders into the Javaparser type resolver.file#line:var
.Underlying elements to get a working CLI:
sdg
submodulesdg-cli
submoduleMethodDeclarationSolver
.SlicingCriterion
that works with the SDG.Slice#getAst()
so that it can return NodeList<CompilationUnit>
.ACTUAL_IN
to all ACTUAL_OUT
in unresolved method calls.See #32.
Add support for command line interaction.
Todo list:
cli
Slicer
Graph
(optional)Two entrypoints needed:
Slicer
Entrypoint:
Slicer
class (cli
module) Commands:-f <file>
: the Java file for which the slicing will be performed-v <variable>
: the name of the variable to take as slicing criterion-l <line>
: the line in which the variable is to take as slicing criterion-i <directory>
(Optional): directory of Java files to take into account for the analysis (this should look for Java files in subdirectories too)-o <directory>
(Optional): directory in which output files will be stored (current directory by default)-d, --debug
(Optional): Outputs debug files and prints debug informationGraph (Optional)
Entrypoint:
Graph
class (cli
module) Options:cfg|pdg|sdg
: the graph to build-m <method>
: The method to analyse (only forcfg
orpdg
options)-d, --debug
(Optional): Outputs debug files and prints debug information-i <directory>
: The directory of Java files to be processed (only forsdg
option)-o <directory>
: Directory in which output files will be stored@cargaji