Hrmmm, somehow I did missed this.

Right now that is not possible, but seems to me this is a very low 
performance operation, since FM will need to scan for *.as and *.mxml, then 
parse the files to see if it is a modules or it is not.  As a limitation it 
won't be able to deal with inherited classes, for instance you have 
YourCompanyBaseModule that extends mx:Module....  it gets too hard to figure 
this out.

The only possible way would be using a wildcard match.... 
<modules>
<includes>
<include>**/Module*.mxml</include>
</includes>
</modules>

But still there is nothing like that in place.

VELO

-- 
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/

Reply via email to