While I'm at it ... currently all maven artifacts are structured in a flat directory and the "parents" are found using the "relativePath" tag ... I greatly dislike projects in this structure. Would there be any objections against me moving things around a little to reflect their natural structure?
Currently I had to open a pom and find out what that modules parent was, from that modules pom I got to that modules parent and so on ... at the end I found the root, but I really prefer a pom.xml in the root of the project and to get started from there on. What do you think? 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
