|
Michael V. Scovetta |
||||||||||||||
Yasca > Documentation > How to Use Yasca (A Quick Introduction)I noticed a search engine referral that asked How to use Yasca. Maybe it seems obvious to me only because I've been using it for over a year, so here are a few examples of what you'll most likely want to do with it:Scenario #1 Simple PHP ProjectSuppose you have a PHP project with source code in c:\work\myproject\src\. You could run: yasca c:\work\myproject\src
The output is placed in a folder called Yasca on your desktop. Alternatively, since you know you dont have any Java, C, or C++ files there, you can exclude certain plugins that definitely wont find anything to scan. (This is optional; if you ignore this, execution time will just take a few seconds longer.) yasca -px FindBugs,Antic,JLint,PMD c:\work\myproject\src
Scenario #2 Java Project, Output To Different LocationSuppose you have a Java project in c:\work\myproject, but you want the output from Yasca to go to a different location (z:\YascaOutput). You could run: yasca -o z:\Yasca_Output c:\work\myproject
Scenario #3 Only See Critical IssuesYou can turn up the dial and view only critical issues by using the level parameter: yasca --level 1 c:\work\myproject
These are some typical uses. Please send in a comment if you'd like examples of any others. Scovetta.com is a personal website. Opinions expressed are my own, and not those of my employer or any groups I am affiliated with.
|
|
|||||||||||||