Was just reading this article (I had read it before and still think there is currently no option to add support for flex to PMD without adding this to the PMD project). http://pmd.sourceforge.net/pmd-5.1.3/new-language.html
In our FlexPMD project we generally have two parts ... a GUI editor/viewer written in Flex and the FlexPMD written in Java (Ignore the hybrid thing ... don't really know what that's for ;-) ). I guess we could leave all as is with the GUI part. But going though the individual fragments of FlexPMD I noticed that again we have a rudimentary parser for ActionScript. That parses AS code and creates an Abstract Syntax Tree from this an which the FlexPMD rules operate ... now I was thinking ... how would it be, if FlexPMD referenced falcon and used the parsers and AST from that? To me it sort of looks like all the tools are re-inventing the wheel. And this way our zoo of code could start growing together. Chris ________________________________________ Von: Christofer Dutz <christofer.d...@c-ware.de> Gesendet: Freitag, 5. September 2014 12:45 An: dev@flex.apache.org Betreff: AW: Migrating Flex PMD to latest PMD version Just for the reference ... I pushed my changes to the feature branch "feature/flexpmd-pmd-update" ... Chris ________________________________________ Von: Christofer Dutz <christofer.d...@c-ware.de> Gesendet: Freitag, 5. September 2014 12:32 An: dev@flex.apache.org Betreff: Migrating Flex PMD to latest PMD version Hi, even if I got a lot of stuff working with FlexPMD, I was still having problems with the report-plugins for maven complaining about API incompatabilities. It seems that this is due to changes in the maven report and site plugin. I decided not to fix these problems, but so solve them by updating FlexPMD to PMD 5.1.3 as well as the latest pmd maven plugin. After migrating almost everything to the new versions I am now blocked by one issue which i hope the PMD guys will answer soon. In PMD 5.x a rule has to specify the language it is designed for. This allows to create mixed rule-sets. Unfortunately the supported languages are hard-coded into PMD (net.sourceforge.pmd.lang.Language?) and I currently see no way in which I could make FlexPMD extend this. Extending it in PMD itself sort of sounds problematic too, because I doubt they will add a language for which the implementation is outside of their project. So I haven't dropped the ball ... I am just expecting to have a little stall on my work here. Chris
