Unless the inheriting project overrides the preparationGoals property
explicitly, you should be good.
On Jan 26, 2009, at 8:24 AM, Kent Närling <[email protected]>
wrote:
That was what I was planning, which is easy enough for me, just
wanted to
check before that this was the best way... thanks! :-)
Will this configuration setting be inherited even if I change other
parts of
the configuration in the inherited projects? or will they then
override this
with the default empty list (removing my called plugins)?
//Kent
2009/1/26 Edelson, Justin <[email protected]>
> Write plugins to perform your validation and add them to the
> preparationGoals of the release plugin.
>
> Justin
>
>
> On Jan 26, 2009, at 7:12 AM, Kent Närling <[email protected]
e>
> wrote:
>
> Just asking to see if anyone wanted to do the same and hints
about the
>> best
>> way of doing this:
>> I would like to add some simple standard pre-validation steps
before
>> making
>> a release of any project in the company.
>> For instance checking that some standard files (release notes,
etc) are
>> present and up-to-date etc
>>
>> What is the best way to achieve this?
>>
>> Adding standard configuration for the release plugin in the root
parent
>> project?
>>
>> We are running continuum and invoice the release plugin there,
which is
>> working nicely so I don't want to change any of that behaviour,
just want
>> to
>> add this behaviour...
>>
>> Grateful for any pointers or if there is stuff others did in this
area etc
>> :-)
>>
>
--
Kent Närling
System Architect
SEAMLESS
Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden
Phone: +46 8 5648 7800, fax: +46 8 5648 7823
Mobile: +46 70 836 9925
Mail: [email protected]
www.seamless.se
