Hi Justin, no wonder you were having a hard time with this ;-) It is built with flexmojos 3.5.0 ... this is insanely old and completely incompatable with Apache Flex. Perhaps I should simply update the project to work with Flexmojos 7.0.0 and to use Apache Flex 4.13 But as we have never released Flex officially yet, you would still have to Mavenize 4.13 manually before being able to build it.
I also saw a lot of the Maven metadata needs updating ... the SCM the DistributionManagement and a lot more still point to Adobe systems. Sounds like a good thing for me to work on when I'm sitting around in my Hotel during the week ... certainly better than getting a few of these "Alt" Beers they drink in Düsseldorf (Local speciality beer) ;-) Chris -----Ursprüngliche Nachricht----- Von: Christofer Dutz [mailto:christofer.d...@c-ware.de] Gesendet: Sonntag, 24. August 2014 12:32 An: dev@flex.apache.org Betreff: AW: Flex PMD donation I'll have a look at this ... usually in these cases, there's a "minimal" profile you select to build the initial artifacts and then you can build as normal. Chris -----Ursprüngliche Nachricht----- Von: Justin Mclean [mailto:jus...@classsoftware.com] Gesendet: Sonntag, 24. August 2014 10:42 An: dev@flex.apache.org Betreff: Flex PMD donation Hi, I've taken a look at Flex PMD to see what it required to become a release and can't make head or tails of the maven setup. It seem to me that each subproject requires all the others to be already compiled - sort of a chicken and egg issue. My knowledge about maven is minimal at best, so would someone who knows a bit more mind taking a look at the poms and explain what's going on / what needs to be done to get everything to compile locally. I am able to compile some sub projects but only if I manually do each one in a specific order. eg this order works for the first few projects as3-parser-api. as3-plugin-utils (test need to be modified for test to pass), flex-pmd-test-resources, flex-pmd-files. Thanks, Justin
