We are doing this on our end right now, it just means that every time there is a patch, we need to go through the process of putting all of the jar files in the repository. No big deal, but lots of other java centric projects are offering ‘official’ maven repositories that provide the jars. It serves to make it easier for all maven users out there to upgrade to the latest version wowza and stay current with patches, instead of having everybody go through the same steps.
Understandable if you don’t want to deal with this. I didn’t find any other posts related to maven on the forums, so there may not be many of us out there.
However the versioning question doesn’t apply. The individual module project’s maven build script specifies the exact version to pull from the repository (1.6.0.15). The repository keeps all of the separate versions available in parallel. So this would not be an issue.
Overall i’ve found maven to be a really good thing for our development. It’s a natural for java, and projects like Flex Mojos ( http://code.google.com/p/flex-mojos/ ) have made it an excellent way to build flex applications.