For now I do nothing with this/super in (SUPER_)CTOR_CALL.
Should think more about this.
Also I've changed grammer to not generate extends/implement cleases
if there is no such in the code.
Made some refactoring for build.xml to make possible to redirect build
output to custom directory (and we used too much hardcoded paths there
:)
It looks like this is my last commit before vacation, so I hope
I will break nothing :)
Some pretty big refactoring for typeaware checks performed.
Also added handling for type params. Current handling algorithm
has some preconditions and restriction, but it works for most cases
(not sure I've covered all situation when type param will have name
of real exception, but I do not think it is critical for now :)
Also, I've added column number for JavadocTag (mainly to be able use
ClassInfo for it). So, JavadocTypeCheck also affected.
And I've added new logger for TreeWalker (if we have loggers we should
use them :)
enforce which packages can import which packages. I was required to
develop this for a large project to enforce application layering rules.
The check is fairly basic at the moment, but is still sufficiently
powerful to be useful. I am sure there will be feature requests in the
future.
all nodes in AST tree (bug 1244994)
Now we set next sibling during tree creation, instead of calculating
it (the calculation doesn't work if parent is null as for toplevel
nodes such as package, import and class definition).
Added test which verify correct tree structure for all testinputs.
implementation of tree processing, now we can activate it by setting
checkstyle.use.recursive.algorithm to false (by default checkstyle
still uses recursive algorithm).
Also I've chenged build.xml so it will be possible to use it from any
location and user will be able to specify filter for tests.
code coverage report when ever the unit tests are run. The report can be
found in target/emma/report.
I have been using EMMA for a while at work and am very happy with the
results. It is not quite as polished as Clover, but you get what you pay
for. I think it is good to be able to get a code coverage report
whenever the tests are run.
Oleg Sukhodolsky
Lars Kühne
Oliver Burn
Michael Studman