Subject: Workaround to see violations if they do not show in your view...
From: Paul Freeman (firstname.lastname@example.org)
Date: Wed Dec 11 2002 - 12:57:28 EST
Hi Class -
What follows are instructions regarding a workaround to see the
violations in the APLib if they do not show up in your Eclipse plugin.
To see the violations, you will need to generate the log file that
contains the violations with the command line version of the homework.
Then you can replace the log file used by the plugin with the command
line one. All of the violations in this file will be read, so please
remember to delete the log file generated by the command line version
prior to running the aplib test from the command line, i.e. the log file
can contain multiple sessions (violations detected by more than one run
of the program). You want to make sure the log file read in by the
Eclipse plugin only contains the last session's worth of violations.
Here are the instructions:
There is a "hack" I can think of. If you can produce the command-line
first make sure the following line in the "LoDChecker.lcf" file is set
to something very large like 20000
this will produce all of the violations in one log file.
Next copy it to the directory:
where workspace is the workspace directory that contains your project
and <project_name> is the name of the aplib project
Now change the name of the copied log file to:
Now when you are in the Eclipse environment (you don't need to shut it
down to do the steps above) select the aplib project (which has been
checker enabled) and the violations should load into the violation window.
you can now use the double_click feature to view the violations.
Let me know if the instructions above need any further clarification.
This archive was generated by hypermail 2b28 : Wed Dec 11 2002 - 13:01:12 EST