Hi Robert, It depends on how much changes you are making. Instead of copying entire eCommerce component over to hot-deploy, you can as well 'extend' the eCommerce component, make and maintain your changes separately (See https://cwiki.apache.org/OFBIZ/faq-tips-tricks-cookbook-howto.html#FAQ-Tips-Tricks-Cookbook-HowTo-HowtoExtendanexistingcomponentincustomizedapplication? ).
On Thu, May 23, 2013 at 9:25 AM, Paul Foxworthy <p...@cohsoft.com.au> wrote: > Hi Robert, > > I agree with the others that your UI is your UI and it's fine to copy it > and > make the changes you need for your own situation. > > It's harder with OFBiz services. You might make a change that with a bit of > refinement may one day become a submission. But for now you decide to keep > to yourself, perhaps to test it. You might have customizations that you > know > would not be relevant to the OFBiz community in general. You might base > your > work on a release of OFBiz, and cherry-pick fixes that are going into > trunk. > One day you might move to a later release, and the cherry-picked changes > won't be needed any more. > > In short, you might branch with some prospect of merging at some stage in > the future. > > In these situations, you want a clear separation between core OFBiz and > your > own changes, so you can move to a different core in future and integrate > your changes. I suspect you understand all of that perfectly well, thus > your > caution about changing OFBiz code. > > We use Mercurial patch queues (MQ) to handle this. We start with core > OFBiz, > and we make our own changes in hot-deploy when we need and want to. > Anything > that is our own mod of core OFBiz is done as a patch in a patch queue. We > have several "guards" so we can apply different sequences of patches. We > have guards for submitted patches, for pending submissions, and others for > customizations that are for a specific customer. > > MQ is working well for us and if you want to manage these issues I suggest > you give it a try. See http://mercurial.selenic.com/wiki/MqExtension for > more. > > Cheers > > Paul Foxworthy > > > Ruth Hoffman-2 wrote > > Hi Robert: > > > > Having worked on many OFBiz based ecommerce applications (both large and > > small), I agree with Paul. Copy over and use the OOTB webapp as a guide > > to move forward with your own customizations. > > > > Best of luck. > > Ruth Hoffman > > > > On 5/22/13 4:08 PM, Paul Piper wrote: > >> Hi Robert, > >> > >> that really depends on what you are set out to do. In general, I > >> recommend > >> to copy the eCommerce app over to hot-deploy and get the module to run > >> from > >> there. Then check it into your local repository to keep it consistent. > >> With > >> SVN you can use svn:external for instance to include your own module > >> while > >> keeping the rest of ofbiz consistent with the svn trunk. Then you can do > >> your own changes and commit to your local repository at any time. > >> > >> Does that help or were you looking for something else? > >> > >> Regards, > >> Paul > >> > >> P.S.: I don't think that Nick understood your question - BigFish > >> certainly > >> isn't the answer > >> > >> > >> > >> -- > >> View this message in context: > >> > http://ofbiz.135035.n4.nabble.com/New-to-OFBiz-How-to-modify-the-eCommerce-app-tp4641469p4641473.html > >> Sent from the OFBiz - User mailing list archive at Nabble.com. > >> > > > > > > ----- > -- > Coherent Software Australia Pty Ltd > http://www.coherentsoftware.com.au/ > > Bonsai ERP, the all-inclusive ERP system > http://www.bonsaierp.com.au/ > > -- > View this message in context: > http://ofbiz.135035.n4.nabble.com/New-to-OFBiz-How-to-modify-the-eCommerce-app-tp4641469p4641484.html > Sent from the OFBiz - User mailing list archive at Nabble.com. > -- Regards, Varun Bhansaly
