If you take testing seriously as I do, you most likely know test code coverage tools. And in the Flex Universe the de facto standard is Flex Cover. Now let’s be honest here, the tool does the job but it isn’t simple. Using it requires a special compiler to run code on Flex projects, which is the main reason why test code coverage never got into Flexmojos. The available tool was too complex to use, and so I never gave it any serious thought.
Since day one, Flexmojos has tried to follow the KISS philosophy (Keep It Simple Stupid Smartguy). With that in mind, Flexmojos is proud to announce state of the art test code coverage support.
Read more…
Sonatype
flexmojos
On March 18 2008 I checked in the first bits of code for Flexmojos. Two years later, here we are: Flexmojos now provides first-class support for Flex and AIR development within Apache Maven. It allows for Maven to compile, optimize, and test Flex SWF, Flex SWC, Air SWF and Air SWC and Air files.
We are celebrating this anniversary with a dual release of Flexmojos 3.6 and Flexmojos 4.0-pre-alpha-1.
Flexmojos 3.6 Release
Flexmojos 3.6 most relevant changes:
- Add a new source-view goal which goal produces a syntax highlighted version of the as, mxml and html if they are bundled in a SWF (thanks to Julien Nicoulaud for this contribution)
- Some fixes to Flexbuilder metadata generation
- Add support to Flex SDK 4.0.0.13555 and newer
- Add support for building applications using Flashplayer 10.1 and Air 2.0
- New configuration includeAsClasses for SWC compilation. Wildcard support for includeClasses
- Generator mojo now supports package translation between Java and generated AS3
- Support for granite generator 2.1 (thanks to Kyle Lebel)
For a full list of changes on 3.6, visit this page: https://issues.sonatype.org/browse/FLEXMOJOS/fixforversion/10629
Maven
apache, flexmojos, Maven
Last night I released Flexmojos 3.5.0.
Flexmojos provides first-class support for Flex and AIR development within Apache Maven. It allows for Maven to compile, optimize, and test Flex SWF, Flex SWC, Air SWF and Air SWC.
Most relevant changes:
- fix the unit test parameters that stopped working on 3.3.0
- asdoc now allow to aggregate all sub modules docs
- created a new goal that build SWF with automation swcs
- fix problems when building modules and runtime libraries
- add the ability to produce non-optimized RSLs
- fix asdoc on Flex 4
For a full list of changes, visit this page: https://issues.sonatype.org/browse/FLEXMOJOS/fixforversion/10437
VELO
Sonatype
Flexmojos 3.4.2 is out!
Flexmojos provides first-class support for Flex and AIR development within Apache Maven. It allows Maven to compile, optimize, and test Flex SWF, Flex SWC, Air SWF and Air SWC.
We are proud to announce that Flexmojos now supports Flexunit4 and Fluint, being the first maven plugin to support Flexunit 4.
You can see all the other changes in Jira.
This is likely the last release in the 3.x series (although any critical bug will force a new release). Flexmojos 4.x development is focusing Flex 4. It probably won’t be compatible with Flex 3, but Flex 3 is well served by Flexmojos 3.x. Maven version will be bumped too, to Maven 2.2.1 or Maven 3, which contain some bug fixes not available on Maven 2.x (Flexmojos 3.x still compatible with Maven 2.0.9).
Sonatype
Continuing the series of articles, let’s check how we do integration tests for nexus plugins.
The kungfu virus scanner
The kungfu virus scanner is a simple nexus plugin. It will prevent nexus from caching infected files (it will still serve the file, but won’t cache it). To know if a file is infected or not, there is a “sophisticated” algorithm that checks if the file has the word “infected” in its name. It is used for demonstration purposes only and is useless for everything else. You can download its source files here.
To run our test, first of all, we will need a Nexus instance that will be launched and used to hold the plugin being tested. Originally we used the maven-dependency-plugin to unpack the Nexus bundle. Then, we used the same to copy the plugin under test to nexus plugin-repository directory. This alone would mean about 20 lines in the POM and no potential for reuse between different plugins, so we decided to write a specific testing plugin to create the environment required by Nexus plugins. Thus was born the nexus-test-environment-maven-plugin (we should come up with a shorter name =D ).
Read more…
Sonatype
