I think that is a great idea, IF: The project subscribes to allow the change, which I think would happen.
But ultimately, the jars would not be in CVS, and the project could always use Gump's latest successful integration. Scott > -----Original Message----- > From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]] > Sent: Monday, March 18, 2002 12:12 PM > To: Alexandria Developers List > Subject: Crazy idea: update project jars if Gump build succedes > > > 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:alexandria-dev-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
