Thank you for the explanation. To clarify, does that mean: currently on 1.2 release the snapshot is part of project.xml is a "mistake", and in trunk/future release, it will be moved to deployment.xml?...
snapshot should be a configuration property set at deployment time (different for each environment). However project.xml is for development time and exist inside the catalog jar file. This means either I have to build a different jar for each environment (which violates the rule of same build for all env), or I have to play stunts to replace the value inside the jar before deployment.
In 1.3, all snapshot configuration is moved to the deployment file. While we always intended to separate project content from deployment content, the implementation of the deployment file is relatively new; we made some changes, hopefully improvements, to the organization of the project and deployment configuration in 1.3.
Also, where can I find documentation about "partition-detection"? What's the purpose of its own "snapshot" child element?
Partition detection is documented here: