Brett, it is a good idea. I propose a new select field in Build Definition. Something like 'Update policy' where you can select your update policy.
Update policy would be defined in new Administration Menu and its design could be something like to it: Update Policy -------------- Name: .... Field Updated Current POM New POM Project name Description X Version X X SCM Url X X SCM Tag X X X Don't Uptade fields for new POM What do you think? If you think it is a good idea I'm going to start in it. ----------------------- Jose -----Original Message----- From: Brett Porter [mailto:[email protected]] Sent: mié 08/04/2009 16:14 To: [email protected] Subject: Re: Building a project with data changed I like (2) as a sensible middle ground. Let the user decide. A more fancy one might be to allow updating only if the POM is newer by comparing times, but that doesn't necessarily cover all fields, and I'd still want it as an option to enable vs. always updating or never updating a suggested here. Would be a great change! Cheers, Brett ______________________ Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener informacion clasificada por su emisor como confidencial en el marco de su Sistema de Gestion de Seguridad de la Informacion siendo para uso exclusivo del destinatario, quedando prohibida su divulgacion copia o distribucion a terceros sin la autorizacion expresa del remitente. Si Vd. ha recibido este mensaje erroneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboracion. ______________________ This message including any attachments may contain confidential information, according to our Information Security Management System, and intended solely for a specific individual to whom they are addressed. Any unauthorised copy, disclosure or distribution of this message is strictly forbidden. If you have received this transmission in error, please notify the sender immediately and delete it. ______________________
