Re: [DISCUSSION] Plugins: svn:external or Gradle Task? (was Re: Proposal to create a separate svn repository for the OFBiz official plugins)

On Sun, Feb 12, 2017 at 1:32 PM, Taher Alkhateeb wrote: > Let's take a look at the big picture for a moment before we decide. We have > broken OFBiz into essentially two products: framework and plugins. > > Why did we break it up? Why did we go through the trouble of

Re: Proposal to create a separate svn repository for the OFBiz official plugins

In 13.07 we totally removed all the specialpurposes component except ecommerce. Now here we are managing all the specialpurpose component in separate repo. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com On Sun, Feb 12, 2017 at 6:24 PM, Taher Alkhateeb wrote:

Re: [DISCUSSION] Plugins: svn:external or Gradle Task? (was Re: Proposal to create a separate svn repository for the OFBiz official plugins)

I agree with Taher, We have to keep both framework and plugins separately. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com On Sun, Feb 12, 2017 at 6:02 PM, Taher Alkhateeb wrote: > Let's take a look at the big picture for a moment before we decide. We have

Re: Proposal to create a separate svn repository for the OFBiz official plugins

What does 13.07 have anything to do with this? On Feb 12, 2017 3:49 PM, "Jacques Le Roux" wrote: That can be done but I think we need 1st to discuss the political implications and everybody needs to well understand them We must avoid the R13.07 "fiasco" Jacques

Re: Proposal to create a separate svn repository for the OFBiz official plugins

That can be done but I think we need 1st to discuss the political implications and everybody needs to well understand them We must avoid the R13.07 "fiasco" Jacques Le 12/02/2017 à 13:15, Deepak Dixit a écrit : I think we can setup svn:ignore similar to hot-deploy. Thanks & Regards --

Re: [DISCUSSION] Plugins: svn:external or Gradle Task? (was Re: Proposal to create a separate svn repository for the OFBiz official plugins)

Let's take a look at the big picture for a moment before we decide. We have broken OFBiz into essentially two products: framework and plugins. Why did we break it up? Why did we go through the trouble of creating two different repositories? I hope the answer is something like "because it is too

Re: Proposal to create a separate svn repository for the OFBiz official plugins

I think we can setup svn:ignore similar to hot-deploy. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com On Sun, Feb 12, 2017 at 5:31 PM, Taher Alkhateeb wrote: > I'm not sure, but I think we should set up subversion to ignore the plugins > directory except

Re: Proposal to create a separate svn repository for the OFBiz official plugins

I'm not sure, but I think we should set up subversion to ignore the plugins directory except for the README file. On Sun, Feb 12, 2017 at 2:30 PM, Taher Alkhateeb wrote: > Great work Deepak! Thank you. > > On Sun, Feb 12, 2017 at 2:00 PM, Jacques Le Roux < >

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Great work Deepak! Thank you. On Sun, Feb 12, 2017 at 2:00 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Deepak, > > All sounds good to me, thanks. I know you have created a > beforeSvnRestructuring tag as Taher suggested (we exchanged directly) > I have asked infra for possible

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Deepak, All sounds good to me, thanks. I know you have created a beforeSvnRestructuring tag as Taher suggested (we exchanged directly) I have asked infra for possible Github mirror best practices, here is Daniel's answer Daniel Gruno (Humbedooh)·11:54 AM: normally, git accounts for this in

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Thanks Jacques. Restructuring done at r#1782651 and r#1782652 Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com On Sun, Feb 12, 2017 at 3:56 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > OK, I'll start a discussion on this point ASAP > > Jacques > > > > Le 12/02/2017 à

[DISCUSSION] Plugins: svn:external or Gradle Task? (was Re: Proposal to create a separate svn repository for the OFBiz official plugins)

Hi All, This discussion already happened at OFBIZ-9182, but only between Taher, Nicolas and I. The question is simple, below reflects it, and the subject summarises it. So what are your thoughts and opinions? Also when answering I guess we can remove '(was Re: Proposal to create a separate

Re: Proposal to create a separate svn repository for the OFBiz official plugins

