Re: Purchase Order Cancel status

Le 09/10/2017 à 11:10, Arun Patidar a écrit : IMO, we should keep SO and PO consistent in this workflow. Also, there is less chance to add item after canceling all item. To keep order status sync with items, we should cancel the order if all items have been canceled. Agreed, better to create a

Re: svn commit: r1811699 - /ofbiz/ofbiz-framework/trunk/framework/service/src/main/java/org/apache/ofb iz/service/config/model/ThreadPool.java

Le 10/10/2017 à 15:46, mbr...@apache.org a écrit : public static final int MAX_THREADS = 5; // Values higher than 5 might slow things down. Hi While reviewing recent Michael's commits (thanks Michael and the ecomify team) I stumbled upon this static variable I know it's only a default, but

Re: Planning for the creation of the new 17.xx branch(es)

Hi Taher, At 1s glance, I can't see any problems with individual plugins releases: +1 Jacques Le 10/10/2017 à 18:33, Taher Alkhateeb a écrit : Hi Jacopo, I recently created a JIRA [1] to finalize the implementation of of gradle to utilize a maven repository provided by Infra [2]. The purpose

Re: Purchase Order Cancel status

To make SO and PO flow consistent and to maintain order header status with its item status. Removed the condition, patch attached in OFBIZ-9838 Thanks Renuka Srishti On Mon, Oct 9, 2017 at 3:20 PM, Suraj Khurana < suraj.khur...@hotwaxsystems.com>

Re: Planning for the creation of the new 17.xx branch(es)

+1, good idea and good timing. -- Thanks & Regards --- Arun Patidar Manager, Enterprise Software Development HotWax Systems Pvt Ltd. www.hotwaxsystems.com On Tue, Oct 10, 2017 at 10:03 PM, Taher Alkhateeb < slidingfilame...@gmail.com> wrote: > Hi Jacopo, > > I recently created a JIRA [1] to

Re: Planning for the creation of the new 17.xx branch(es)

Hi Jacopo, I recently created a JIRA [1] to finalize the implementation of of gradle to utilize a maven repository provided by Infra [2]. The purpose of this maven repository as you may recall from our old discussion [3] is to be able to publish OFBiz plugins as ZIP archives in the repository. So

Re: [Site] things to clean up or improve

Le 28/09/2017 à 22:13, Jacques Le Roux a écrit : Small quirk, when you look at https://cwiki.apache.org/confluence/display/OFBIZ/Documentation#Documentation-End-UserDocumentation    you see 5 dropdowns w/o any indication (I guess it's for each workspaces?). We had something clearer before, when

buildbot success in on ofbiz-trunk-framework-plugins

The Buildbot has detected a restored build on builder ofbiz-trunk-framework-plugins while building . Full details are available at: https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/539 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: lares_ubuntu Build Reas

Re: default-no-eca

Thanks Jacques, I appreciate :) Nicolas Le 09/10/2017 à 19:05, Jacques Le Roux a écrit : Done at r1811571 Jacques Le 04/10/2017 à 17:30, Jacques Le Roux a écrit : Thanks Nicolas, Then I suggest to keep it and document where it's used (in entityengine.xm) with a simple sentence What wou

Re: Planning for the creation of the new 17.xx branch(es)

Hi Jacopo, all, yes, we should definitely plan the next release. Only thinking briefly about it, I would like to have the following things completed before the release: - FindBugs and refactoring tasks (at least most of it, needs two or three rounds of review-and-commit sessions) - the com

Re: Planning for the creation of the new 17.xx branch(es)

+1,  good idea! And yes it is about the right time to start focussing on this. Thanks Sharan On 10/10/17 09:35, Jacopo Cappellato wrote: Hi all, I think it is time to start thinking about if, when, how we should create the new release branch out of the trunk. Actually, for the first time, we

Re: Planning for the creation of the new 17.xx branch(es)

+1. Sounds good to me. -- Thanks and Regards, *Suraj Khurana* | Sr. Enterprise Software Engineer *HotWax Commerce* by *HotWax Systems* Plot no. 80, Scheme no. 78, Vijay Nagar, Indore, M.P. India 452010 On Tue, Oct 10, 2017 at 2:11 PM, Deepak Dixit < deepak.di...@hotwaxsystems.com> wrote: > +1

Re: Planning for the creation of the new 17.xx branch(es)

+1 perfect make sense. release17.11 looks good to me, We have around more then 1.5 month to complete things. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com www.hotwax.co On Tue, Oct 10, 2017 at 1:05 PM, Jacopo Cappellato < jacopo.cappell...@hotwaxsystems.com> wrote: > Hi all, > > I think

Re: Planning for the creation of the new 17.xx branch(es)

+1, that sounds indeed like the right time Jacques Le 10/10/2017 à 10:15, Devanshu Vyas a écrit : +1 Jacopo, I couldn't agree with you more. This is the right time to start planning and this way we can get all things merged in the Trunk so they can be available in the new branch. Thanks & Reg

Re: Planning for the creation of the new 17.xx branch(es)

+1 Jacopo, I couldn't agree with you more. This is the right time to start planning and this way we can get all things merged in the Trunk so they can be available in the new branch. Thanks & Regards, Devanshu Vyas. On Tue, Oct 10, 2017 at 1:36 PM, Swapnil Mane < swapnil.m...@hotwaxsystems.com> w

Re: Planning for the creation of the new 17.xx branch(es)

+1 Jacopo. We have done really good process from last OFBiz 16.11 release. And yes I think, it's a right time to start planning for next release. - Best Regards, Swapnil M Mane On Tue, Oct 10, 2017 at 1:05 PM, Jacopo Cappellato wrote: > Hi all, > > I think it is time to start thinking about i

Planning for the creation of the new 17.xx branch(es)

Hi all, I think it is time to start thinking about if, when, how we should create the new release branch out of the trunk. Actually, for the first time, we should probably create two branches: one for the framework and one for the plugins. What do you think? In my opinion we could try to get all