> parent pom in one process the plugin seems to get stuck on the plugin > dependencies defined in the first module executed. Subsequent plugin > dependency configurations are ignored. It feels like this is an issue with > the underlying Maven dependency mechanism and not with the Flex-Mojos > plugin. We're using the latest Maven 2.2.1 release.
You're right about what you're seeing, and this is how Maven2 currently works. You need to copy all your plugin deps (needed for all executions of that plugin across all modules etc) into the "first" declaration of that plugin which is executed -- the easiest is to just consolidate and copy the deps to each one. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