OK, I'll start a discussion on this point ASAP Jacques Le 12/02/2017 à 11:22, Jacques Le Roux a écrit : Sincerely I hardly see the benefit, but I see the disadvantages when I remember what happened with R13.07. I mean how and by who will be maintained the OOTB plugins? I think this should

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Sincerely I hardly see the benefit, but I see the disadvantages when I remember what happened with R13.07. I mean how and by who will be maintained the OOTB plugins? I think this should be more discussed, and maybe voted, here Jacques Le 12/02/2017 à 11:18, Deepak Dixit a écrit : Hi

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Hi Jacques, I think we can proceed with restructuring, as we can set/remove svn external at later stage as well. So its not an blocker for restructuring. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com On Sun, Feb 12, 2017 at 3:48 PM, Deepak Dixit < deepak.di...@hotwaxsystems.com> wrote:

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Sure Jacques. Let me check.. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com On Sun, Feb 12, 2017 at 3:51 PM, Deepak Dixit < deepak.di...@hotwaxsystems.com> wrote: > Hi Jacques, > > I think we can proceed with restructuring, as we can set/remove svn > external at later stage as well. So

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Yes, right Deepak Will you handle it ? Jacques Le 12/02/2017 à 10:33, Deepak Dixit a écrit : Hi Jacques, We don't need to delete plugins from trunk as svn move will move this to destination. So first move plugins from trunk to new structure and then move trunk to new location. So sequence

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Hi Jacques, We can add gradle task to pull all plugins from remote. As we are de-coupling plugins from core so I think its good idea to keep them separate. If any committer or developer want he can use gradle task for the same. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com On Sun, Feb

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Yes this is the idea, why should we not? How else committers will easily maintain the plugins? Jacques Le 12/02/2017 à 10:25, Deepak Dixit a écrit : Hi Jacques, I think if we svn:external on trunk, then it will always checkout the plugins with trunk Thanks & Regards -- Deepak Dixit

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Hi Taher, I think adding a tag is a good idea which missed in my proposition Jacques Le 12/02/2017 à 10:14, Taher Alkhateeb a écrit : Hi Deepak, Thank you for helping out! To me the challenge now is figuring out how to do the restructure. Do we move? copy and dump? or some other strategy

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Hi Jacques, We don't need to delete plugins from trunk as svn move will move this to destination. So first move plugins from trunk to new structure and then move trunk to new location. So sequence should be like following: svn move -m "Moves plugins and creates the new structure"

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Hi Jacques, I think if we svn:external on trunk, then it will always checkout the plugins with trunk Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com On Sun, Feb 12, 2017 at 2:52 PM, Deepak Dixit < deepak.di...@hotwaxsystems.com> wrote: > Hi Taher, > > We can directly use svn mv command

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Hi Taher, We can directly use svn mv command to restructure. It will retail svn history. It will automatically create new directory/folder in destination if not present. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com On Sun, Feb 12, 2017 at 2:44 PM, Taher Alkhateeb

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Hi, As it was discussed, I assume ofbiz-framework contains also applications. So I agree with the proposed structure and the move. I note that the proposed structure is also good for next created branches for releases and such. If we use svn move we should not lose history. This explains it:

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Hi Deepak, Thank you for helping out! To me the challenge now is figuring out how to do the restructure. Do we move? copy and dump? or some other strategy [1]. What happens to the subversion history? Should we add a tag that perhaps says "before_restructuring_svn" for example? We also need to

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Hi Taher, I am willing to help, Please let me know how can I help in this effort? Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com On Sat, Feb 11, 2017 at 7:18 PM, Taher Alkhateeb wrote: > Hello Folks, > > We are ready now to finally restructure our

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Hello Folks, We are ready now to finally restructure our subversion repositories. This requires the following: - Move everything except plugins from http://svn.apache.org/repos/asf/ofbiz/trunk to http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk - Move the plugins directory to a new

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Thanks Taher, Jacques Le 31/01/2017 à 15:12, Taher Alkhateeb a écrit : The plugins are already published as zip archives in the implementation On Jan 31, 2017 5:09 PM, "Jacques Le Roux" wrote: Hi Jinghai, Taher, Taher, what do you think agout Jinghais

Re: Proposal to create a separate svn repository for the OFBiz official plugins

The plugins are already published as zip archives in the implementation On Jan 31, 2017 5:09 PM, "Jacques Le Roux" wrote: > Hi Jinghai, Taher, > > Taher, what do you think agout Jinghais proposition? > > Jinghai, if nobody opposes the idea, would you mind creating

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Hi Jinghai, Taher, Taher, what do you think agout Jinghais proposition? Jinghai, if nobody opposes the idea, would you mind creating a Jira? Thanks Jacques Le 13/01/2017 à 11:09, Jacques Le Roux a écrit : That's an interesting proposition ans should be considered indeed Thanks Jinghai

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Thank you all very much for your votes and participation. I think this request pretty much got approval from everyone who participated. I will apply everything in the proposal with a minor change in reference to a related discussion here -> https://s.apache.org/yLpE The change is to relocate

