I use ./ant or .\ant (ofbiz_home)/{customfoldername}/build-cust.xlm
this modifies the (ofbiz_home)/framework/base/config/*
I also use ./ant or .\ant (ofbiz_home)/build-setup.xml for updating my
demos.
install-first, modifies and copies all the changed files.
Update will download the new image(don't use svn) and expand it then
copy the previous saved files over the one in the image had.
so maybe a run-custom that ask where the custom build file path and name.
Jacques Le Roux sent the following on 2/10/2011 1:25 AM:
> From: "Jacques Le Roux" <
[hidden email]>
>> Hi,
>>
>> I was wondering about run-install-extseed and run-install-exttest targets
>>
>> run-install-extseed This loads seed, seed-initial and ext data; meant
>> for manual/generic testing, development, or going into production with
>> a derived system based on stock OFBiz where the ext data basically
>> replaces the demo data
>>
>> run-install-exttest This loads seed, seed-initial, ext and ext-test
>> data; meant for automated testing with a derived system based on stock
>> OFBiz
>>
>> Those are great to quickly test custom code with respective ext-test
>> data. But I wonder if using run-install for a continuous
>> integration would not be a better strategy since it allows to check
>> for any regressive code introduced by custom development. Of
>> course, only kept/used components would be concerned with all
>> implications, ie regarding dependency between components
>
> BTW maybe a better way to see run-install is as a secondary build as
> described by Martin Fowler in
>
http://martinfowler.com/articles/continuousIntegration.html#KeepTheBuildFast>
>
> Jacques
>
>> What do you think? What are your best practices with custom continuous
>> intregration?
>>
>> Thanks
>>
>>
>> Jacques
>
>
>
Locked
