> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]] > > Then, when the project decides for a code-freeze for the release, the jars > are not updated anymore till release is done. > > What do you think? <ducking/> ;-) >
Do you mean that the jars a project depends on should be "frozen" at the last successful build? I disagree. Whan a project proceeeds to a release it should, IMHO, only depend on the released versions of other projects. These are the only jars which those projects have agreed to release. These snapshots built by Gump may contain features that a project may later decide not to proceed with. If you depend on those features and they are never released, you may be in trouble. If users of your code upgrade that dependent library, you will break. Gump, in its current incarnation, is an early warning system when using the latest of everything. It alerts you to the impacts your changes made in CVS may have on other projects. Gump will not, however, warn you if you rely on a feature that is not yet released. There may be a case for doing a separate Gump run where the dependencies are provided from the latest released versions of a library rather than the current CVS HEAD, although I have not looked into what would be required to do that. Conor -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