Re: Proposal to create a separate svn repository for the OFBiz official plugins

+1 to the svn folder structure. and I like separation between ofbiz-framework and ofbiz-core Le 12/01/2017 à 09:13, Jacopo Cappellato a écrit : > On Thu, Jan 12, 2017 at 7:40 AM, Nicolas Malin > wrote: > >> Why prepare the future in the same time to rename ofbiz as

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Actually you already spoke about it at http://markmail.org/message/tww4jaoy2a3l5ghs Jacques Le 13/01/2017 à 11:02, Jacques Le Roux a écrit : HI Taher, OK I forgot that with Gradle we no longer worry about dependencies between components/plugins (is that good, future will tell...) But my

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Le 13/01/2017 à 10:35, Jacques Le Roux a écrit : Le 12/01/2017 à 07:28, Jacopo Cappellato a écrit : On Wed, Jan 11, 2017 at 6:54 PM, Pierre Smits wrote: We could also consider to have for each component a separate ASF git repo that replicates to external repo

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Le 13/01/2017 à 10:56, Jacques Le Roux a écrit : Le 12/01/2017 à 09:31, Nicolas Malin a écrit : Le 12/01/2017 à 09:13, Jacopo Cappellato a écrit : On Thu, Jan 12, 2017 at 7:40 AM, Nicolas Malin wrote: Why prepare the future in the same time to rename ofbiz as

Re: Proposal to create a separate svn repository for the OFBiz official plugins

That's an interesting proposition ans should be considered indeed Thanks Jinghai Jacques Le 12/01/2017 à 02:01, Shi Jinghai a écrit : +1 to the svn folder structure. On the plugin publish and install, could we consider publish a zip file to maven repository as well as the jars? In

Re: Proposal to create a separate svn repository for the OFBiz official plugins

HI Taher, OK I forgot that with Gradle we no longer worry about dependencies between components/plugins (is that good, future will tell...) But my question stands Jacques Le 13/01/2017 à 10:38, Taher Alkhateeb a écrit : Hi Jacques, Sorry I'm a little confused I don't understand what you

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Le 12/01/2017 à 09:31, Nicolas Malin a écrit : Le 12/01/2017 à 09:13, Jacopo Cappellato a écrit : On Thu, Jan 12, 2017 at 7:40 AM, Nicolas Malin wrote: Why prepare the future in the same time to rename ofbiz as ofbiz-core ? Like that we would have :

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Hi Jacques, Sorry I'm a little confused I don't understand what you mean. What are you suggesting to do exactly? Regarding the comment "Our goal is to have no dependencies between plugins" is the opposite of what the plugin system offers. The plugin system specifically allows you to define

Re: Proposal to create a separate svn repository for the OFBiz official plugins

That's an important point indeed, have we not Jiras or else where the status/efforts are currently known? Jacques Le 12/01/2017 à 10:12, Pierre Smits a écrit : Before this is executed we should decide whether there are any components of which we feel that they should go to the attic.

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Le 12/01/2017 à 07:28, Jacopo Cappellato a écrit : On Wed, Jan 11, 2017 at 6:54 PM, Pierre Smits wrote: We could also consider to have for each component a separate ASF git repo that replicates to external repo structures like GitHub. Agreed. it would be a natural

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Le 11/01/2017 à 16:01, Taher Alkhateeb a écrit : 3- Remove /plugins/component-load.xml (any component in /plugins will load automatically if it is enabled in ofbiz-component.xml) Could we not rather use the hot-deploy mechanism in plugins and use ofbiz-component.xml only when dependencies

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Before this is executed we should decide whether there are any components of which we feel that they should go to the attic. Otherwise we would be moving stuff around that needn't be moved. Best regards, Pierre Smits ORRTIZ.COM OFBiz based solutions & services OFBiz

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Le 12/01/2017 à 09:13, Jacopo Cappellato a écrit : On Thu, Jan 12, 2017 at 7:40 AM, Nicolas Malin wrote: Why prepare the future in the same time to rename ofbiz as ofbiz-core ? Like that we would have : http://svn.apache.org/repos/asf/ofbiz/ofbiz-core

Re: Proposal to create a separate svn repository for the OFBiz official plugins

On Thu, Jan 12, 2017 at 7:40 AM, Nicolas Malin wrote: > Why prepare the future in the same time to rename ofbiz as ofbiz-core ? > Like that we would have : > http://svn.apache.org/repos/asf/ofbiz/ofbiz-core > http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugin I like

