Re: [Proposal] Return History Feature in eCommerce

+1 Thanks & Regards --- Arun Patidar Director of Information SystemsHotWax Commerce On Mon, Apr 30, 2018 at 4:48 PM, Devanshu Vyas wrote: > +1 > > Thanks & Regards, > Devanshu Vyas. > > > On Sat, Apr 28, 2018 at 7:13 PM Ratnesh Upadhyay < >

Re: [Proposal] Return History Feature in eCommerce

+1 Thanks & Regards, Devanshu Vyas. On Sat, Apr 28, 2018 at 7:13 PM Ratnesh Upadhyay wrote: > Hi Devs, > > I have gone through eCommerce application and noticed that we have order > history section there but we don't have return history. So I would like to >

Re: [Proposal] Return History Feature in eCommerce

+1 Jacques Le 28/04/2018 à 15:44, Rishi Solanki a écrit : +1 Rishi Solanki Sr Manager, Enterprise Software Development HotWax Systems Pvt. Ltd. Direct: +91-9893287847 http://www.hotwaxsystems.com www.hotwax.co On Sat, Apr 28, 2018 at 7:13 PM, Ratnesh Upadhyay < upadhyay.ratn...@gmail.com>

Re: svn commit: r1830236 - /ofbiz/ofbiz-framework/trunk/framework/webtools/widget/ServiceForms.xml

Hi Scott, Gil, If I understand well, OOTB crashed jobs are only restarted at startup. So maybe adding a link to manually restart them any time makes sense? Jacques Le 27/04/2018 à 07:48, Gil Portenseigne a écrit : Hello Scott, Thanks for the review and the pointer to reloadCrashedJobs. I

Re: buildbot failure in on ofbizTrunkFramework

Recent build is success, https://ci.apache.org/builders/ofbizTrunkFramework/builds/205 Thanks & Regards -- Deepak Dixit www.hotwax.co On Sat, Apr 28, 2018 at 5:59 PM, Yash Sharma wrote: > Hello, > > I guess we need to fix test cases also and the implementation,

Re: Accessibility scope of variables in Java packages and modules

* I am not pen downing things, but yea I am really full on high energy to work on these front. Thanks & Regards, -- *Pradhan Yash Sharma* On Mon, Apr 30, 2018 at 11:37 AM, Yash Sharma wrote: > Hello, > > Thank you for the response, I was wondering about the

Re: Accessibility scope of variables in Java packages and modules

Hello, Thank you for the response, I was wondering about the volume of refactoring we can do at each component, so let's apply Divide and Conquer approach for each component upgrading work. I can see a few patterns for the update which I've listed down in my previous mail. We can pick any piece