cookies and code

Over the last few months, I’ve been working with Michael Labriola on the next minor version release of Fluint. Well, this evening Michael and I put the finishing touches on release 1.1.0. This release brought all of the changes I made to get Fluint working at the office for our CI process to the community. There are a couple of cool little gems that I think will be helpful for some:

• Separation of failures and errors in test reporting (visual and XML).
• XML compliant output with most CI servers as well as the JUnitReport task in Ant and the Surefire Reporting plugin in Maven.
• Support in the Ant task for truly headless executions of the AIR Test Runner via xvfb-run.
• Support for relative paths in the Ant task and AIR Test Runner.
• Better error handling for non-compliant modules loaded into the AIR Test Runner.
• LogBook integration for debugging
• A big folder re-organization and Ant scripts to support developers when they need specialty builds.
• Agreed upon a branching and tagging strategy so the community can have stable snapshots of source to build.

We probably should put together a ChangeLog wiki page, so that may be available soon. We did a few updates to the wiki, so stop by the Google Code site and check out the changes. Also, provide feedback on the discussion list, if there are features you’d like to see implemented, bugs that you find, or just general questions you need help with. People are great about helping on the list, so don’t feel discouraged.

This is my first major release of an OSS project that I’ve had code go into, so thanks to everyone who helped with the release, especially my wife for putting up with a lot of late nights. There is a lot more to come with Fluint over the next year that is going to be really exciting. Look for announcements during my presentation at FlexCamp Miami and on the discussion mailing list. Hope you enjoy the new release!

Tags: actionscript, air, ant, continuous integration, flex, fluint, maven, subversion, xunit