Comment #2 by RedBugz:
We actually did this with our automation build, though we cheated a
bit. I haven't
applied the same steps to our main application since we always run from
within Flex
Builder currently, but it should be a similar setup.
We built the app in Flex Builder, then put a copy of the Main.html in
src/main/resources, with all instances of the application replaced with
${project.build.finalName},then set up the pom like this:
<plugin>
<artifactId>maven-resources-plugin</artifactId>
<executions>
<execution>
<id>automationresources</id>
<phase>install</phase>
<goals>
<goal>resources</goal>
</goals>
<configuration>
<outputDirectory>${basedir}/target</outputDirectory>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
<resources>
<resource>
<directory>src/main/resources/</directory>
<filtering>true</filtering>
</resource>
<resource>
<directory>src/main/flex/</directory>
<excludes>
<exclude>org/**</exclude>
<exclude>com/**</exclude>
<exclude>*.mxml</exclude>
</excludes>
</resource>
<resource>
<directory>${basedir}/html-template</directory>
</resource>
</resources>
We don't have our projects completely set up the maven way yet, so this
should be
tidier once we get that cleaned up.
We plan to set this up for our main application build in a few weeks.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings