You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@continuum.apache.org by José Morales Martínez <jm...@gmv.com> on 2009/04/07 20:28:52 UTC
Building a project with data changed
Currently when update a Maven project, the information is updated in the database and at this moment information in BD and pom.xml is different. If you build the project, then override database with pom.xml data. There are currently three issues related to this matter: CONTINUUM-2151, CONTINUUM-2132, CONTINUUM-2085.
I view three options:
* Do not modify this information when building a project. It would add the option to update the project with pom information.
* Add an option(check) in the build definition to indicate whether to copy or not pom information.
* Do not allow the modification of this information from the UI (I think it is too drastic).
What do you think?
-----------------------
Jose
______________________
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.
______________________
Re: Building a project with data changed
Posted by Brett Porter <br...@apache.org>.
Looks good to me!
On 22/04/2009, at 10:48 AM, José Morales Martínez wrote:
> I have created issue CONTINUUM-2188. What do you think about this?
>
> I am working in this matter.
>
> -------
> Jose
>
> ________________________________________
> De: Brett Porter [brett@apache.org]
> Enviado el: lunes, 20 de abril de 2009 7:12
> Para: dev@continuum.apache.org
> Asunto: Re: Building a project with data changed
>
> Sorry for the delayed response. I think this might be overkill - I'd
> be happy with just a checkbox about whether to update or not on the
> build definition rather than attaching another thing like this to it
> for now.
>
> - Brett
>
> On 09/04/2009, at 3:17 AM, José Morales Martínez wrote:
>
>> 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:brett@apache.org]
>> Sent: mié 08/04/2009 16:14
>> To: dev@continuum.apache.org
>> 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.
> ______________________
RE: Building a project with data changed
Posted by José Morales Martínez <jm...@gmv.com>.
I have created issue CONTINUUM-2188. What do you think about this?
I am working in this matter.
-------
Jose
________________________________________
De: Brett Porter [brett@apache.org]
Enviado el: lunes, 20 de abril de 2009 7:12
Para: dev@continuum.apache.org
Asunto: Re: Building a project with data changed
Sorry for the delayed response. I think this might be overkill - I'd
be happy with just a checkbox about whether to update or not on the
build definition rather than attaching another thing like this to it
for now.
- Brett
On 09/04/2009, at 3:17 AM, José Morales Martínez wrote:
> 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:brett@apache.org]
> Sent: mié 08/04/2009 16:14
> To: dev@continuum.apache.org
> 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.
______________________
Re: Building a project with data changed
Posted by Brett Porter <br...@apache.org>.
Sorry for the delayed response. I think this might be overkill - I'd
be happy with just a checkbox about whether to update or not on the
build definition rather than attaching another thing like this to it
for now.
- Brett
On 09/04/2009, at 3:17 AM, José Morales Martínez wrote:
> 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:brett@apache.org]
> Sent: mié 08/04/2009 16:14
> To: dev@continuum.apache.org
> 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.
> ______________________
RE: Building a project with data changed
Posted by José Morales Martínez <jm...@gmv.com>.
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:brett@apache.org]
Sent: mié 08/04/2009 16:14
To: dev@continuum.apache.org
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.
______________________
Re: Building a project with data changed
Posted by Brett Porter <br...@apache.org>.
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
On 08/04/2009, at 4:28 AM, José Morales Martínez wrote:
> Currently when update a Maven project, the information is updated in
> the database and at this moment information in BD and pom.xml is
> different. If you build the project, then override database with
> pom.xml data. There are currently three issues related to this
> matter: CONTINUUM-2151, CONTINUUM-2132, CONTINUUM-2085.
>
> I view three options:
>
> * Do not modify this information when building a project. It would
> add the option to update the project with pom information.
> * Add an option(check) in the build definition to indicate whether
> to copy or not pom information.
> * Do not allow the modification of this information from the UI (I
> think it is too drastic).
>
> What do you think?
>
> -----------------------
> Jose
>
> ______________________
> 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.
> ______________________