The analyzer works only if the projects that are being analyzed are stored under the same directory as our analyzer project. For example, if you have eclipse-workspace/Build-System-Inference, you should have the project being analyzed, for example commons-math, stored in eclipse-workspace/commons-math. It's a rather hacky solution at the moment. We need better design to make this more flexible.
Right now, the analyzer requires user to input:
1)build file name and have the build file inside our project
2)the name of the file that stores output
3)the name of the project that needs to be analyzed
It would be better if we can automatically get the 1) build file, and 2).properties file from the project.
Regarding the BuildAnalyzer Interface:
Right now it has 9 methods that returns strings. We can either keep this patter, or set all return types to void and directly write the output to our output file. Need more comments on this.
Please comment under this thread so we can finalize ideas.
The analyzer works only if the projects that are being analyzed are stored under the same directory as our analyzer project. For example, if you have eclipse-workspace/Build-System-Inference, you should have the project being analyzed, for example commons-math, stored in eclipse-workspace/commons-math. It's a rather hacky solution at the moment. We need better design to make this more flexible.
Right now, the analyzer requires user to input: 1)build file name and have the build file inside our project 2)the name of the file that stores output 3)the name of the project that needs to be analyzed It would be better if we can automatically get the 1) build file, and 2).properties file from the project.
Regarding the BuildAnalyzer Interface: Right now it has 9 methods that returns strings. We can either keep this patter, or set all return types to void and directly write the output to our output file. Need more comments on this.
Please comment under this thread so we can finalize ideas.