Flexbuilder goal barely provides you an workable environment.... it doesn't
make flexbuilder builder the exactly same thing flexmojos does.
About the extra configurations, well, you had it hardcoded to your old
plugin, since that isn't the case anymore you need to write this information
somewhere, flooding the pom with this stuff... may be pom inherit can help,
but you probably already tried that, right?!
VELO
On Wed, Sep 29, 2010 at 5:30 AM, Nicolas Hurion <nicolas.hur...@gmail.com>wrote:
> Hello all,
>
>
>
> In my company, we are currently using a custom made maven plug-in, created
> a long time ago, for compiling flex modules and we are investigating the
> possibility to switch to FlexMojos.
>
> One particular feature that we have in our plug-in, is a new type of
> artifact, that we called fxm, that is actually the compilation of the same
> module twice, once as a swc and once as a swf.
>
> Those fxm modules can also have a moduleCSS that allow us to also compile
> one CSS per module and attach it to the main artifact with a style
> qualifier.
>
> We managed to do the same with Flexmojos by adding the configuration of two
> extra executions and configuring the build-helper plug-in to attach the swf
> to the swc artifact.
>
> But this is quite verbose plug-in configuration that we would have to
> repeat in each module configuration. I was wondering if there was a way to
> make this with less configuration?
>
>
>
> One issue we faced with Flexmojos is that we use namespaces, and when we
> include a namespace, we also have to specify that we want to include all the
> classes otherwise the one that are not imported in that module aren’t
> included.
>
> It’s working, but it’s again something that we have to specify in each
> module.(we have a lot of modules)
>
> We had a look in the source code, and we found in FlexbuilderMojo the
> following test :
>
> if ( includeClasses == null && includeSources == null &&
> includeNamespaces == null )
>
> {
>
> // Changed to relative paths to eliminate issues with
> spaces.
>
> additionalCompilerArguments.append( " -include-sources " +
> plain( cleanSources( getSourceRoots() ) ) );
>
> }
>
> else if ( includeSources != null )
>
> {
>
> additionalCompilerArguments.append( " -include-sources " +
> getPlainSources() );
>
> }
>
>
>
> And the includeNamespaces is managed just after in another if.
>
> We were wondering if you would consider removing the “&& includeNamespaces
> == null “ from that statement.
>
> This would allow to only have to specify the namespaces we want to include
> and by default all the classes would be included as well.
>
>
>
> One thing that I didn’t find out, is when a link-report is provided, does
> the FlexbuilderMojo also add it to the compilation parameters of the
> project?
>
> This is important for us because to speed up development process, we often
> hot deploy only the modified swf compiled by FlexBuilder to the server, so
> we need to have FlexBuilder compilation as close as possible to the one made
> by maven.
>
>
>
> Thanks in advance for your responses,
>
> Nicolas.
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Flex Mojos" group.
> To post to this group, send email to flex-mojos@googlegroups.com
> To unsubscribe from this group, send email to
> flex-mojos+unsubscr...@googlegroups.com<flex-mojos%2bunsubscr...@googlegroups.com>
> For more options, visit this group at
> http://groups.google.com/group/flex-mojos
>
> http://flexmojos.sonatype.org/
>
--
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
To post to this group, send email to flex-mojos@googlegroups.com
To unsubscribe from this group, send email to
flex-mojos+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/flex-mojos
http://flexmojos.sonatype.org/
