Author Archives: Marvin Froeder

Continuous Compilation in FlexMojos


October 14, 2010 By
Marvin Froeder

I’ve got some great information to pass on. One of our open source contributors Joa Ebert contributed some code to enable a very useful feature in FlexMojos 4.0. FlexMojos 4.0 will ship with a new feature for rapid application development and good old Flash experiments. Continuous compilation monitors your source path and dependencies. Whenever your […]

Continue reading...

Categories: Uncategorized

Flexmojos Two Years Later


March 17, 2010 By
Marvin Froeder

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 […]

Continue reading...

Categories: Uncategorized

Flexmojos 3.5.0 is out!


January 28, 2010 By
Marvin Froeder

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 […]

Continue reading...

Categories: Uncategorized

Flexmojos 3.4.2 is out!


November 2, 2009 By
Marvin Froeder

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 […]

Continue reading...

Categories: Uncategorized

Profiling Maven Tests


September 7, 2009 By
Marvin Froeder

A few days ago we changed nexus integration tests to use an embedded version of nexus instead of using a forked VM. Before every test Nexus is started and then stopped again after the test completes. This is done once for each test class (Junit: @BeforeClass=start nexus, @AfterClass=stop nexus). During the first run we noticed […]

Continue reading...

Categories: Uncategorized