Re: Proposal to rename specialpurpose to plugins

Thanks Taher, Well done! Jacques Le 11/01/2017 à 11:56, Taher Alkhateeb a écrit : Okay Folks, Done in r1778271. Thank you all for your patience, and you can continue your work on /plugins (the new directory replacing /specialpurpose) Cheers, Taher Alkhateeb On 11/01/17 10:48, Taher

Re: Proposal to rename specialpurpose to plugins

Okay Folks, Done in r1778271. Thank you all for your patience, and you can continue your work on /plugins (the new directory replacing /specialpurpose) Cheers, Taher Alkhateeb On 11/01/17 10:48, Taher Alkhateeb wrote: Hello everyone, Minor correction, sorry for the miscount, the total

Re: Proposal to rename specialpurpose to plugins

Hello everyone, Minor correction, sorry for the miscount, the total number of binding +1 votes is 5 and total number of +1 non-binding votes is 4 Cheers, Taher Alkhateeb On Wed, Jan 11, 2017 at 10:28 AM, Taher Alkhateeb < slidingfilame...@gmail.com> wrote: > +1 > > Thank you everyone for your

Re: Proposal to rename specialpurpose to plugins

+1 Thank you everyone for your feedback. I count 9 binding +1 votes (including me), one +0 binding vote, and and -1 non-binding vote. I will proceed with the name change today and link it to OFBIZ-7972. If you have any work on /specialpurpose, may I ask to postpone it for a day or two until the

Re: Proposal to rename specialpurpose to plugins

+1 to rename as plugins On Mon, Jan 9, 2017 at 12:23 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Thanks for the update Nicolas > > Jacques > > > > Le 09/01/2017 à 11:04, Nicolas Malin a écrit : > >> +1 to change specialpurpose. >> >> For remove hot-deploy, I prefer wait to have

Re: Proposal to rename specialpurpose to plugins

Thanks for the update Nicolas Jacques Le 09/01/2017 à 11:04, Nicolas Malin a écrit : +1 to change specialpurpose. For remove hot-deploy, I prefer wait to have a good namespace management to identify correctly the origin of each plugin. I work with Jacques on the

Re: Proposal to rename specialpurpose to plugins

+1 to change specialpurpose. For remove hot-deploy, I prefer wait to have a good namespace management to identify correctly the origin of each plugin. I work with Jacques on the https://issues.apache.org/jira/browse/OFBIZ-6919 but I take to much time to finish this task, so I think you can

Re: Issue with Gradle [was Re: Proposal to rename specialpurpose to plugins]

Perhaps this might be relevant? https://issues.gradle.org/browse/GRADLE-1801 On Tue, Jan 3, 2017 at 2:50 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Moving Gradle to another location worked for "gradlew eclipse" but again > not for "gradlew cleanGradle " > > Microsoft Windows

Re: Issue with Gradle [was Re: Proposal to rename specialpurpose to plugins]

