FlexPMD 1.0 is out.
FlexCPD 1.0 is out (and improved).
FlexMetrics 1.0 is also out.
and guess what, the Eclipse plugin is also out.
You will find more info on the wiki
I am thrilled to announce the release FlexPMD RC5, which is mainly a bug fix version. The list of the fixed issues can be found here.
Part of that release, we added a new sub-project: FlexCPD which stands for Flex Copy & Paste Detector.
You will be able to find duplications in your Flash-based project. More info here
At the moment FlexCPD can be invoked from:
- The command-line
- Ant
- Maven
There may even be a Eclipse view for FlexCPD.... More on that later.
You can download the latest archives here
I have the pleasure to announce that Cairngorm 3 is finally out.
You can find more information on Alex Ulhmann's blog
Check it out!
Xavier
I'm pleased to announce that FlexPMD 1.0-RC4 has been released.
You can find resolved issues here (you need to be logged in to view the related issues)
On top of the resolved bugs, one feature has been added:
You can now append // NO PMD ruleName specifying the rule you want to ignore on that line.
You can find the latest download here.
Happy cleaning!
Xavier
While RC4 is on its way, I would like to share some tips about FlexPMD:
Default ruleset
Some people were asking why there were no default rulesets in the archives. There is a simple reason: if you don't specify any ruleset, the default one is loaded. The default ruleset contains every rule implemented.
Acknowledge violations
FlexPMD finds "possible" problems. It is possible that a violation for FlexPMD, has been done on purpose by the developer. So if you want to acknowledged a violation, just append // NO PMD at the end of the line. This specific violation will be ignored by FlexPMD.
Maven repository
While FlexPMD artefacts, are not (yet) deployed on a public repository, if you want to used FlexPMD with Maven, you will need to download the sources and install the artifacts in your repository.
Fine tuned ruleset
When using the ruleset creator, you can either remove a rule, modify it (changing the message, the description, or its level).
Let's say you decide, that if any rule with a high level is broken, then you want the build to be refused.
There is an extra argument in the Maven target, and the Ant task, called failOnError, which makes the build failing if an error violation is found.
Then in your favorite Continuous Integration server, the build would be broken just like if there is a compilation error, or a failing unit-test.
Let's build high quality software...
Recent Comments