Maybe it's just because I'm hungry, or because I'm shutting off my computer
and will not see your replies till tomorrow ;-) , but I just had this crazy
idea:
---------------------------------------------------------------------
What would you think of making Gump update the jars
of the projects with fresh ones if the build succedes?
---------------------------------------------------------------------
This would really be *cross-project integration*: catching build errors is
ok, but we this way we can also catch errors on program behaviour early.
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/> ;-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