Re: Proposal to create a separate svn repository for the OFBiz official plugins

We can see this on second time to improve the taher's suggest task pullPluginSource with list different repository on the build.gradle But by default only the official repository source code can be listed. Nicolas Le 11/01/2017 à 18:54, Pierre Smits a écrit : We could also consider to have

Re: Proposal to create a separate svn repository for the OFBiz official plugins

I like the idea of ofbiz-core Nicolas On Jan 12, 2017 9:49 AM, "Nicolas Malin" wrote: > Hi Taher > > > Le 11/01/2017 à 16:01, Taher Alkhateeb a écrit : > >> Hello Folks >> >> This is a proposal to the community to restructure our SVN repository. We >> do this by

Re: Proposal to create a separate svn repository for the OFBiz official plugins

Hi Taher Le 11/01/2017 à 16:01, Taher Alkhateeb a écrit : Hello Folks This is a proposal to the community to restructure our SVN repository. We do this by separating "official" plugins from the core OFBiz framework and to provide build script tasks to easily download and install these

Re: Proposal to create a separate svn repository for the OFBiz official plugins

+1 -- Kind Regards Ashish Vijaywargiya HotWax Systems - est. 1997 On Wed, Jan 11, 2017 at 8:31 PM, Taher Alkhateeb wrote: > Hello Folks > > This is a proposal to the community to restructure our SVN repository. We > do this by separating "official" plugins from

Re: Proposal to create a separate svn repository for the OFBiz official plugins

On Wed, Jan 11, 2017 at 6:54 PM, Pierre Smits wrote: > We could also consider to have for each component a separate ASF git repo > that replicates to external repo structures like GitHub. +1 Best regards, Pranay Pandey HotWax Systems http://www.hotwaxsystems.com/ On

Re: Proposal to create a separate svn repository for the OFBiz official plugins

On Wed, Jan 11, 2017 at 6:54 PM, Pierre Smits wrote: > We could also consider to have for each component a separate ASF git repo > that replicates to external repo structures like GitHub. Agreed. it would be a natural consequence of the new layout and we should

Re: Proposal to create a separate svn repository for the OFBiz official plugins

+1 for the proposal from Taher. Best regards, Pranay Pandey HotWax Systems http://www.hotwaxsystems.com/ On Wed, Jan 11, 2017 at 8:31 PM, Taher Alkhateeb wrote: > Hello Folks > > This is a proposal to the community to restructure our SVN repository. We > do this

Re: Proposal to create a separate svn repository for the OFBiz official plugins

+1 for directory structure and OFBiz plugin management. -- Thanks & Regards --- Arun Patidar Manager,Enterprise Software Development HotWax Mediawww.hotwaxsystems.com On Thu, Jan 12, 2017 at 10:34 AM, Gavin Mabie wrote: > +1 Like it > Gavin > > On Thu, Jan 12, 2017 at

Re: Proposal to create a separate svn repository for the OFBiz official plugins

+1 Like it Gavin On Thu, Jan 12, 2017 at 7:00 AM, Deepak Dixit < deepak.di...@hotwaxsystems.com> wrote: > +1 for the svn folder structure. > > Thanks & Regards > -- > Deepak Dixit > www.hotwaxsystems.com > > On Thu, Jan 12, 2017 at 6:31 AM, Shi Jinghai wrote: > > > +1 to

Re: Proposal to create a separate svn repository for the OFBiz official plugins

+1 for the svn folder structure. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com On Thu, Jan 12, 2017 at 6:31 AM, Shi Jinghai wrote: > +1 to the svn folder structure. > > On the plugin publish and install, could we consider publish a zip file to > maven repository

Re: Proposal to create a separate svn repository for the OFBiz official plugins

+1 to the svn folder structure. On the plugin publish and install, could we consider publish a zip file to maven repository as well as the jars? In production environment, unzip the zip file under plugins and then it can work, or even better, don't unzip it, let it work similar to an android

Re: Proposal to create a separate svn repository for the OFBiz official plugins

We could also consider to have for each component a separate ASF git repo that replicates to external repo structures like GitHub. This would increase exposure and potentially attract more contributors as subject matter experts. Best regards, Pierre Smits ORRTIZ.COM

Re: Proposal to create a separate svn repository for the OFBiz official plugins

I agree with the svn layout that Taher is proposing which is also inline with what other Apache projects are doing (see for example [*]). The idea behind these layouts is that the top level folder is for the "project" and its subfolders are for the project's products: project/product1