Hi All,

We've run into a slight issue with plugin dependencies.  We're using plugin
dependencies to configure the version of Flex to use in several Flex modules
with the Flex-Mojos plugin.  The idea is we need to support two different
versions of Flex, v3.4 and v4.0.  This works fine as long as the different
versions are run in separate Maven processes.  However, when run from a
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.

This affects our ability to do easy releases of the entire platform and
complicates our module structure greatly.  I have a test project available
if that would help.

Please advise,

-- Tim

Reply via email to