Moving Gradle to another location worked for "gradlew eclipse" but again not for "gradlew cleanGradle " Microsoft Windows [version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. Tous droits réservés. C:\projectsASF\ofbiz>g eclipse C:\projectsASF\ofbiz>gradlew eclipse Downloading

Issue with Gradle [was Re: Proposal to rename specialpurpose to plugins]

Even deleting the whole C:\Users\Jacques\.gradle does not work :-o This is creasy :/ C:\projectsASF\ofbiz>svn up && gradlew cleanAll eclipse loadDefault testIntegration Mise à jour de '.' : À la révision 1777109. Downloading https://services.gradle.org/distributions/gradle-3.2.1-bin.zip

Re: Proposal to rename specialpurpose to plugins

Hi Jacques, may I suggest to keep the discussion to this topic. You can start a new thread for the issues you're facing with gradle. On Tue, Jan 3, 2017 at 1:34 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > This turns to be insane, after deleting the whole Gradle caches and >

Re: Proposal to rename specialpurpose to plugins

This turns to be insane, after deleting the whole Gradle caches and rebooting my machine (was still not working after I DLed the new cache) it was still not working I have tried to delete C:\projectsASF\ofbiz\.gradle\3.2.1\taskArtifacts\taskArtifacts.lock but then Gradle create it again on

Re: Proposal to rename specialpurpose to plugins

On Tue, Jan 3, 2017 at 8:57 AM, Pierre Smits wrote: > It will increase the workload on our volunteers > contributing, as the impact is far reaching: not only our documentation > must be revisited, but also elements in JIRA must be renamed. Our potential > adopters, and

Re: Proposal to rename specialpurpose to plugins

Moreover while svn updating I just got a merge issue with recent lucene changes, then an Eclipse issue (I had it open) and then it seems I have to remove all Gradle caches, got this

Re: Proposal to rename specialpurpose to plugins

Sure Jacques, I'll wait for you and this thread is under discussion anyway On Tue, Jan 3, 2017 at 12:32 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Taher, > > Could you please just wait 1 day or 2, maybe more? > > I'm currently working on

Re: Proposal to rename specialpurpose to plugins

+1 In general I think that the word 'plugins' will have more meaning to people than 'specialpurpose'. Thanks Sharan On 2017-01-02 17:45 (+0100), Taher Alkhateeb wrote: > Hello Everyone, > > In reference to earlier discussions and threads on the above subject, I

Re: Proposal to rename specialpurpose to plugins

Taher, Could you please just wait 1 day or 2, maybe more? I'm currently working on https://issues.apache.org/jira/browse/OFBIZ-6919 and its subtasks (a new one is ready but not created). and would prefer to apply these patch before yours because it's a huge thing and mixing both will not help.

Re: Proposal to rename specialpurpose to plugins

> > So I think what this means is whether you rename or not most of the > specialpurpose documentation will be irrelevant anyway if we apply this > strategy. Well yes and no. If I expect to find something under specialpurpose and it turns out to contain just a README file then I'll read that

Re: Proposal to rename specialpurpose to plugins

I will try to exclude some useless dependencies in solr lib later. BTW, is there any tool to find dependencies conflicts in gradle? -邮件原件- 发件人: Taher Alkhateeb [mailto:slidingfilame...@gmail.com] 发送时间: 2017年1月3日 13:57 收件人: OFBIZ Development Mailing List 主题: Re: Proposal to rename

Re: Proposal to rename specialpurpose to plugins

+1. Personally, I support the efforts to slim down OFBiz. I think lightweight will give us more flexibility. -邮件原件- 发件人: Taher Alkhateeb [mailto:slidingfilame...@gmail.com] 发送时间: 2017年1月3日 0:45 收件人: OFBIZ Development Mailing List 主题: Proposal to rename specialpurpose to plugins Hello

Re: Proposal to rename specialpurpose to plugins

+0 James taher wrote > Hello Everyone, > > In reference to earlier discussions and threads on the above subject, I am > hereby proposing renaming the directory "specialpurpose" to "plugins". I > have patch ready with all tests passing. > > Ref discussion: >

Re: Proposal to rename specialpurpose to plugins

+1 Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com On Mon, Jan 2, 2017 at 10:15 PM, Taher Alkhateeb wrote: > Hello Everyone, > > In reference to earlier discussions and threads on the above subject, I am > hereby proposing renaming the directory

Re: Proposal to rename specialpurpose to plugins

-1 This serves no other purpose than renaming for the sake of renaming and brings no added value. It will increase the workload on our volunteers contributing, as the impact is far reaching: not only our documentation must be revisited, but also elements in JIRA must be renamed. Our potential

Re: Proposal to rename specialpurpose to plugins

+1 Jacopo On Mon, Jan 2, 2017 at 5:45 PM, Taher Alkhateeb wrote: > Hello Everyone, > > In reference to earlier discussions and threads on the above subject, I am > hereby proposing renaming the directory "specialpurpose" to "plugins". I > have patch ready with all

Re: Proposal to rename specialpurpose to plugins

Hi Scott and All, Recalling earlier discussions, one of the important reasons for creating the plug-in manager is to remove non-core components (perhaps to a separate repo) from OFBiz while having the ability to maintain them easily (i.e. the build system takes care of downloading and

Re: Proposal to rename specialpurpose to plugins

Ok thanks, it just wasn't clear to me. My only concern with renaming it just for the sake of renaming it is that we have to make sure our documentation reflects the change and we have to be aware that anyone searching our email archives is going to be confused about constant references to a

Re: Proposal to rename specialpurpose to plugins

Hi Scott, I don't know, it depends on what people prefer. We can either delete the component-load.xml in /plugins and remove hot-deploy, or keep the component-load.xml and hot-deploy. I lean slightly towards the former but no strong opinion. I think one thing at a time though. The focus now is

Re: Proposal to rename specialpurpose to plugins

What's the plan for the hot-deploy folder? Remove it? Regards Scott On 3 January 2017 at 08:26, gil portenseigne wrote: > +1 > > Gil > > > > On 02/01/2017 17:45, Taher Alkhateeb wrote: > >> Hello Everyone, >> >> In reference to earlier discussions and threads on

Re: Proposal to rename specialpurpose to plugins

+1 Gil On 02/01/2017 17:45, Taher Alkhateeb wrote: Hello Everyone, In reference to earlier discussions and threads on the above subject, I am hereby proposing renaming the directory "specialpurpose" to "plugins". I have patch ready with all tests passing. Ref discussion:

Re: Proposal to rename specialpurpose to plugins

+1 Jacques Le 02/01/2017 à 17:45, Taher Alkhateeb a écrit : Hello Everyone, In reference to earlier discussions and threads on the above subject, I am hereby proposing renaming the directory "specialpurpose" to "plugins". I have patch ready with all tests passing. Ref discussion: