Re: [SURVEY] Name for the task which load demo and all data

2017-06-15 Thread Jacques Le Roux
Ah OK, that's the point I did not get. So we would use instead gradlew 'ofbiz --load-data' 'ofbiz --test' or abbreviations, sounds good to me. I think we still should ask at least on dev ML before removing. And of course update everywhere it's needed. Jacques Le 15/06/2017 à 14:02, Taher

Re: [SURVEY] Name for the task which load demo and all data

2017-06-15 Thread Taher Alkhateeb
No problem in renaming. Why would you move these tasks to tools? That's another weird thing! The idea is to delete them, not move them! On Jun 15, 2017 2:55 PM, "Jacques Le Roux" wrote: 1) rename loadDefault by loadAll 2) ask if we want to remove loadAll and

Re: [SURVEY] Name for the task which load demo and all data

2017-06-15 Thread Jacques Le Roux
1) rename loadDefault by loadAll 2) ask if we want to remove loadAll and testIntegration Gradle tasks and replace them by creating loadAll and testIntegration scripts in tools branch. "Moving" Gradle tasks to tools is complicating things for everybody (notably committers), hence should be

Re: [SURVEY] Name for the task which load demo and all data

2017-06-15 Thread Taher Alkhateeb
Why would removing it complicate things while removing testIntegration is okay? I don't understand? On Jun 15, 2017 12:48 PM, "Jacques Le Roux" wrote: In my mind it's 2 steps (in the 2nd we would move loadAll to tools) but I'm not much for that, because it

Re: [SURVEY] Name for the task which load demo and all data

2017-06-15 Thread Jacques Le Roux
In my mind it's 2 steps (in the 2nd we would move loadAll to tools) but I'm not much for that, because it complicate things for everybody, not only committers Jacques Le 15/06/2017 à 11:23, Taher Alkhateeb a écrit : I am afraid you misunderstood my suggestion. I suggested removing all

Re: [SURVEY] Name for the task which load demo and all data

2017-06-15 Thread Taher Alkhateeb
I am afraid you misunderstood my suggestion. I suggested removing all shortcut tasks, not renaming them. So either remove everything, or rename loadDefault. What you want to do as I undsrstand is rename loadDefault and remove testIntegration. Weird choice! On Jun 15, 2017 12:03 PM, "Jacques Le

Re: [SURVEY] Name for the task which load demo and all data

2017-06-15 Thread Michael Brohl
Hi Jacques, Am 15.06.17 um 11:03 schrieb Jacques Le Roux: Hi, It's near a month I suggested to rename loadDefault by loadAll without negative comments I'm fine with this. We should promptly update all documentation and wiki pages accordingly to prevent confusion and unneccessary questions

Re: [SURVEY] Name for the task which load demo and all data

2017-06-15 Thread Jacques Le Roux
Hi, It's near a month I suggested to rename loadDefault by loadAll without negative comments So I'll do it soon and will then ask if we want to move the 2 Gradle tasks "testIntegration" and "loadDefault" as scripts in the tools branch. Though it's not really the antonym of start, I finally

Re: [SURVEY] Name for the task which load demo and all data

2017-05-20 Thread Jacques Le Roux
OK, we partly came to something unexpected :) There is obviously a majority, in those who answered to the "survey", to prefer loadAll So I suggest that we rename loadDefault to loadAll And then decide if we want to move the 2 Gradle tasks "testIntegration" and "loadDefault" as scripts in the

Re: [SURVEY] Name for the task which load demo and all data

2017-05-15 Thread Paul Mandeltort
Agreed! As a user who mainly pokes through at the top level scripts to integrate with the rest of my systems, this would be the most clear approach when looking at existing scripts. —P > On May 15, 2017, at 10:40 AM, Taher Alkhateeb > wrote: > > Beautifully said

Re: [SURVEY] Name for the task which load demo and all data

2017-05-15 Thread Taher Alkhateeb
Beautifully said Mike! When we switched to gradle, we dropped all "shortcut" tasks (ant targets) and exposed users directly to the server, thereby combining and issuing commands however the user desires. The only shortcut tasks we left in are "testIntegration" and "loadDefault" because we should

Re: [SURVEY] Name for the task which load demo and all data

2017-05-15 Thread Todd Thorner
I'm in agreement with the last two posts of this thread. I'm not a contributor, though, so there's that whole armchair QB thing going on from my end. On 17-05-15 08:12 AM, Mike wrote: gradlew "ofbiz --load-data readers=seed,seed-initial,ext,ext-demo" Just leave it "as-is". These are

Re: [SURVEY] Name for the task which load demo and all data

2017-05-15 Thread Mike
gradlew "ofbiz --load-data readers=seed,seed-initial,ext,ext-demo" Just leave it "as-is". These are historical. There is nothing gained but more confusion and out-dating of existing documentation. On Sun, May 14, 2017 at 10:34 PM, Paul Foxworthy wrote: > Hi all, > > At

Re: [SURVEY] Name for the task which load demo and all data

2017-05-14 Thread Paul Foxworthy
Hi all, At the risk of bikeshedding... The "data" is redundant. What else would you "load" but "data"? loadAll 1 (best) loadDefault 2 loadAllData 3 loadData 4 (worst) loadData should be infinity. It's meaningless. Cheers Paul Foxworthy On 13 May 2017 at 02:45, Paul Mandeltort

Re: [SURVEY] Name for the task which load demo and all data

2017-05-12 Thread Paul Mandeltort
Sorry, I’m being a jerk and not following your directions so feel free to ignore me, but some unsolicited advice :-) The proposed terms are still ambiguous. One of OFBiz’s biggest problems is there’s a lot of shorthand and ambiguity which makes it really hard for someone who occasionally digs

[SURVEY] Name for the task which load demo and all data

2017-05-12 Thread Jacques Le Roux
Hi, Following the discussion in this thread https://s.apache.org/9PBV we agreed to change the name of the Gradle task which load demo and all data. Before Gradle it was load-demo. It's currently loadDefault and in the discussion came loadAll, loadData and loadAllData. So I propose an