Jason Dillon wrote:
Which is what you want if you have on-the-bleeding-edge dependencies.
Not all dependencies have SNAPSHOT releases.
That's understood. Just keep in mind that if you have jar files that are being updated frequently, you really should be marking them up as snapshots, otherwise you will end up inconsitencies in the builds as soon as you start breaking the system into manageble chunks. My experience has been that its much easier to put in place SNAPSHOT at the beginning.
Stephen.
--jason
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
