Hi Alger, I have spent a lot of time figuring out how to correctly structure flexmojo projects. With a team of 10-20 I suppose one person would probably look after the build. This is obviously not workable when there is the architect/system administrator and coder are the same person.
To cut a long story short I spent christmas 2010 struggling to develop a working project structure. I succeeded, but at the cost of family and friendships. Now I'm sure I will have to repeat the same process next year, and the year after that because: Maven is very opaque, when it works, it works great but when it breaks you really are stuffed. The solution. Use strace to debug your Maven builds. Want to know if it accesses something? Then strace. Want to know what it's copying? Then strace. Want to know what it's reading? Then strace. Want to know if it's writing a file? Then strace. Alternatively you can: Run your build through a debugger Create a custom Java security manager Use an Aspect to trace that stuff out Trust me, strace is a LOT easier than the above. It generates a lot of information so you will want to have some command line skills to filter the output. My typical usage is (-ff means follow fork): strace -ff mvn install &> out.txt grep src/main/mypath out.txt Now take the ball and run with it. Regards, Bryan Hunt On Feb 11, 11:38 am, Alger Werft <[email protected]> wrote: > Hi, > I'm trying out Flexmojos 4.0-beta-3 -- You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos http://flexmojos.sonatype.org/
