Hi,
As I have seen more and more dependencies between the different parts of the Flex ecosystem, I just added a diagram to our Wiki <https://cwiki.apache.org/confluence/display/FLEX/Subproject+Dependencies> https://cwiki.apache.org/confluence/display/FLEX/Subproject+Dependencies I added the parts that I'm currently working on, so feel free to add your stuff :-) I think we should start a release strategy in which we start releasing the parts that are blocking other parts first instead of releasing what's easy first and eventually having to push another release in when detecting problems with other parts up the stream. What I will personally put more effort in, is finally releasing the Mavenizer. After that's done I could release Flexmojos 7.1 ... in my opinion BlazeDS should already be in a releasable state. If you don't let yourself be distracted by the completely out of date legacy Ant wrapper ... the Maven part with it's test suite runs fine (The failing tests, fail because on Apaches Jenkins there seem to be restrictions in spawning secondary VMs that open ports but I'll have another look at that). Releasing BlazeDS would eliminate one more Adobe dependency from the Installer that is causing some trouble currently. In Squiggly I noticed some modules Chris
