"ALRubinger" wrote : | What is the reasoning behind this? If snapshots are done only at the project level, then: | | 1) AS increments to snapshot of project A | 2) EJB3 remains on release 1 of project A | 3) AS requires release 2 of project A, updates shared parent | 4) EJB3 implicitly gets release 2 now, and has version conflict because it hasn't been seeing snapshot changes all along. Possible compile and runtime problems. | Too many projects are affected by an unknown release. A project may not even allow snapshot releases in its build policy. The potential for 4 exists regardless of whether or not snapshots are used. Any update of the shared parent needs coordination and should result in rollback if existing builds fail. Snapshots simply cannot be adequately coordinated in my view. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136463#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...