* src/main/java | resources
* enabled tests
* removed lib/pmd-build-0.4.jar - the plan is to have this dependency in maven central
git-svn-id: https://pmd.svn.sourceforge.net/svnroot/pmd/trunk@7557 51baf565-9d33-0410-a72c-fc3788e3496d
CPD XMLRenderer was still manipulating strings and strings buffer
which lead to countless issues with proper encoding. It now uses
the appropriate XML API and relies ONLY on the defined system
variable file.encoding to set the encoding.
If one uses Ant or CLI option to change the encoding, the value of
file.encoding will then adapt. It may sounds a little bit extreme
but it should ensure consistency of all the files...
git-svn-id: https://pmd.svn.sourceforge.net/svnroot/pmd/trunk@7547 51baf565-9d33-0410-a72c-fc3788e3496d
As Maven is doing the work of having PMD in the classpath
we don't need this parameter. Having it causes problem if
you remove the lib/ folder in the root of the project, so
...
git-svn-id: https://pmd.svn.sourceforge.net/svnroot/pmd/trunk@7546 51baf565-9d33-0410-a72c-fc3788e3496d
In order to run javacc I implemented a stupid hack
copying and renaming the jar file from the local
repository to a folder called 'lib' (otherwise,
the associate AntTask can't find the jar as it
expect it to be named javacc.jar - grrr...)
Anyway, this change remove the folder at the end
of the alljavac run.
git-svn-id: https://pmd.svn.sourceforge.net/svnroot/pmd/trunk@7545 51baf565-9d33-0410-a72c-fc3788e3496d
Currently it's not possible to generate
documentation for a rule with a code based
descriptor - short of generating an XML file from
it and process it through the current set of XSL
transformation we use to produce the website.
While it's a nice idea, I don't think this is
eleganlty doable and I do think it's something
"people are desperatly" waiting for. So, as I
don't want this item to block the release, I'll
remove it...
git-svn-id: https://pmd.svn.sourceforge.net/svnroot/pmd/trunk@7542 51baf565-9d33-0410-a72c-fc3788e3496d
Turning this set of classes into a Maven plugin
has been incredibly easy (less than 30 minutes
actually) and allow us to simplify a little bit
the pom.xml configuration.
git-svn-id: https://pmd.svn.sourceforge.net/svnroot/pmd/trunk@7534 51baf565-9d33-0410-a72c-fc3788e3496d
Fix a bug in the website generation leading all entries in the rulesets navigation
menu to be duplicated.
Also introduce Java Logging, instead of System.out, as a logger for the tools's
subproject. (Rationale behing that is - I hope, an easier integration with Maven later
on without making this code dependant of any librairies outside the JVM).
git-svn-id: https://pmd.svn.sourceforge.net/svnroot/pmd/trunk@7528 51baf565-9d33-0410-a72c-fc3788e3496d
The tools subproject was created over 2 years ago to simplify the build
process and enable both Maven 2 and Ant to easily do what maven 1 was
actually doing for us. The present refactoring has greatly clarified the
code and allow the build to process rulesets's directory recursively, in
order to cope with new rulesets directory layout.
Note: as we are now moving forward with using only mvn as our build system
this subproject will probably wrap into a regular mvn-plugin, and therefore
should be moved from the pmd/ directory to the root of our svn. Maven plugin
integration should reduced greatly the complexity of the pom.xml and remove
the pmd-build-*.jar from the repository... (however, it remains to be done).
git-svn-id: https://pmd.svn.sourceforge.net/svnroot/pmd/trunk@7519 51baf565-9d33-0410-a72c-fc3788e3496d
