This will take all the SDKs in the source directory and output them in a mavenized form to the output directory. The last parameter is used to force the generator to generate the Apache FDKs using the group-id "com.adobe.flex" instead of the obviously correct "org.apache.flex" group-id. The content of the target-directory simply needs to be copied to the local maven repository.
Updating your POMs
Specifying the Flash version
The mavenizer generates air and flex artifacts separate from the flex artifacts. In the olf FDK structure you had to specify the flashplayer using a classifier:
Please note that the version of the Flashplayer artifacts all have two segment versions and that the GroupId is com.adobe.flash.framework.
Specifying the Air version
The Flex SDK comes with a bundled Air SDK. The libs of the SDK are accompanied with special Flex AIR libs. The Mavenizer generated the SDK libs to the group-id "com.adobe.air.framework" and the Flex-Air libs to "com.adobe.flex.framework.air". This makes configuring the dependencies for Air application a little more complicated, but allows to select the target Air SDK version separately from the version of Flex SDK. This should make it easier to use new Air SDK versions that were not yet bundled with a Flex SDK.
The dependency to the air compiler artifact is only needed if you are creating an Air application (Packaging "air")
Prior to the Mavenized SDKs the theme artifacts were provided in different ways. Some were simple CSS files, some CSS with resources and some were available as compiled Libraries. When executing, the Mavenizer now compiles any non-library themes to libraries and all Themes are now available the exatyl same way.
However the Group-Id has been changed from "com.adobe.flex.framework" to "com.adobe.flex.framework.themes".
Another change has been that you no longer need a classifier.
If this was the way you previously added your theme prior to FM 6: