Hi,
In order to start releasing falcon cleanly I did some pre-release checks and did a little cleaning up. I removed my Patch mojo from the compiler-build-tools, as we now use normal patches instead of the regexp stuff. I also noticed that I put shared test-code in there too. I moved that out into a new compiler-test-utils utils. I decoupled compiler-jburg-types and compiler-build-tools from the rest so they can be released separately (you will probably not even notice the change ... it's just a different parent module) I also moved the flexjs-maven-plugin to the "compiler" profile so it is built and released with the rest. When releasing the falcon module I would prepare 3 separate maven-releases (compiler-jburg-types, compiler-build-tools and the rest) which will be staged together and we can vote on. As the compiler-jburg-types and compiler-build-tools will probably not change in the near future, I would like to release them as 1.0.0 and not re-release them every time we fire out a new release. This will simplify releasing dramatically in the future. If you are fine with moving the externs to the flex-asjs/frameworks repo, I think I could prepare everything for a release in the coming week. I just finished re-running a complete test with a clean maven local repo so I'll checkin my changes (but keep in mind, that's still in the "feature/maven-ant-tasks" branch for flex-falcon) Chris
