I want to just put a bit of emphasis on the global impact of this POM.
This POM gets advertised as the appropriate parent for \any/ Apache
project building with Maven. As such, I submit to you, it should
supply all of the necessary settings (e.g. repository locations,
deployment) and no surprising extra behavior. If the Land Of Maven
wants a policy of running a full build on prepare, I'd respectfully
ask you to embody that policy in a POM that isn't the one advertised
to the complete Apache community.

On Thu, Jan 27, 2011 at 3:58 PM, Lukas Theussl <[email protected]> wrote:
>
>
> Brian Fox wrote:
>>>
>>> FWIW, if the code-signing step fails due to some POM misconfiguration,
>>> and
>>> only runs in the perform step, then you've got to rollback the release
>>> and
>>> try it again...either that, or muck around with manually shifting the tag
>>> in
>>> the SCM, which is probably as ugly.
>>>
>>> I'm not as concerned about spending a little extra time to reduce the
>>> chances of things going wrong in the release process, since this seems to
>>> happen often enough already...and causes a HUGE waste of time in some
>>> cases.
>>> If we were releasing a 100+ module project structure, then I'd be willing
>>> enough to give on this point and say that accepting a little extra risk
>>> in
>>> the 'perform' phase isn't that big of a deal. But, at least in Maven, the
>>> releases aren't that big.
>>>
>>
>> For Lukas: I agree with John here.
>>
>> For everyone else: +1
>
>
> For everyone: I agree too. Especially with the part about things going wrong
> often enough.
>
> -Lukas
>
>
>>
>> ;p
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to