Comments on the module-file format

[Patrick Wright]

> One thing I'd like to bring up again regarding in-place revisions and SNAPSHOTs is that they are in general a bad idea for large systems and can cause grief when releasing and testing. You might have 10+ different versions of 1.1-SNAPSHOT for example and they are littered about your organization and servers. Often there are no constraints around releasing with SNAPSHOT dependencies either and this makes matters worse. Maven's system for all of this is something I would recommend not using.
>
> Savant uses integration builds to solve this problem which create new versions each time using a timestamp. In general, integration builds are local only and they enforce strict semantics, which SNAPSHOT doesn't.

For the record, I don't like using snapshots either, and wasn't trying
to recommend it. While we've largely moved away from them in our team,
individuals are still allowed to use snapshots if they want to access,
essentially, the latest on trunk which has not yet been verified with
an integration build. In any case, snapshots exist and the tools
support them, so I wanted to bring that case up--where local artifacts
are updated because a newer copy of the same version exists in a
remote repo.


Patrick