Ah. I can poke in the maven core a bit and figure out what the problem is. If it is related to the custom scopes I did see where the set of resolved artifacts can be set on the project and some ways to do the resolution ourselves in the mojo execution using a public helper that maven has in the core... I implemented something but a quick test still failed and I haven't had a chance to look more into it.
I committed a test case to a new branch on github that currently fails. Do you know an easy way to get the pom based tests to run and debug the maven execution being run as a test? I can run maven and attach to my debugger but once it gets into executing the test cases none of my breakpoints get hit (does it execute in a different jvm or something?) I went to run the pom for that test case directly but it has many places where it is using placeholder variables for the versions currently. Is there a way to pass in those values as parameters so that it will run? If not I will just find and replace manually tomorrow on a copy of it so I can run it in a debugger-attached maven and take a closer look at what is going on. Ryan On Nov 30, 2010 5:34 PM, "Marvin Froeder" <[email protected]> wrote: -- 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/
