Hi,

I am trying to automate our tests with RiaTest and built some
delegates for this purpose. They basically work fine when building
with Flexbuilder/eclipse, yet I do not manage to build them with flex-
mojos.

The delegates (and the automation libs) should be integrated into our
application swf for QA purposes, yet not into the release. For this
purpose I am using the test-swf goal (with flex-mojos 3.6.1).

The problem is that the resulting "release" swf file is much too small
in comparison to both the Flashbuilder version and also the related
output of compile-swf.

Here is part of my pom.xml:

...
<executions>
        <execution>
                <id>compile-cdmclient-flex-sources</id>
                <phase>compile</phase>
                <goals>
                        <goal>test-swf</goal>
                </goals>
                <configuration>
                        <sourceFile>CDM.mxml</sourceFile>
                        <sourcePaths>
                                <path>src/main/flex</path>
                                <path>src/main/resources</path>
                                <path>src/main/generator</path>
                                <path>src/main/locales/{locale}</path>
                        </sourcePaths>
                        <targetPlayer>10.0.0</targetPlayer>
                        <compiledLocales>
                                <locale>en_US</locale>
                                <locale>de_DE</locale>
                        </compiledLocales>
                        <themes>
                                
<theme>${project.build.outputDirectory}/themes/halo.swc</theme>
                        </themes>
                </configuration>
        </execution>
</executions>
...

The dependency for automation is included as follows:

<dependency>
        <groupId>com.test.package</groupId>
        <artifactId>cdm-flex-ria-delegates</artifactId>
        <version>SNAPSHOT</version>
        <scope>test</scope>
</dependency>

This is the only difference in the pom between release and test.

A workaround is to include two executions one for test-swf and the
other for compile-swf. Yet my understanding was that this would not be
necessary since test-swf takes care of both outputs.

Any idea what the problem could be?



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