Nick Chalko wrote:
If I understand the proposal, the hypothetical tag would compile clean for a period of time, except when the jelly core failed to compile, at which point an old version of jelly would be downloaded and the taglib compile would fail.As to your specific proposal, I'm concerned about co-evolution. Suppose a new Jelly tag requires something to be added to the core of Jelly. Since this tag will either be released concurrently with, or after Jelly is, this is not a problem. However, suppose one day somebody forgets a semicolon in a commit to Jelly...My proposal would be option say gen.sh --downloadNotDrop That way people can use gump on whatever subset they want
I don't object to the proposal, but in my mind there is a differnce between not having downloaded cryptix and jelly failing to compile.
FYI: quite a ways back, Geir had a suggestion for the latter scenario. The suggesion was that gump save the jars from prior runs and use them instead. In many ways, this is mostly implemented... there is a jardir attribute on the workspace, and the dependency checking logic simply checks for existence of the jars, not their dates.
- Sam Ruby
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
