Sylvain Wallez wrote:
<snip/>
There are 3 possible policies:
1/ do not keep sources. The build date that's present in the jar name gives us enough precision to get the corresponding sources, even if some files may have changed within a 24 hour period.
2/ keep sources as a separate zip file. This allows to distribute binary-only jars, and we can dig the Cocoon CVS to get the corresponding sources when needed.
3/ include the sources inside the jar. This makes the jar size bigger but ensures immediate availability of source files.
Please cast your votes: [ ] do not keep sources [ ] keep sources as separate zip files [X] keep sources in jar files
This solution ensures permanent and unambiguous availability of snapshot sources, especially in critical situations such as commando-debugging at a customer site months after the deployment (yes, we sometimes deploy unreleased Cocoon versions).
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
