The problem with snapshots, and the reason for their ban in AS component-matrix, is because a version of X.Y.Z-SNAPSHOT is not enough to uniquely identify a version to make a build reproducible: * By default, Maven local repo is reconciled only once/day to check for newer versions. * The notion of "newest" snapshot is defined by a timestamp, a property of the *publishing machine*. Rouge system clocks wreck havoc on all. * A developer may have installed a newer version locally than is available to all on snapshots.jboss.org However, take a look at a typical directory: http://snapshots.jboss.org/maven2/org/jboss/ejb3/jboss-ejb3-proxy/0.1.2-S... I'd like to test out explicitly specifying an extension in the version, ie: <version>0.1.2-20080818.031348-4</version> If Maven handles this case we may again put snaps up for integration testing in AS (using this format only), and hold off preparing a proper release until it's confirmed that the version we're testing is valid. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171833#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...