Hi everybody,

when using flexmojos:test-swf for including the automation libraries
into our flex application, I fell on the questions below, to which I
could not find answers in documentation/discussions.

Our procedure is as follows:
1. we are using flexmojos-3.6.1 / maven 2
2. test-swf is executed as an additional goal in the pom.xml
        <execution>
                <id>generate-test-client</id>
                <phase>compile</phase>
                <goals>
                <goal>test-swf</goal>
                </goals>
        </execution>
3. we are using flex framework version 4.1.0.16076
4. Our resulting swf is packaged into a web-app afterwards using
another pom

The problem is that there are tons of runtime errors when trying to
use the resulting test swf file.
These are apparently caused by a missing dependency - although nothing
has been changed related to this dependency.

Hence the following questions:

1. I was able to produce a somewhat "bigger" swf with the test-swf
goal as compared to the compile-swf indicating that the libaries are
actually included. See also:

[INFO] Flex compiler configurations:
-compiler.include-libraries C:\.m2\repository\com\adobe\flexunit
\flexunit\4.0.0\flexunit-4.0.0.swc C:\.m2\repository\com\riatest
\riatestagent4\3.5\riatestagent4-3.5.swc C:\.m2\repository\com\adobe
\flex\framework\automation\4.1.0.16076\automation-4.1.0.16076.swc C:
\.m2\repository\com\adobe\flex\framework\automation_agent
\4.1.0.16076\automation_agent-4.1.0.16076.swc C:\.m2\repository\com
\adobe\flex\framework\automation_spark
\4.1.0.16076\automation_spark-4.1.0.16076.swc C:\.m2\repository\com
\adobe\flex\framework\automation_dmv
\4.1.0.16076\automation_dmv-4.1.0.16076.swc

The two artifacts are lying next to each other in the target dir.
How is the test version now deployed into the web-app? Is it enough to
just rename it and then put into the tomcat web app directory
replacing the original swf? Does anyone have an idea on how to setup
the web app pom for doing this?

2. It seems to me that the naming of the resulting swf is not
consistent with usual maven patterns: the output is called $
{project.artifactId}-${project.version}-test.swf so it cannot be
referenced in other poms as a regular dependency. Could the name be
changed to ${project.artifactId}-test-${project.version}.swf? This way
it could be used in subsequent builds.

3. Also it seems, that the test artifact is not correctly installed in
the local maven repository (the correct directory m2 repository dir is
created, yet the test artifact is not written to it. Did anyone
encounter a similar problem?

Sorry, for the epics, I hope these issues are relevant to some others
as well.

Regards
Matthias

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