Here is a list of issues we encounter when trying to work with the whole maven enchilada. 1. There is no staging server / level when publishing a version in Maven. On a modular project portfolio (say Hibernate), it means you need to push a version in the wild, give it a try with related bits of the project and potentially fix issues that came up during the release process. In a pure Maven way, thou shalt not republish the same version. The reason comes from: - the absence of a staging server - a rather stupid caching approach Today, people either have to a. create a new release (which is very long as you need to update doc and a few other things) => not practical b. override the broken fresh release. People that decided to go ahead of time and try from maven before the official announcement now have a wrong cache While this can be worked around somehow when a single person is releasing all the dependent modules, there is no solution today when the release is done by multiple people. 2. There is no (that I am aware of) continuous build integration of JBoss AS using snapshots, so errors come up late in the game when final releases are already in Maven. This makes problem 1. even worse. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171809#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...