Flex-mojos: Maven 2 plugins for Flex

After a few time working on issues and on get a better test coverage, here is a new flex-mojos release.

On flex-mojos alpha2 the test coverage was near to 44% (blocks). Now, on alpha3 code coverage is 81% (blocks). While I was writing those extra integration tests I was able to find and fix some unknown issues.

BTW, I take some time to fix issues too. 8 issues closed:
* Issue 12 - now you can run a quick build by typing mvn install -Dquick.compile=true. It will compare the last generated artifact with current sources. If there is any new code, will recompile. If not will skip compilation.
* Issue 43 - flex-mojos will ignore test errors using -Dmaven.test.failure.ignore=true (same expression used by surefire)
* Issue 53 - flex-mojos will skip test running with -DskipTests=true. It will compile the tests. But will not run they.
* Issues 67 and 68 some fixes on AsDoc support.
* Issue 69 flex-mojos tests runner will add a sandbox exception to run tests. To do that just need to add the configuration updateSecuritySandbox. Default value is false.
* Issue 70 just a cosmetic change on flex-super-pom.
* Issue 71 fixed an old issue on compiled localization support. After Adobe feedback was piece of cake =P

This version should be flex-mojos most stable release.

VELO

Hi folks,

Some time ago, I wrote a post showing how to update compiler version.

But is possible to compile Flex 4 with flex-mojos?

First, I take this sample source.

Then, I use this knowledge to upgrade flex-oem-compiler to 4.0.0.2480.

Try to compile and got this error:

[ERROR] D:\flex\workspace\sonatype-flex-mojos\flex-mojo-IT\src\test\resources\flex4-gumbo\src\main\flex\Flex4App.mxml:[-1,-1] Unable to locate specified base class ‘flex.core.Application’ for component class ‘Flex4App’.

At this point I figure out flex gumbe came with some new manifest files:

gumbo-manifest.xml

fxg-manifest.xml

mxml-2009-manifest.xml

mxml-manifest.xml

To handle this, I add those xml to my project and this configuration:

  <build>
    <plugins>
...
      <plugin>
        <groupId>info.flex-mojos</groupId>
        <artifactId>flex-compiler-mojo</artifactId>
        <extensions>true</extensions>
        <configuration>
...
          <namespaces>
            <namespace>
              <uri>library:adobe/flex/gumbo</uri>
              <manifest>gumbo-manifest.xml</manifest>
            </namespace>
            <namespace>
              <uri>library:adobe/flex/halo</uri>
              <manifest>mxml-manifest.xml</manifest>
            </namespace>
            <namespace>
              <uri>http://ns.adobe.com/mxml/2009</uri>
              <manifest>mxml-2009-manifest.xml</manifest>
            </namespace>
            <namespace>
              <uri>http://www.adobe.com/2006/mxml</uri>
              <manifest>mxml-manifest.xml</manifest>
            </namespace>
            <namespace>
              <uri>http://ns.adobe.com/fxg/2008</uri>
              <manifest>fxg-manifest.xml</manifest>
            </namespace>
          </namespaces>
        </configuration>
      </plugin>
    </plugins>
  </build>

In the end, run mvn clean install, all compile and fine.

You can checkout this entire post source from:
http://svn.sonatype.org/flexmojos/trunk/rvin-mojo/flex-mojo-IT/src/test/resources/flex4-gumbo/

Hopefully all required dependencies are on flex-mojos maven(svn) repository. Let me know if I miss something.

VELO

Hi folks,

Some time ago I created a flex-mojos 2.0 roadmap:
http://code.google.com/p/flex-mojos/wiki/roadmap2

Now I wanna get some feedback. What do you think about this roadmap? Are you missing something? If you can change this list, what you like to change?

Please, post any comments on wiki.

VELO

Some time ago, I write a post with instructions to generate test reports here.

At that time, flex-mojos was generating the reports at wrong directory. To workaround it, was necessary to declare reportsDirectory.

Now this issue is fixed. To generate test reports you only need this:

<reporting>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-report-plugin</artifactId>
      </plugin>
    </plugins>
  </reporting>

Note reportsDirectory is not present anymore.

Hi guys,

A new flex-mojos release is out.

Main changes:
* Now is possible to pack tests into SWC. Read more here.
* Improved flex-compiler-mojo documentation, specially adding usage hints for complex parameters.
* Some fixes on docs site (http://docs.flex-mojos.info/)
* Update generator mojo to use GAS3 1.1.0-RC2 (thanks to Juraj Burian)
* Fixed some issues: 58, 59, 60, 61, 62, 63, 64 and 65.

That’s All Folks

VELO

Hi folks…

To test flex applications, flex-mojos compile and run a SWF file. Nothing new on that.

But, under certain circumstances (i.e. on multi-modular projects) you need to get access to some classes used to test your module A in order to test module B. One issue was filed asking that, check here.

To do that, you need to add a new mojo to your project:

<build>
  <plugins>
    <plugin>
      <groupId>info.flex-mojos</groupId>
      <artifactId>flex-compiler-mojo</artifactId>
      <executions>
        <execution>
          <id>package</id>
          <goals>
            <goal>test-swc</goal>
          </goals>
        </execution>
      </executions>
    </plugin>
  </plugins>
</build>

This plugin will compile your test folder into a SWC file. This SWC will be installed at maven repository under test classifier.

You can read more on Maven Guide to using attached tests.

Nice holiday to US buddies.

VELO

Sebastien still posting.

Some day ago I blog the link for the first part.

You can check the second part at:
http://www.adobe.com/devnet/flex/articles/fullstack_pt2.html

Good reading.

VELO