Hi Suresh, sorry for not responding to your private mail, but I was stuck at the german JavaLand conference :-(
The problem with FlexPMD is that it's actually a fork of an insanely old PMD version. I had tried to get that working, but it turned out that it wouldn't be possible as Maven has changed to much in the last 4-5 years and I wasn't planing to invest my time in order to get things working just with Ant ;-) So I invested quite some time to help make original PMD itself modular to support additional languages. One of them will be Flex. I have finished that quite some time ago. I then tried migrating the old PMD fork code to the new PMD code, but it turned out here far to much has changed too. The only good solution would be to re-implement the Flex support from scratch (having to do far less as we only have to provide the language support and not update the entire PMD system) My next attempt was to use Falcon to parse Flex input and to make the rules run directly on the AST Falcon had created. This would however require us to rewrite the entire rule-base to the new AST classes. It's not impossible, but it's a lot of work. Unfortunately that one or two years ago Falcon didn't quite work as I expected it to, I got exceptions all over the place and I had a lot of trouble building it. I had therefore stopped work on this but had planned to return as soon as Falcon is more stable and the build isn't so challenging anymore ... we are on a very good way regarding both of these issues. So I hope as soon as I'm done with my Maven efforts, I am sure Alex and the others have made Falcon stable enough to be a good platform for adding real PMD support for Flex. But for this the rule-translation-task we will definitely need some helpers to help translate the rules :-) So much for the update for now. Sorry to not be able to give you a satisfying answer. Chris ________________________________________ Von: suresh babu k s <[email protected]> Gesendet: Dienstag, 8. März 2016 13:40 An: [email protected] Betreff: FlexPMD Build Error FlexPMD is generating errors when it is being build from source,looks like it is not being active for long time.please let me know if anyone tried in recent times ,would like to add some custom rulesError.....INFO] Scanning for projects...ownloading: https://repo.maven.apache.org/maven2/org/apache/apache/14/apache-14pomERROR] [ERROR] Some problems were encountered while processing the POMs:FATAL] Non-resolvable parent POM for org.apache.flex.pmd:flex-pmd:1.3-SNAPSHOT:Could not transfer artifact org.apache:apache:pom:14 from/to central (https://rpo.maven.apache.org/maven2): Connect to repo.maven.apache.org:443 [repo.maven.aache.org/199.27.79.215] failed: Connection timed out: connect and 'parent.relatvePath' points at wrong local POM @ line 25, column 13@ERROR] The build could not read 1 project -> [Help 1]ERROR]ERROR] The project org.apache.flex.pmd:flex-pmd:1.3-SNAPSHOT (E:\Notice\FlexPD\Wokspace\FlexPMD\pom.xml) has 1 errorERROR] Non-resolvable parent POM for org.apache.flex.pmd:flex-pmd:1.3-SNAPSOT: Could not transfer artifact org.apache:apache:pom:14 from/to central (https//repo.maven.apache.org/maven2): Connect to repo.maven.apache.org:443 [repo.mavn.apache.org/199.27.79.215] failed: Connection timed out: connect and 'parent.rlativePath' points at wrong local POM @ line 25, column 13 -> [Help 2]ERROR]ERROR] To see the full stack trace of the errors, re-run Maven with the -e swith.ERROR] Re-run Maven using the -X switch to enable full debug logging.ERROR]ERROR] For more information about the errors and possible solutions, please rea the following articles:ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildinExceptionERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableMoelException -- View this message in context: http://apache-flex-users.2333346.n4.nabble.com/FlexPMD-Build-Error-tp12147.html Sent from the Apache Flex Users mailing list archive at Nabble.com.
