- build checkstyle-all.jar directly from jars, without unpacking them in a tmp folder
- avoid adding overview.html from beanutils.jar to checkstyle-all.jar
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 :)
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.
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.
Added ignoreAbstractMethods property to allow configure HiddenField
check to ignore params of abstract methods.
Now test inputs (almost all) will be compiled as part of
run.test.suite and run.tests targets (this compilation requires
jdk1.5 or higher)
All references to Jakarta Regexp removed from the docs/javadocs.
Removed regexp.jar.
Patch 835901:
Added package lists for antlr and jdk to make rosslink our docs with
antlr and jdk1.4.2 (if you see some problems here feel free to correct).
- we avoid some compiler warnings on JDK 1.5
- follow the advice from the Ant team ("we highly recommend to always set this attribute")
- even if Checkstyle is compiled on JDK 1.5, it can still be used on 1.3 (untested)
the <junit> task. By setting to "perBatch" the "run.tests" target takes
~21 seconds to execute instead of 2 minutes 12 seconds.
Since this version of ANT has been released for over six months, this is OK
for the performance gain. Still does not account for the current failure in
the tests though.
- This is not really code any user should rely on. Package names, API, etc. are not stable
- trims down distribution size by several MB (uncompressed)
- class javadoc of checks is used for autogenerating xdocs (see CheckDocsDoclet),
those classdocs are easier to write if they only serve one purpose
Oliver Burn
Lars Kühne
Oleg Sukhodolsky
Michael Studman