Proposal to create a separate svn repository for the OFBiz official plugins
Locked
123
123
Re: Proposal to create a separate svn repository for the OFBiz official plugins
 
Administrator
|
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 > www.hotwaxsystems.com > > On Sun, Feb 12, 2017 at 2:52 PM, Deepak Dixit < > [hidden email]> wrote: > >> 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 < >> [hidden email]> wrote: >> >>> 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 figure the >>> actual command itself to create the new repositories. >>> >>> If you can help in this area it would be great, and I can focus on perhaps >>> making sure the plugin API works correctly and updating buildbot. I >>> already >>> have OFBIZ-9182 setup for this task, so perhaps you can work over there on >>> the actual restructuring, putting the commands and your thoughts in place >>> on how to do it exactly. >>> >>> [1] >>> http://stackoverflow.com/questions/360758/moving-a-subversio >>> n-repository-to-another-server#360829 >>> >>> Cheers, >>> >>> Taher Alkhateeb >>> >>> On Sun, Feb 12, 2017 at 11:15 AM, Deepak Dixit < >>> [hidden email]> wrote: >>> >>>> 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 < >>>> [hidden email] >>>>> wrote: >>>>> 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 repository in >>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk >>>>> - Update the references in the website >>>>> https://ofbiz.apache.org/source-repositories.html >>>>> - Update the buildbot scripts (we might as well figure out why it >>> fails >>>>> constantly lately) >>>>> >>>>> Any volunteers to help? >>>>> >>>>> Cheers, >>>>> >>>>> Taher Alkhateeb >>>>> >>>>> On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux < >>>>> [hidden email]> wrote: >>>>> >>>>>> 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" < >>>>> [hidden email]> >>>>>>> wrote: >>>>>>> >>>>>>> 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 >>>>>>>>> >>>>>>>>> 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 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 apk file. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -----邮件原件----- >>>>>>>>>> 发件人: Taher Alkhateeb [mailto:[hidden email]] >>>>>>>>>> 发送时间: 2017年1月11日 23:02 >>>>>>>>>> 收件人: [hidden email] >>>>>>>>>> 主题: Proposal to create a separate svn repository for the OFBiz >>>>> official >>>>>>>>>> plugins >>>>>>>>>> >>>>>>>>>> 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 plugins. The details of this proposal are as follows: >>>>>>>>>> >>>>>>>>>> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ >>> to >>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, >>>>> branches >>>>>>>>>> and tags underneath as is) >>>>>>>>>> 2- Create a new tree under >>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house >>> all >>>>>>>>>> plugins >>>>>>>>>> 3- Remove /plugins/component-load.xml (any component in /plugins >>>> will >>>>>>>>>> load automatically if it is enabled in ofbiz-component.xml) >>>>>>>>>> 4- Create a gradle task with the below syntax. This task >>> downloads >>>> a >>>>>>>>>> plugin from subversion and places it in /plugins and runs any >>>> install >>>>>>>>>> logic >>>>>>>>>> that it may have >>>>>>>>>> Syntax: pullPluginSource -PpluginId=<plugin-id-here> >>>>>>>>>> Example: pullPluginSource -PpluginId=birt >>>>>>>>>> 5- Refactor the build scripts to cater for all the above >>>>>>>>>> 6- Update README.md to reflect all the above >>>>>>>>>> >>>>>>>>>> So for example, under this proposal, trunk is located in: >>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk >>>>>>>>>> >>>>>>>>>> And the birt component is located in: >>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt >>>>>>>>>> >>>>>>>>>> This would allow us to have in the future the ability to provide >>>>>>>>>> releases not only for the framework but the plugins as well as >>> two >>>>>>>>>> separate >>>>>>>>>> products. >>>>>>>>>> >>>>>>>>>> What do you think? >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> >>>>>>>>>> Taher Alkhateeb >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >> |
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 12, 2017 at 3:43 PM, Jacques Le Roux < [hidden email]> wrote: > 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 >> www.hotwaxsystems.com >> >> On Sun, Feb 12, 2017 at 2:52 PM, Deepak Dixit < >> [hidden email]> wrote: >> >> 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 < >>> [hidden email]> wrote: >>> >>> 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 figure the >>>> actual command itself to create the new repositories. >>>> >>>> If you can help in this area it would be great, and I can focus on >>>> perhaps >>>> making sure the plugin API works correctly and updating buildbot. I >>>> already >>>> have OFBIZ-9182 setup for this task, so perhaps you can work over there >>>> on >>>> the actual restructuring, putting the commands and your thoughts in >>>> place >>>> on how to do it exactly. >>>> >>>> [1] >>>> http://stackoverflow.com/questions/360758/moving-a-subversio >>>> n-repository-to-another-server#360829 >>>> >>>> Cheers, >>>> >>>> Taher Alkhateeb >>>> >>>> On Sun, Feb 12, 2017 at 11:15 AM, Deepak Dixit < >>>> [hidden email]> wrote: >>>> >>>> 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 < >>>>> [hidden email] >>>>> >>>>>> wrote: >>>>>> 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 repository in >>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk >>>>>> - Update the references in the website >>>>>> https://ofbiz.apache.org/source-repositories.html >>>>>> - Update the buildbot scripts (we might as well figure out why it >>>>>> >>>>> fails >>>> >>>>> constantly lately) >>>>>> >>>>>> Any volunteers to help? >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Taher Alkhateeb >>>>>> >>>>>> On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux < >>>>>> [hidden email]> wrote: >>>>>> >>>>>> 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" < >>>>>>>> >>>>>>> [hidden email]> >>>>>> >>>>>>> wrote: >>>>>>>> >>>>>>>> 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 >>>>>>>>>> >>>>>>>>>> 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 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 apk file. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -----邮件原件----- >>>>>>>>>>> 发件人: Taher Alkhateeb [mailto:[hidden email]] >>>>>>>>>>> 发送时间: 2017年1月11日 23:02 >>>>>>>>>>> 收件人: [hidden email] >>>>>>>>>>> 主题: Proposal to create a separate svn repository for the OFBiz >>>>>>>>>>> >>>>>>>>>> official >>>>>> >>>>>>> plugins >>>>>>>>>>> >>>>>>>>>>> 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 plugins. The details of this proposal are as follows: >>>>>>>>>>> >>>>>>>>>>> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ >>>>>>>>>>> >>>>>>>>>> to >>>> >>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, >>>>>>>>>>> >>>>>>>>>> branches >>>>>> >>>>>>> and tags underneath as is) >>>>>>>>>>> 2- Create a new tree under >>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house >>>>>>>>>>> >>>>>>>>>> all >>>> >>>>> plugins >>>>>>>>>>> 3- Remove /plugins/component-load.xml (any component in /plugins >>>>>>>>>>> >>>>>>>>>> will >>>>> >>>>>> load automatically if it is enabled in ofbiz-component.xml) >>>>>>>>>>> 4- Create a gradle task with the below syntax. This task >>>>>>>>>>> >>>>>>>>>> downloads >>>> >>>>> a >>>>> >>>>>> plugin from subversion and places it in /plugins and runs any >>>>>>>>>>> >>>>>>>>>> install >>>>> >>>>>> logic >>>>>>>>>>> that it may have >>>>>>>>>>> Syntax: pullPluginSource -PpluginId=<plugin-id-here> >>>>>>>>>>> Example: pullPluginSource -PpluginId=birt >>>>>>>>>>> 5- Refactor the build scripts to cater for all the above >>>>>>>>>>> 6- Update README.md to reflect all the above >>>>>>>>>>> >>>>>>>>>>> So for example, under this proposal, trunk is located in: >>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk >>>>>>>>>>> >>>>>>>>>>> And the birt component is located in: >>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt >>>>>>>>>>> >>>>>>>>>>> This would allow us to have in the future the ability to provide >>>>>>>>>>> releases not only for the framework but the plugins as well as >>>>>>>>>>> >>>>>>>>>> two >>>> >>>>> separate >>>>>>>>>>> products. >>>>>>>>>>> >>>>>>>>>>> What do you think? >>>>>>>>>>> >>>>>>>>>>> Cheers, >>>>>>>>>>> >>>>>>>>>>> Taher Alkhateeb >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>> > |
Re: Proposal to create a separate svn repository for the OFBiz official plugins
|
Administrator
|
In reply to this post by Deepak Dixit-3
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 should be like following: > > svn move -m "Moves plugins and creates the new structure" > https://svn.apache.org/repos/asf/ofbiz/trunk/plugins > http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk > > > svn move -m "Moves plugins and creates the new structure" > https://svn.apache.org/repos/asf/ofbiz/trunkhttp://svn.apache.org/repos/as > f/ofbiz/ofbiz-framework/trunk > > > > Thanks & Regards > -- > Deepak Dixit > www.hotwaxsystems.com > > On Sun, Feb 12, 2017 at 2:48 PM, Jacques Le Roux < > [hidden email]> wrote: > >> 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: "svn help >> rename". So we should use >> >> svn move -m "Moves plugins and creates the new structure" >> https://svn.apache.org/repos/asf/ofbiz/trunk >> http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk >> >> svn move -m "Moves plugins and creates the new structure" >> https://svn.apache.org/repos/asf/ofbiz/trunk/plugins >> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk >> >> Delete plugins from a "trunk" working copy checked out from the new trunk >> location (http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk) >> and commit this change using the same "Moves plugins and creates the new >> structure" comment >> >> Adds and a svn:externals for the plugins using the same "Moves plugins and >> creates the new structure" comment. >> >> By adding a svn:externals, I mean committing, from the "trunk" working >> copy this svn:externals root properties (a line) with a relative path to >> the common parent directory (http://svn.apache.org/repos/asf/ofbiz) >> >> ../../ofbiz-plugins/trunk plugins >> >> I can do it. Please check and confirm my assertions before I do, by >> reading http://svnbook.red-bean.com/en/1.8/svn.advanced.externals.html >> >> Thanks to the svn:externals, we'll have no problems with Buildbot and >> other aspects. Like committing to ofbiz-plugins from the integrated whole. >> Though not recursively, which means committing twice if you have changes in >> ofbiz-framework AND ofbiz-plugins. It's not a big deal IMO, you just have >> to remember it... >> >> Jacques >> >> >> >> >> Le 12/02/2017 à 09:15, Deepak Dixit a écrit : >> >>> 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 < >>> [hidden email] >>> >>>> wrote: >>>> 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 repository in >>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk >>>> - Update the references in the website >>>> https://ofbiz.apache.org/source-repositories.html >>>> - Update the buildbot scripts (we might as well figure out why it fails >>>> constantly lately) >>>> >>>> Any volunteers to help? >>>> >>>> Cheers, >>>> >>>> Taher Alkhateeb >>>> >>>> On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux < >>>> [hidden email]> wrote: >>>> >>>> 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" < >>>>>> >>>>> [hidden email]> >>>>> wrote: >>>>>> 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 >>>>>>>> >>>>>>>> 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 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 apk file. >>>>>>>>> >>>>>>>>> -----邮件原件----- >>>>>>>>> 发件人: Taher Alkhateeb [mailto:[hidden email]] >>>>>>>>> 发送时间: 2017年1月11日 23:02 >>>>>>>>> 收件人: [hidden email] >>>>>>>>> 主题: Proposal to create a separate svn repository for the OFBiz >>>>>>>>> >>>>>>>> official >>>>> plugins >>>>>>>>> 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 plugins. The details of this proposal are as follows: >>>>>>>>> >>>>>>>>> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ to >>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, >>>>>>>>> >>>>>>>> branches >>>>> and tags underneath as is) >>>>>>>>> 2- Create a new tree under >>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house all >>>>>>>>> plugins >>>>>>>>> 3- Remove /plugins/component-load.xml (any component in /plugins >>>>>>>>> will >>>>>>>>> load automatically if it is enabled in ofbiz-component.xml) >>>>>>>>> 4- Create a gradle task with the below syntax. This task downloads a >>>>>>>>> plugin from subversion and places it in /plugins and runs any >>>>>>>>> install >>>>>>>>> logic >>>>>>>>> that it may have >>>>>>>>> Syntax: pullPluginSource -PpluginId=<plugin-id-here> >>>>>>>>> Example: pullPluginSource -PpluginId=birt >>>>>>>>> 5- Refactor the build scripts to cater for all the above >>>>>>>>> 6- Update README.md to reflect all the above >>>>>>>>> >>>>>>>>> So for example, under this proposal, trunk is located in: >>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk >>>>>>>>> >>>>>>>>> And the birt component is located in: >>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt >>>>>>>>> >>>>>>>>> This would allow us to have in the future the ability to provide >>>>>>>>> releases not only for the framework but the plugins as well as two >>>>>>>>> separate >>>>>>>>> products. >>>>>>>>> >>>>>>>>> What do you think? >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> >>>>>>>>> Taher Alkhateeb >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> |
Re: Proposal to create a separate svn repository for the OFBiz official plugins
|
|
In reply to this post by Deepak Dixit-3
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 < [hidden email]> wrote: > 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 12, 2017 at 3:43 PM, Jacques Le Roux < > [hidden email]> wrote: > >> 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 >>> www.hotwaxsystems.com >>> >>> On Sun, Feb 12, 2017 at 2:52 PM, Deepak Dixit < >>> [hidden email]> wrote: >>> >>> 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 < >>>> [hidden email]> wrote: >>>> >>>> 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 figure the >>>>> actual command itself to create the new repositories. >>>>> >>>>> If you can help in this area it would be great, and I can focus on >>>>> perhaps >>>>> making sure the plugin API works correctly and updating buildbot. I >>>>> already >>>>> have OFBIZ-9182 setup for this task, so perhaps you can work over >>>>> there on >>>>> the actual restructuring, putting the commands and your thoughts in >>>>> place >>>>> on how to do it exactly. >>>>> >>>>> [1] >>>>> http://stackoverflow.com/questions/360758/moving-a-subversio >>>>> n-repository-to-another-server#360829 >>>>> >>>>> Cheers, >>>>> >>>>> Taher Alkhateeb >>>>> >>>>> On Sun, Feb 12, 2017 at 11:15 AM, Deepak Dixit < >>>>> [hidden email]> wrote: >>>>> >>>>> 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 < >>>>>> [hidden email] >>>>>> >>>>>>> wrote: >>>>>>> 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 repository in >>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk >>>>>>> - Update the references in the website >>>>>>> https://ofbiz.apache.org/source-repositories.html >>>>>>> - Update the buildbot scripts (we might as well figure out why it >>>>>>> >>>>>> fails >>>>> >>>>>> constantly lately) >>>>>>> >>>>>>> Any volunteers to help? >>>>>>> >>>>>>> Cheers, >>>>>>> >>>>>>> Taher Alkhateeb >>>>>>> >>>>>>> On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux < >>>>>>> [hidden email]> wrote: >>>>>>> >>>>>>> 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" < >>>>>>>>> >>>>>>>> [hidden email]> >>>>>>> >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>>> 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 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 apk file. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -----邮件原件----- >>>>>>>>>>>> 发件人: Taher Alkhateeb [mailto:[hidden email]] >>>>>>>>>>>> 发送时间: 2017年1月11日 23:02 >>>>>>>>>>>> 收件人: [hidden email] >>>>>>>>>>>> 主题: Proposal to create a separate svn repository for the OFBiz >>>>>>>>>>>> >>>>>>>>>>> official >>>>>>> >>>>>>>> plugins >>>>>>>>>>>> >>>>>>>>>>>> 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 plugins. The details of this proposal are as follows: >>>>>>>>>>>> >>>>>>>>>>>> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ >>>>>>>>>>>> >>>>>>>>>>> to >>>>> >>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, >>>>>>>>>>>> >>>>>>>>>>> branches >>>>>>> >>>>>>>> and tags underneath as is) >>>>>>>>>>>> 2- Create a new tree under >>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house >>>>>>>>>>>> >>>>>>>>>>> all >>>>> >>>>>> plugins >>>>>>>>>>>> 3- Remove /plugins/component-load.xml (any component in /plugins >>>>>>>>>>>> >>>>>>>>>>> will >>>>>> >>>>>>> load automatically if it is enabled in ofbiz-component.xml) >>>>>>>>>>>> 4- Create a gradle task with the below syntax. This task >>>>>>>>>>>> >>>>>>>>>>> downloads >>>>> >>>>>> a >>>>>> >>>>>>> plugin from subversion and places it in /plugins and runs any >>>>>>>>>>>> >>>>>>>>>>> install >>>>>> >>>>>>> logic >>>>>>>>>>>> that it may have >>>>>>>>>>>> Syntax: pullPluginSource -PpluginId=<plugin-id-here> >>>>>>>>>>>> Example: pullPluginSource -PpluginId=birt >>>>>>>>>>>> 5- Refactor the build scripts to cater for all the above >>>>>>>>>>>> 6- Update README.md to reflect all the above >>>>>>>>>>>> >>>>>>>>>>>> So for example, under this proposal, trunk is located in: >>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk >>>>>>>>>>>> >>>>>>>>>>>> And the birt component is located in: >>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt >>>>>>>>>>>> >>>>>>>>>>>> This would allow us to have in the future the ability to provide >>>>>>>>>>>> releases not only for the framework but the plugins as well as >>>>>>>>>>>> >>>>>>>>>>> two >>>>> >>>>>> separate >>>>>>>>>>>> products. >>>>>>>>>>>> >>>>>>>>>>>> What do you think? >>>>>>>>>>>> >>>>>>>>>>>> Cheers, >>>>>>>>>>>> >>>>>>>>>>>> Taher Alkhateeb >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>> >> > |
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 < [hidden email]> wrote: > 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.dixit@hotwaxsystems. > com> wrote: > >> 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 12, 2017 at 3:43 PM, Jacques Le Roux < >> [hidden email]> wrote: >> >>> 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 >>>> www.hotwaxsystems.com >>>> >>>> On Sun, Feb 12, 2017 at 2:52 PM, Deepak Dixit < >>>> [hidden email]> wrote: >>>> >>>> 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 < >>>>> [hidden email]> wrote: >>>>> >>>>> 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 figure >>>>>> the >>>>>> actual command itself to create the new repositories. >>>>>> >>>>>> If you can help in this area it would be great, and I can focus on >>>>>> perhaps >>>>>> making sure the plugin API works correctly and updating buildbot. I >>>>>> already >>>>>> have OFBIZ-9182 setup for this task, so perhaps you can work over >>>>>> there on >>>>>> the actual restructuring, putting the commands and your thoughts in >>>>>> place >>>>>> on how to do it exactly. >>>>>> >>>>>> [1] >>>>>> http://stackoverflow.com/questions/360758/moving-a-subversio >>>>>> n-repository-to-another-server#360829 >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Taher Alkhateeb >>>>>> >>>>>> On Sun, Feb 12, 2017 at 11:15 AM, Deepak Dixit < >>>>>> [hidden email]> wrote: >>>>>> >>>>>> 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 < >>>>>>> [hidden email] >>>>>>> >>>>>>>> wrote: >>>>>>>> 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 repository in >>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk >>>>>>>> - Update the references in the website >>>>>>>> https://ofbiz.apache.org/source-repositories.html >>>>>>>> - Update the buildbot scripts (we might as well figure out why it >>>>>>>> >>>>>>> fails >>>>>> >>>>>>> constantly lately) >>>>>>>> >>>>>>>> Any volunteers to help? >>>>>>>> >>>>>>>> Cheers, >>>>>>>> >>>>>>>> Taher Alkhateeb >>>>>>>> >>>>>>>> On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux < >>>>>>>> [hidden email]> wrote: >>>>>>>> >>>>>>>> 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" < >>>>>>>>>> >>>>>>>>> [hidden email]> >>>>>>>> >>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>>> 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 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 apk file. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -----邮件原件----- >>>>>>>>>>>>> 发件人: Taher Alkhateeb [mailto:[hidden email]] >>>>>>>>>>>>> 发送时间: 2017年1月11日 23:02 >>>>>>>>>>>>> 收件人: [hidden email] >>>>>>>>>>>>> 主题: Proposal to create a separate svn repository for the OFBiz >>>>>>>>>>>>> >>>>>>>>>>>> official >>>>>>>> >>>>>>>>> plugins >>>>>>>>>>>>> >>>>>>>>>>>>> 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 plugins. The details of this proposal are as follows: >>>>>>>>>>>>> >>>>>>>>>>>>> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ >>>>>>>>>>>>> >>>>>>>>>>>> to >>>>>> >>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, >>>>>>>>>>>>> >>>>>>>>>>>> branches >>>>>>>> >>>>>>>>> and tags underneath as is) >>>>>>>>>>>>> 2- Create a new tree under >>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house >>>>>>>>>>>>> >>>>>>>>>>>> all >>>>>> >>>>>>> plugins >>>>>>>>>>>>> 3- Remove /plugins/component-load.xml (any component in >>>>>>>>>>>>> /plugins >>>>>>>>>>>>> >>>>>>>>>>>> will >>>>>>> >>>>>>>> load automatically if it is enabled in ofbiz-component.xml) >>>>>>>>>>>>> 4- Create a gradle task with the below syntax. This task >>>>>>>>>>>>> >>>>>>>>>>>> downloads >>>>>> >>>>>>> a >>>>>>> >>>>>>>> plugin from subversion and places it in /plugins and runs any >>>>>>>>>>>>> >>>>>>>>>>>> install >>>>>>> >>>>>>>> logic >>>>>>>>>>>>> that it may have >>>>>>>>>>>>> Syntax: pullPluginSource -PpluginId=<plugin-id-here> >>>>>>>>>>>>> Example: pullPluginSource -PpluginId=birt >>>>>>>>>>>>> 5- Refactor the build scripts to cater for all the above >>>>>>>>>>>>> 6- Update README.md to reflect all the above >>>>>>>>>>>>> >>>>>>>>>>>>> So for example, under this proposal, trunk is located in: >>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk >>>>>>>>>>>>> >>>>>>>>>>>>> And the birt component is located in: >>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt >>>>>>>>>>>>> >>>>>>>>>>>>> This would allow us to have in the future the ability to >>>>>>>>>>>>> provide >>>>>>>>>>>>> releases not only for the framework but the plugins as well as >>>>>>>>>>>>> >>>>>>>>>>>> two >>>>>> >>>>>>> separate >>>>>>>>>>>>> products. >>>>>>>>>>>>> >>>>>>>>>>>>> What do you think? >>>>>>>>>>>>> >>>>>>>>>>>>> Cheers, >>>>>>>>>>>>> >>>>>>>>>>>>> Taher Alkhateeb >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>> >>> >> > |
Re: Proposal to create a separate svn repository for the OFBiz official plugins
|
Administrator
|
In reply to this post by Deepak Dixit-3
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 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 12, 2017 at 3:43 PM, Jacques Le Roux < > [hidden email]> wrote: > >> 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 >>> www.hotwaxsystems.com >>> >>> On Sun, Feb 12, 2017 at 2:52 PM, Deepak Dixit < >>> [hidden email]> wrote: >>> >>> 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 < >>>> [hidden email]> wrote: >>>> >>>> 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 figure the >>>>> actual command itself to create the new repositories. >>>>> >>>>> If you can help in this area it would be great, and I can focus on >>>>> perhaps >>>>> making sure the plugin API works correctly and updating buildbot. I >>>>> already >>>>> have OFBIZ-9182 setup for this task, so perhaps you can work over there >>>>> on >>>>> the actual restructuring, putting the commands and your thoughts in >>>>> place >>>>> on how to do it exactly. >>>>> >>>>> [1] >>>>> http://stackoverflow.com/questions/360758/moving-a-subversio >>>>> n-repository-to-another-server#360829 >>>>> >>>>> Cheers, >>>>> >>>>> Taher Alkhateeb >>>>> >>>>> On Sun, Feb 12, 2017 at 11:15 AM, Deepak Dixit < >>>>> [hidden email]> wrote: >>>>> >>>>> 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 < >>>>>> [hidden email] >>>>>> >>>>>>> wrote: >>>>>>> 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 repository in >>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk >>>>>>> - Update the references in the website >>>>>>> https://ofbiz.apache.org/source-repositories.html >>>>>>> - Update the buildbot scripts (we might as well figure out why it >>>>>>> >>>>>> fails >>>>>> constantly lately) >>>>>>> Any volunteers to help? >>>>>>> >>>>>>> Cheers, >>>>>>> >>>>>>> Taher Alkhateeb >>>>>>> >>>>>>> On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux < >>>>>>> [hidden email]> wrote: >>>>>>> >>>>>>> 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" < >>>>>>>> [hidden email]> >>>>>>>> wrote: >>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>>> 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 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 apk file. >>>>>>>>>>>> >>>>>>>>>>>> -----邮件原件----- >>>>>>>>>>>> 发件人: Taher Alkhateeb [mailto:[hidden email]] >>>>>>>>>>>> 发送时间: 2017年1月11日 23:02 >>>>>>>>>>>> 收件人: [hidden email] >>>>>>>>>>>> 主题: Proposal to create a separate svn repository for the OFBiz >>>>>>>>>>>> >>>>>>>>>>> official >>>>>>>> plugins >>>>>>>>>>>> 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 plugins. The details of this proposal are as follows: >>>>>>>>>>>> >>>>>>>>>>>> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ >>>>>>>>>>>> >>>>>>>>>>> to >>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, >>>>>>>>>>> branches >>>>>>>> and tags underneath as is) >>>>>>>>>>>> 2- Create a new tree under >>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house >>>>>>>>>>>> >>>>>>>>>>> all >>>>>> plugins >>>>>>>>>>>> 3- Remove /plugins/component-load.xml (any component in /plugins >>>>>>>>>>>> >>>>>>>>>>> will >>>>>>> load automatically if it is enabled in ofbiz-component.xml) >>>>>>>>>>>> 4- Create a gradle task with the below syntax. This task >>>>>>>>>>>> >>>>>>>>>>> downloads >>>>>> a >>>>>> >>>>>>> plugin from subversion and places it in /plugins and runs any >>>>>>>>>>> install >>>>>>> logic >>>>>>>>>>>> that it may have >>>>>>>>>>>> Syntax: pullPluginSource -PpluginId=<plugin-id-here> >>>>>>>>>>>> Example: pullPluginSource -PpluginId=birt >>>>>>>>>>>> 5- Refactor the build scripts to cater for all the above >>>>>>>>>>>> 6- Update README.md to reflect all the above >>>>>>>>>>>> >>>>>>>>>>>> So for example, under this proposal, trunk is located in: >>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk >>>>>>>>>>>> >>>>>>>>>>>> And the birt component is located in: >>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt >>>>>>>>>>>> >>>>>>>>>>>> This would allow us to have in the future the ability to provide >>>>>>>>>>>> releases not only for the framework but the plugins as well as >>>>>>>>>>>> >>>>>>>>>>> two >>>>>> separate >>>>>>>>>>>> products. >>>>>>>>>>>> >>>>>>>>>>>> What do you think? >>>>>>>>>>>> >>>>>>>>>>>> Cheers, >>>>>>>>>>>> >>>>>>>>>>>> Taher Alkhateeb >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> > |
Re: Proposal to create a separate svn repository for the OFBiz official plugins
|
Administrator
|
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 be more discussed, and maybe voted, here > > Jacques > > > Le 12/02/2017 à 11:18, Deepak Dixit a écrit : >> 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 12, 2017 at 3:43 PM, Jacques Le Roux < >> [hidden email]> wrote: >> >>> 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 >>>> www.hotwaxsystems.com >>>> >>>> On Sun, Feb 12, 2017 at 2:52 PM, Deepak Dixit < >>>> [hidden email]> wrote: >>>> >>>> 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 < >>>>> [hidden email]> wrote: >>>>> >>>>> 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 figure the >>>>>> actual command itself to create the new repositories. >>>>>> >>>>>> If you can help in this area it would be great, and I can focus on >>>>>> perhaps >>>>>> making sure the plugin API works correctly and updating buildbot. I >>>>>> already >>>>>> have OFBIZ-9182 setup for this task, so perhaps you can work over there >>>>>> on >>>>>> the actual restructuring, putting the commands and your thoughts in >>>>>> place >>>>>> on how to do it exactly. >>>>>> >>>>>> [1] >>>>>> http://stackoverflow.com/questions/360758/moving-a-subversio >>>>>> n-repository-to-another-server#360829 >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Taher Alkhateeb >>>>>> >>>>>> On Sun, Feb 12, 2017 at 11:15 AM, Deepak Dixit < >>>>>> [hidden email]> wrote: >>>>>> >>>>>> 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 < >>>>>>> [hidden email] >>>>>>> >>>>>>>> wrote: >>>>>>>> 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 repository in >>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk >>>>>>>> - Update the references in the website >>>>>>>> https://ofbiz.apache.org/source-repositories.html >>>>>>>> - Update the buildbot scripts (we might as well figure out why it >>>>>>>> >>>>>>> fails >>>>>>> constantly lately) >>>>>>>> Any volunteers to help? >>>>>>>> >>>>>>>> Cheers, >>>>>>>> >>>>>>>> Taher Alkhateeb >>>>>>>> >>>>>>>> On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux < >>>>>>>> [hidden email]> wrote: >>>>>>>> >>>>>>>> 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" < >>>>>>>>> [hidden email]> >>>>>>>>> wrote: >>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>>> 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 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 apk file. >>>>>>>>>>>>> >>>>>>>>>>>>> -----邮件原件----- >>>>>>>>>>>>> 发件人: Taher Alkhateeb [mailto:[hidden email]] >>>>>>>>>>>>> 发送时间: 2017年1月11日 23:02 >>>>>>>>>>>>> 收件人: [hidden email] >>>>>>>>>>>>> 主题: Proposal to create a separate svn repository for the OFBiz >>>>>>>>>>>>> >>>>>>>>>>>> official >>>>>>>>> plugins >>>>>>>>>>>>> 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 plugins. The details of this proposal are as follows: >>>>>>>>>>>>> >>>>>>>>>>>>> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ >>>>>>>>>>>>> >>>>>>>>>>>> to >>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, >>>>>>>>>>>> branches >>>>>>>>> and tags underneath as is) >>>>>>>>>>>>> 2- Create a new tree under >>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house >>>>>>>>>>>>> >>>>>>>>>>>> all >>>>>>> plugins >>>>>>>>>>>>> 3- Remove /plugins/component-load.xml (any component in /plugins >>>>>>>>>>>>> >>>>>>>>>>>> will >>>>>>>> load automatically if it is enabled in ofbiz-component.xml) >>>>>>>>>>>>> 4- Create a gradle task with the below syntax. This task >>>>>>>>>>>>> >>>>>>>>>>>> downloads >>>>>>> a >>>>>>> >>>>>>>> plugin from subversion and places it in /plugins and runs any >>>>>>>>>>>> install >>>>>>>> logic >>>>>>>>>>>>> that it may have >>>>>>>>>>>>> Syntax: pullPluginSource -PpluginId=<plugin-id-here> >>>>>>>>>>>>> Example: pullPluginSource -PpluginId=birt >>>>>>>>>>>>> 5- Refactor the build scripts to cater for all the above >>>>>>>>>>>>> 6- Update README.md to reflect all the above >>>>>>>>>>>>> >>>>>>>>>>>>> So for example, under this proposal, trunk is located in: >>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk >>>>>>>>>>>>> >>>>>>>>>>>>> And the birt component is located in: >>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/birt >>>>>>>>>>>>> >>>>>>>>>>>>> This would allow us to have in the future the ability to provide >>>>>>>>>>>>> releases not only for the framework but the plugins as well as >>>>>>>>>>>>> >>>>>>>>>>>> two >>>>>>> separate >>>>>>>>>>>>> products. >>>>>>>>>>>>> >>>>>>>>>>>>> What do you think? >>>>>>>>>>>>> >>>>>>>>>>>>> Cheers, >>>>>>>>>>>>> >>>>>>>>>>>>> Taher Alkhateeb >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >> > > |
[DISCUSSION] Plugins: svn:external or Gradle Task? (was Re: Proposal to create a separate svn repository for the OFBiz official plugins)
|
Administrator
|
In reply to this post by Jacques Le Roux
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 svn repository for the OFBiz official plugins)' from the subject (I was just "lazy" here) Thanks 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 be more discussed, and maybe voted, here > > Jacques > > > Le 12/02/2017 à 11:18, Deepak Dixit a écrit : >> 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 12, 2017 at 3:43 PM, Jacques Le Roux < >> [hidden email]> wrote: >> >>> 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 >>>> www.hotwaxsystems.com >>>> >>>> On Sun, Feb 12, 2017 at 2:52 PM, Deepak Dixit < >>>> [hidden email]> wrote: |
Re: Proposal to create a separate svn repository for the OFBiz official plugins
|
|
In reply to this post by Jacques Le Roux
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 < [hidden email]> wrote: > 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 be more discussed, and maybe voted, here >> >> Jacques >> >> >> Le 12/02/2017 à 11:18, Deepak Dixit a écrit : >> >>> 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 12, 2017 at 3:43 PM, Jacques Le Roux < >>> [hidden email]> wrote: >>> >>> 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 >>>>> www.hotwaxsystems.com >>>>> >>>>> On Sun, Feb 12, 2017 at 2:52 PM, Deepak Dixit < >>>>> [hidden email]> wrote: >>>>> >>>>> 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 < >>>>>> [hidden email]> wrote: >>>>>> >>>>>> 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 figure >>>>>>> the >>>>>>> actual command itself to create the new repositories. >>>>>>> >>>>>>> If you can help in this area it would be great, and I can focus on >>>>>>> perhaps >>>>>>> making sure the plugin API works correctly and updating buildbot. I >>>>>>> already >>>>>>> have OFBIZ-9182 setup for this task, so perhaps you can work over >>>>>>> there >>>>>>> on >>>>>>> the actual restructuring, putting the commands and your thoughts in >>>>>>> place >>>>>>> on how to do it exactly. >>>>>>> >>>>>>> [1] >>>>>>> http://stackoverflow.com/questions/360758/moving-a-subversio >>>>>>> n-repository-to-another-server#360829 >>>>>>> >>>>>>> Cheers, >>>>>>> >>>>>>> Taher Alkhateeb >>>>>>> >>>>>>> On Sun, Feb 12, 2017 at 11:15 AM, Deepak Dixit < >>>>>>> [hidden email]> wrote: >>>>>>> >>>>>>> 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 < >>>>>>>> [hidden email] >>>>>>>> >>>>>>>> wrote: >>>>>>>>> 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 repository in >>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk >>>>>>>>> - Update the references in the website >>>>>>>>> https://ofbiz.apache.org/source-repositories.html >>>>>>>>> - Update the buildbot scripts (we might as well figure out why it >>>>>>>>> >>>>>>>>> fails >>>>>>>> constantly lately) >>>>>>>> >>>>>>>>> Any volunteers to help? >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> >>>>>>>>> Taher Alkhateeb >>>>>>>>> >>>>>>>>> On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux < >>>>>>>>> [hidden email]> wrote: >>>>>>>>> >>>>>>>>> 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" < >>>>>>>>> >>>>>>>>>> [hidden email]> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> 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 >>>>>>>>>>>>> >>>>>>>>>>>>> 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 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 apk file. >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>>> -----邮件原件----- >>>>>>>>>>>>>> 发件人: Taher Alkhateeb [mailto:[hidden email]] >>>>>>>>>>>>>> 发送时间: 2017年1月11日 23:02 >>>>>>>>>>>>>> 收件人: [hidden email] >>>>>>>>>>>>>> 主题: Proposal to create a separate svn repository for the OFBiz >>>>>>>>>>>>>> >>>>>>>>>>>>>> official >>>>>>>>>>>>> >>>>>>>>>>>> plugins >>>>>>>>>> >>>>>>>>>>> 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 plugins. The details of this proposal are as follows: >>>>>>>>>>>>>> >>>>>>>>>>>>>> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ >>>>>>>>>>>>>> >>>>>>>>>>>>>> to >>>>>>>>>>>>> >>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, >>>>>>>> >>>>>>>>> branches >>>>>>>>>>>>> >>>>>>>>>>>> and tags underneath as is) >>>>>>>>>> >>>>>>>>>>> 2- Create a new tree under >>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house >>>>>>>>>>>>>> >>>>>>>>>>>>>> all >>>>>>>>>>>>> >>>>>>>>>>>> plugins >>>>>>>> >>>>>>>>> 3- Remove /plugins/component-load.xml (any component in /plugins >>>>>>>>>>>>>> >>>>>>>>>>>>>> will >>>>>>>>>>>>> >>>>>>>>>>>> load automatically if it is enabled in ofbiz-component.xml) >>>>>>>>> >>>>>>>>>> 4- Create a gradle task with the below syntax. This task >>>>>>>>>>>>>> >>>>>>>>>>>>>> downloads >>>>>>>>>>>>> >>>>>>>>>>>> a >>>>>>>> >>>>>>>> plugin from subversion and places it in /plugins and runs any >>>>>>>>> >>>>>>>>>> install >>>>>>>>>>>>> >>>>>>>>>>>> logic >>>>>>>>> >>>>>>>>>> that it may have >>>>>>>>>>>>>> Syntax: pullPluginSource -PpluginId=<plugin-id-here> >>>>>>>>>>>>>> Example: pullPluginSource -PpluginId=birt >>>>>>>>>>>>>> 5- Refactor the build scripts to cater for all the above >>>>>>>>>>>>>> 6- Update README.md to reflect all the above >>>>>>>>>>>>>> >>>>>>>>>>>>>> So for example, under this proposal, trunk is located in: >>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk >>>>>>>>>>>>>> >>>>>>>>>>>>>> And the birt component is located in: >>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/bi >>>>>>>>>>>>>> rt >>>>>>>>>>>>>> >>>>>>>>>>>>>> This would allow us to have in the future the ability to >>>>>>>>>>>>>> provide >>>>>>>>>>>>>> releases not only for the framework but the plugins as well as >>>>>>>>>>>>>> >>>>>>>>>>>>>> two >>>>>>>>>>>>> >>>>>>>>>>>> separate >>>>>>>> >>>>>>>>> products. >>>>>>>>>>>>>> >>>>>>>>>>>>>> What do you think? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Taher Alkhateeb >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>> >> >> > |
Re: Proposal to create a separate svn repository for the OFBiz official plugins
|
Administrator
|
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 its own fashion We now need to document all... Thanks! Jacques Le 12/02/2017 à 11:36, Deepak Dixit a écrit : > 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 < > [hidden email]> wrote: > >> 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 be more discussed, and maybe voted, here >>> >>> Jacques >>> >>> >>> Le 12/02/2017 à 11:18, Deepak Dixit a écrit : >>> >>>> 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 12, 2017 at 3:43 PM, Jacques Le Roux < >>>> [hidden email]> wrote: >>>> >>>> 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 >>>>>> www.hotwaxsystems.com >>>>>> >>>>>> On Sun, Feb 12, 2017 at 2:52 PM, Deepak Dixit < >>>>>> [hidden email]> wrote: >>>>>> >>>>>> 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 < >>>>>>> [hidden email]> wrote: >>>>>>> >>>>>>> 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 figure >>>>>>>> the >>>>>>>> actual command itself to create the new repositories. >>>>>>>> >>>>>>>> If you can help in this area it would be great, and I can focus on >>>>>>>> perhaps >>>>>>>> making sure the plugin API works correctly and updating buildbot. I >>>>>>>> already >>>>>>>> have OFBIZ-9182 setup for this task, so perhaps you can work over >>>>>>>> there >>>>>>>> on >>>>>>>> the actual restructuring, putting the commands and your thoughts in >>>>>>>> place >>>>>>>> on how to do it exactly. >>>>>>>> >>>>>>>> [1] >>>>>>>> http://stackoverflow.com/questions/360758/moving-a-subversio >>>>>>>> n-repository-to-another-server#360829 >>>>>>>> >>>>>>>> Cheers, >>>>>>>> >>>>>>>> Taher Alkhateeb >>>>>>>> >>>>>>>> On Sun, Feb 12, 2017 at 11:15 AM, Deepak Dixit < >>>>>>>> [hidden email]> wrote: >>>>>>>> >>>>>>>> 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 < >>>>>>>>> [hidden email] >>>>>>>>> >>>>>>>>> wrote: >>>>>>>>>> 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 repository in >>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk >>>>>>>>>> - Update the references in the website >>>>>>>>>> https://ofbiz.apache.org/source-repositories.html >>>>>>>>>> - Update the buildbot scripts (we might as well figure out why it >>>>>>>>>> >>>>>>>>>> fails >>>>>>>>> constantly lately) >>>>>>>>> >>>>>>>>>> Any volunteers to help? >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> >>>>>>>>>> Taher Alkhateeb >>>>>>>>>> >>>>>>>>>> On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux < >>>>>>>>>> [hidden email]> wrote: >>>>>>>>>> >>>>>>>>>> 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" < >>>>>>>>>> >>>>>>>>>>> [hidden email]> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> 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 >>>>>>>>>>>>>> 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 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 apk file. >>>>>>>>>>>>>>> -----邮件原件----- >>>>>>>>>>>>>>> 发件人: Taher Alkhateeb [mailto:[hidden email]] >>>>>>>>>>>>>>> 发送时间: 2017年1月11日 23:02 >>>>>>>>>>>>>>> 收件人: [hidden email] >>>>>>>>>>>>>>> 主题: Proposal to create a separate svn repository for the OFBiz >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> official >>>>>>>>>>>>> plugins >>>>>>>>>>>> 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 plugins. The details of this proposal are as follows: >>>>>>>>>>>>>>> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> to >>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, >>>>>>>>>> branches >>>>>>>>>>>>> and tags underneath as is) >>>>>>>>>>>> 2- Create a new tree under >>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> all >>>>>>>>>>>>> plugins >>>>>>>>>> 3- Remove /plugins/component-load.xml (any component in /plugins >>>>>>>>>>>>>>> will >>>>>>>>>>>>> load automatically if it is enabled in ofbiz-component.xml) >>>>>>>>>>> 4- Create a gradle task with the below syntax. This task >>>>>>>>>>>>>>> downloads >>>>>>>>>>>>> a >>>>>>>>> plugin from subversion and places it in /plugins and runs any >>>>>>>>>>> install >>>>>>>>>>>>> logic >>>>>>>>>>> that it may have >>>>>>>>>>>>>>> Syntax: pullPluginSource -PpluginId=<plugin-id-here> >>>>>>>>>>>>>>> Example: pullPluginSource -PpluginId=birt >>>>>>>>>>>>>>> 5- Refactor the build scripts to cater for all the above >>>>>>>>>>>>>>> 6- Update README.md to reflect all the above >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> So for example, under this proposal, trunk is located in: >>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> And the birt component is located in: >>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/bi >>>>>>>>>>>>>>> rt >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> This would allow us to have in the future the ability to >>>>>>>>>>>>>>> provide >>>>>>>>>>>>>>> releases not only for the framework but the plugins as well as >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> two >>>>>>>>>>>>> separate >>>>>>>>>> products. >>>>>>>>>>>>>>> What do you think? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Taher Alkhateeb >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>> |
|
Great work Deepak! Thank you.
On Sun, Feb 12, 2017 at 2:00 PM, Jacques Le Roux < [hidden email]> 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 Github mirror best practices, here is > Daniel's answer > > Daniel Gruno (Humbedooh)·11:54 AM: normally, git accounts for this in its > own fashion > > We now need to document all... > > Thanks! > > Jacques > > > > Le 12/02/2017 à 11:36, Deepak Dixit a écrit : > >> 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 < >> [hidden email]> wrote: >> >> 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 be more discussed, and maybe voted, here >>>> >>>> Jacques >>>> >>>> >>>> Le 12/02/2017 à 11:18, Deepak Dixit a écrit : >>>> >>>> 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 12, 2017 at 3:43 PM, Jacques Le Roux < >>>>> [hidden email]> wrote: >>>>> >>>>> 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 >>>>>>> www.hotwaxsystems.com >>>>>>> >>>>>>> On Sun, Feb 12, 2017 at 2:52 PM, Deepak Dixit < >>>>>>> [hidden email]> wrote: >>>>>>> >>>>>>> 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 < >>>>>>>> [hidden email]> wrote: >>>>>>>> >>>>>>>> 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 figure >>>>>>>>> the >>>>>>>>> actual command itself to create the new repositories. >>>>>>>>> >>>>>>>>> If you can help in this area it would be great, and I can focus on >>>>>>>>> perhaps >>>>>>>>> making sure the plugin API works correctly and updating buildbot. I >>>>>>>>> already >>>>>>>>> have OFBIZ-9182 setup for this task, so perhaps you can work over >>>>>>>>> there >>>>>>>>> on >>>>>>>>> the actual restructuring, putting the commands and your thoughts in >>>>>>>>> place >>>>>>>>> on how to do it exactly. >>>>>>>>> >>>>>>>>> [1] >>>>>>>>> http://stackoverflow.com/questions/360758/moving-a-subversio >>>>>>>>> n-repository-to-another-server#360829 >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> >>>>>>>>> Taher Alkhateeb >>>>>>>>> >>>>>>>>> On Sun, Feb 12, 2017 at 11:15 AM, Deepak Dixit < >>>>>>>>> [hidden email]> wrote: >>>>>>>>> >>>>>>>>> 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 < >>>>>>>>>> [hidden email] >>>>>>>>>> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> 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 repository in >>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk >>>>>>>>>>> - Update the references in the website >>>>>>>>>>> https://ofbiz.apache.org/source-repositories.html >>>>>>>>>>> - Update the buildbot scripts (we might as well figure out why it >>>>>>>>>>> >>>>>>>>>>> fails >>>>>>>>>>> >>>>>>>>>> constantly lately) >>>>>>>>>> >>>>>>>>>> Any volunteers to help? >>>>>>>>>>> >>>>>>>>>>> Cheers, >>>>>>>>>>> >>>>>>>>>>> Taher Alkhateeb >>>>>>>>>>> >>>>>>>>>>> On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux < >>>>>>>>>>> [hidden email]> wrote: >>>>>>>>>>> >>>>>>>>>>> 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" < >>>>>>>>>>> >>>>>>>>>>> [hidden email]> >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> 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 >>>>>>>>>>>>>> >>>>>>>>>>>>>>> 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 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 apk file. >>>>>>>>>>>>>> >>>>>>>>>>>>>>> -----邮件原件----- >>>>>>>>>>>>>>>> 发件人: Taher Alkhateeb [mailto:[hidden email]] >>>>>>>>>>>>>>>> 发送时间: 2017年1月11日 23:02 >>>>>>>>>>>>>>>> 收件人: [hidden email] >>>>>>>>>>>>>>>> 主题: Proposal to create a separate svn repository for the >>>>>>>>>>>>>>>> OFBiz >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> official >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> plugins >>>>>>>>>>>>>> >>>>>>>>>>>>> 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 plugins. The details of this proposal are as follows: >>>>>>>>>>> >>>>>>>>>>>> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> to >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all trunk, >>>>>>>>>>>>>> >>>>>>>>>>>>> branches >>>>>>>>>>> >>>>>>>>>>>> and tags underneath as is) >>>>>>>>>>>>>> >>>>>>>>>>>>> 2- Create a new tree under >>>>>>>>>>>>> >>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> all >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> plugins >>>>>>>>>>>>>> >>>>>>>>>>>>> 3- Remove /plugins/component-load.xml (any component in >>>>>>>>>>> /plugins >>>>>>>>>>> >>>>>>>>>>>> will >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> load automatically if it is enabled in ofbiz-component.xml) >>>>>>>>>>>>>> >>>>>>>>>>>>> 4- Create a gradle task with the below syntax. This task >>>>>>>>>>>> >>>>>>>>>>>>> downloads >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> a >>>>>>>>>>>>>> >>>>>>>>>>>>> plugin from subversion and places it in /plugins and runs any >>>>>>>>>> >>>>>>>>>>> install >>>>>>>>>>>> >>>>>>>>>>>>> logic >>>>>>>>>>>>>> >>>>>>>>>>>>> that it may have >>>>>>>>>>>> >>>>>>>>>>>>> Syntax: pullPluginSource -PpluginId=<plugin-id-here> >>>>>>>>>>>>>>>> Example: pullPluginSource -PpluginId=birt >>>>>>>>>>>>>>>> 5- Refactor the build scripts to cater for all the above >>>>>>>>>>>>>>>> 6- Update README.md to reflect all the above >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> So for example, under this proposal, trunk is located in: >>>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> And the birt component is located in: >>>>>>>>>>>>>>>> http://svn.apache.org/repos/as >>>>>>>>>>>>>>>> f/ofbiz/ofbiz-plugins/trunk/bi >>>>>>>>>>>>>>>> rt >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> This would allow us to have in the future the ability to >>>>>>>>>>>>>>>> provide >>>>>>>>>>>>>>>> releases not only for the framework but the plugins as well >>>>>>>>>>>>>>>> as >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> two >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> separate >>>>>>>>>>>>>> >>>>>>>>>>>>> products. >>>>>>>>>>> >>>>>>>>>>>> What do you think? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Taher Alkhateeb >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>> > |
|
|
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 <[hidden email] > wrote: > Great work Deepak! Thank you. > > On Sun, Feb 12, 2017 at 2:00 PM, Jacques Le Roux < > [hidden email]> 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 Github mirror best practices, here is >> Daniel's answer >> >> Daniel Gruno (Humbedooh)·11:54 AM: normally, git accounts for this in its >> own fashion >> >> We now need to document all... >> >> Thanks! >> >> Jacques >> >> >> >> Le 12/02/2017 à 11:36, Deepak Dixit a écrit : >> >>> 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 < >>> [hidden email]> wrote: >>> >>> 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 be more discussed, and maybe voted, here >>>>> >>>>> Jacques >>>>> >>>>> >>>>> Le 12/02/2017 à 11:18, Deepak Dixit a écrit : >>>>> >>>>> 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 12, 2017 at 3:43 PM, Jacques Le Roux < >>>>>> [hidden email]> wrote: >>>>>> >>>>>> 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 >>>>>>>> www.hotwaxsystems.com >>>>>>>> >>>>>>>> On Sun, Feb 12, 2017 at 2:52 PM, Deepak Dixit < >>>>>>>> [hidden email]> wrote: >>>>>>>> >>>>>>>> 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 < >>>>>>>>> [hidden email]> wrote: >>>>>>>>> >>>>>>>>> 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 >>>>>>>>>> figure >>>>>>>>>> the >>>>>>>>>> actual command itself to create the new repositories. >>>>>>>>>> >>>>>>>>>> If you can help in this area it would be great, and I can focus on >>>>>>>>>> perhaps >>>>>>>>>> making sure the plugin API works correctly and updating buildbot. >>>>>>>>>> I >>>>>>>>>> already >>>>>>>>>> have OFBIZ-9182 setup for this task, so perhaps you can work over >>>>>>>>>> there >>>>>>>>>> on >>>>>>>>>> the actual restructuring, putting the commands and your thoughts >>>>>>>>>> in >>>>>>>>>> place >>>>>>>>>> on how to do it exactly. >>>>>>>>>> >>>>>>>>>> [1] >>>>>>>>>> http://stackoverflow.com/questions/360758/moving-a-subversio >>>>>>>>>> n-repository-to-another-server#360829 >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> >>>>>>>>>> Taher Alkhateeb >>>>>>>>>> >>>>>>>>>> On Sun, Feb 12, 2017 at 11:15 AM, Deepak Dixit < >>>>>>>>>> [hidden email]> wrote: >>>>>>>>>> >>>>>>>>>> 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 < >>>>>>>>>>> [hidden email] >>>>>>>>>>> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> 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 repository in >>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk >>>>>>>>>>>> - Update the references in the website >>>>>>>>>>>> https://ofbiz.apache.org/source-repositories.html >>>>>>>>>>>> - Update the buildbot scripts (we might as well figure out why >>>>>>>>>>>> it >>>>>>>>>>>> >>>>>>>>>>>> fails >>>>>>>>>>>> >>>>>>>>>>> constantly lately) >>>>>>>>>>> >>>>>>>>>>> Any volunteers to help? >>>>>>>>>>>> >>>>>>>>>>>> Cheers, >>>>>>>>>>>> >>>>>>>>>>>> Taher Alkhateeb >>>>>>>>>>>> >>>>>>>>>>>> On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux < >>>>>>>>>>>> [hidden email]> wrote: >>>>>>>>>>>> >>>>>>>>>>>> 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" < >>>>>>>>>>>> >>>>>>>>>>>> [hidden email]> >>>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> 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 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 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 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 apk file. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -----邮件原件----- >>>>>>>>>>>>>>>>> 发件人: Taher Alkhateeb [mailto:[hidden email]] >>>>>>>>>>>>>>>>> 发送时间: 2017年1月11日 23:02 >>>>>>>>>>>>>>>>> 收件人: [hidden email] >>>>>>>>>>>>>>>>> 主题: Proposal to create a separate svn repository for the >>>>>>>>>>>>>>>>> OFBiz >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> official >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> plugins >>>>>>>>>>>>>>> >>>>>>>>>>>>>> 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 plugins. The details of this proposal are as follows: >>>>>>>>>>>> >>>>>>>>>>>>> 1- Relocate OFBiz from http://svn.apache.org/repos/asf/ofbiz/ >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> to >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all >>>>>>>>>>>>>>> trunk, >>>>>>>>>>>>>>> >>>>>>>>>>>>>> branches >>>>>>>>>>>> >>>>>>>>>>>>> and tags underneath as is) >>>>>>>>>>>>>>> >>>>>>>>>>>>>> 2- Create a new tree under >>>>>>>>>>>>>> >>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to house >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> all >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> plugins >>>>>>>>>>>>>>> >>>>>>>>>>>>>> 3- Remove /plugins/component-load.xml (any component in >>>>>>>>>>>> /plugins >>>>>>>>>>>> >>>>>>>>>>>>> will >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> load automatically if it is enabled in ofbiz-component.xml) >>>>>>>>>>>>>>> >>>>>>>>>>>>>> 4- Create a gradle task with the below syntax. This task >>>>>>>>>>>>> >>>>>>>>>>>>>> downloads >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> a >>>>>>>>>>>>>>> >>>>>>>>>>>>>> plugin from subversion and places it in /plugins and runs any >>>>>>>>>>> >>>>>>>>>>>> install >>>>>>>>>>>>> >>>>>>>>>>>>>> logic >>>>>>>>>>>>>>> >>>>>>>>>>>>>> that it may have >>>>>>>>>>>>> >>>>>>>>>>>>>> Syntax: pullPluginSource -PpluginId=<plugin-id-here> >>>>>>>>>>>>>>>>> Example: pullPluginSource -PpluginId=birt >>>>>>>>>>>>>>>>> 5- Refactor the build scripts to cater for all the above >>>>>>>>>>>>>>>>> 6- Update README.md to reflect all the above >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> So for example, under this proposal, trunk is located in: >>>>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> And the birt component is located in: >>>>>>>>>>>>>>>>> http://svn.apache.org/repos/as >>>>>>>>>>>>>>>>> f/ofbiz/ofbiz-plugins/trunk/bi >>>>>>>>>>>>>>>>> rt >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> This would allow us to have in the future the ability to >>>>>>>>>>>>>>>>> provide >>>>>>>>>>>>>>>>> releases not only for the framework but the plugins as >>>>>>>>>>>>>>>>> well as >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> two >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> separate >>>>>>>>>>>>>>> >>>>>>>>>>>>>> products. >>>>>>>>>>>> >>>>>>>>>>>>> What do you think? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Taher Alkhateeb >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>> >> > |
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 <[hidden email] > wrote: > 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 < > [hidden email] > > wrote: > > > Great work Deepak! Thank you. > > > > On Sun, Feb 12, 2017 at 2:00 PM, Jacques Le Roux < > > [hidden email]> 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 Github mirror best practices, here is > >> Daniel's answer > >> > >> Daniel Gruno (Humbedooh)·11:54 AM: normally, git accounts for this in > its > >> own fashion > >> > >> We now need to document all... > >> > >> Thanks! > >> > >> Jacques > >> > >> > >> > >> Le 12/02/2017 à 11:36, Deepak Dixit a écrit : > >> > >>> 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 < > >>> [hidden email]> wrote: > >>> > >>> 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 be more discussed, and maybe voted, here > >>>>> > >>>>> Jacques > >>>>> > >>>>> > >>>>> Le 12/02/2017 à 11:18, Deepak Dixit a écrit : > >>>>> > >>>>> 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 12, 2017 at 3:43 PM, Jacques Le Roux < > >>>>>> [hidden email]> wrote: > >>>>>> > >>>>>> 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 > >>>>>>>> www.hotwaxsystems.com > >>>>>>>> > >>>>>>>> On Sun, Feb 12, 2017 at 2:52 PM, Deepak Dixit < > >>>>>>>> [hidden email]> wrote: > >>>>>>>> > >>>>>>>> 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 < > >>>>>>>>> [hidden email]> wrote: > >>>>>>>>> > >>>>>>>>> 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 > >>>>>>>>>> figure > >>>>>>>>>> the > >>>>>>>>>> actual command itself to create the new repositories. > >>>>>>>>>> > >>>>>>>>>> If you can help in this area it would be great, and I can focus > on > >>>>>>>>>> perhaps > >>>>>>>>>> making sure the plugin API works correctly and updating > buildbot. > >>>>>>>>>> I > >>>>>>>>>> already > >>>>>>>>>> have OFBIZ-9182 setup for this task, so perhaps you can work > over > >>>>>>>>>> there > >>>>>>>>>> on > >>>>>>>>>> the actual restructuring, putting the commands and your thoughts > >>>>>>>>>> in > >>>>>>>>>> place > >>>>>>>>>> on how to do it exactly. > >>>>>>>>>> > >>>>>>>>>> [1] > >>>>>>>>>> http://stackoverflow.com/questions/360758/moving-a-subversio > >>>>>>>>>> n-repository-to-another-server#360829 > >>>>>>>>>> > >>>>>>>>>> Cheers, > >>>>>>>>>> > >>>>>>>>>> Taher Alkhateeb > >>>>>>>>>> > >>>>>>>>>> On Sun, Feb 12, 2017 at 11:15 AM, Deepak Dixit < > >>>>>>>>>> [hidden email]> wrote: > >>>>>>>>>> > >>>>>>>>>> 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 < > >>>>>>>>>>> [hidden email] > >>>>>>>>>>> > >>>>>>>>>>> wrote: > >>>>>>>>>>> > >>>>>>>>>>>> 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 repository in > >>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk > >>>>>>>>>>>> - Update the references in the website > >>>>>>>>>>>> https://ofbiz.apache.org/source-repositories.html > >>>>>>>>>>>> - Update the buildbot scripts (we might as well figure out why > >>>>>>>>>>>> it > >>>>>>>>>>>> > >>>>>>>>>>>> fails > >>>>>>>>>>>> > >>>>>>>>>>> constantly lately) > >>>>>>>>>>> > >>>>>>>>>>> Any volunteers to help? > >>>>>>>>>>>> > >>>>>>>>>>>> Cheers, > >>>>>>>>>>>> > >>>>>>>>>>>> Taher Alkhateeb > >>>>>>>>>>>> > >>>>>>>>>>>> On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux < > >>>>>>>>>>>> [hidden email]> wrote: > >>>>>>>>>>>> > >>>>>>>>>>>> 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" < > >>>>>>>>>>>> > >>>>>>>>>>>> [hidden email]> > >>>>>>>>>>>>> wrote: > >>>>>>>>>>>>> > >>>>>>>>>>>>> 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 > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> 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 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 apk file. > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> -----邮件原件----- > >>>>>>>>>>>>>>>>> 发件人: Taher Alkhateeb [mailto:[hidden email]] > >>>>>>>>>>>>>>>>> 发送时间: 2017年1月11日 23:02 > >>>>>>>>>>>>>>>>> 收件人: [hidden email] > >>>>>>>>>>>>>>>>> 主题: Proposal to create a separate svn repository for the > >>>>>>>>>>>>>>>>> OFBiz > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> official > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> plugins > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> 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 plugins. The details of this proposal are as follows: > >>>>>>>>>>>> > >>>>>>>>>>>>> 1- Relocate OFBiz from http://svn.apache.org/repos/ > asf/ofbiz/ > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> to > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all > >>>>>>>>>>>>>>> trunk, > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> branches > >>>>>>>>>>>> > >>>>>>>>>>>>> and tags underneath as is) > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> 2- Create a new tree under > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to > house > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> all > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> plugins > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> 3- Remove /plugins/component-load.xml (any component in > >>>>>>>>>>>> /plugins > >>>>>>>>>>>> > >>>>>>>>>>>>> will > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> load automatically if it is enabled in > ofbiz-component.xml) > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> 4- Create a gradle task with the below syntax. This task > >>>>>>>>>>>>> > >>>>>>>>>>>>>> downloads > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> a > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> plugin from subversion and places it in /plugins and runs > any > >>>>>>>>>>> > >>>>>>>>>>>> install > >>>>>>>>>>>>> > >>>>>>>>>>>>>> logic > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> that it may have > >>>>>>>>>>>>> > >>>>>>>>>>>>>> Syntax: pullPluginSource -PpluginId=<plugin-id-here> > >>>>>>>>>>>>>>>>> Example: pullPluginSource -PpluginId=birt > >>>>>>>>>>>>>>>>> 5- Refactor the build scripts to cater for all the above > >>>>>>>>>>>>>>>>> 6- Update README.md to reflect all the above > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> So for example, under this proposal, trunk is located in: > >>>>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> And the birt component is located in: > >>>>>>>>>>>>>>>>> http://svn.apache.org/repos/as > >>>>>>>>>>>>>>>>> f/ofbiz/ofbiz-plugins/trunk/bi > >>>>>>>>>>>>>>>>> rt > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> This would allow us to have in the future the ability to > >>>>>>>>>>>>>>>>> provide > >>>>>>>>>>>>>>>>> releases not only for the framework but the plugins as > >>>>>>>>>>>>>>>>> well as > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> two > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> separate > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> products. > >>>>>>>>>>>> > >>>>>>>>>>>>> What do you think? > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> Cheers, > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> Taher Alkhateeb > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>> > >> > > > |
|
|
In reply to this post by Jacques Le Roux
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 big" or "because it carried a lot of non-essential functionality around" So breaking up the project brings the advantage of not having to _worry about everything_ on each and every commit. These are two projects with two release cycles and they don't need to be developed together simultaneously. People can specialize and focus on different areas. The whole idea of breaking the system up and then using gradle's plugin API for OFBiz is to remove the coupling between the two projects. If we introduce svn externals then all we achieve is create two repositories only to merge them again. Why! that's pointless! Two products means two buildbot scripts, two releases, two development cycles, two different things! So to achieve true separation and decoupling, I suggest to avoid any hacks like svn externals. On Sun, Feb 12, 2017 at 1:31 PM, Jacques Le Roux < [hidden email]> wrote: > 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 svn repository for the OFBiz official plugins)' from the subject > (I was just "lazy" here) > > Thanks > > 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 be more discussed, and maybe voted, here >> >> Jacques >> >> >> Le 12/02/2017 à 11:18, Deepak Dixit a écrit : >> >>> 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 12, 2017 at 3:43 PM, Jacques Le Roux < >>> [hidden email]> wrote: >>> >>> 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 >>>>> www.hotwaxsystems.com >>>>> >>>>> On Sun, Feb 12, 2017 at 2:52 PM, Deepak Dixit < >>>>> [hidden email]> wrote: >>>>> >>>> > |
Re: Proposal to create a separate svn repository for the OFBiz official plugins
|
Administrator
|
In reply to this post by Deepak Dixit-3
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 > -- > Deepak Dixit > www.hotwaxsystems.com > > On Sun, Feb 12, 2017 at 5:31 PM, Taher Alkhateeb <[hidden email] >> wrote: >> 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 < >> [hidden email] >>> wrote: >>> Great work Deepak! Thank you. >>> >>> On Sun, Feb 12, 2017 at 2:00 PM, Jacques Le Roux < >>> [hidden email]> 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 Github mirror best practices, here is >>>> Daniel's answer >>>> >>>> Daniel Gruno (Humbedooh)·11:54 AM: normally, git accounts for this in >> its >>>> own fashion >>>> >>>> We now need to document all... >>>> >>>> Thanks! >>>> >>>> Jacques >>>> >>>> >>>> >>>> Le 12/02/2017 à 11:36, Deepak Dixit a écrit : >>>> >>>>> 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 < >>>>> [hidden email]> wrote: >>>>> >>>>> 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 be more discussed, and maybe voted, here >>>>>>> >>>>>>> Jacques >>>>>>> >>>>>>> >>>>>>> Le 12/02/2017 à 11:18, Deepak Dixit a écrit : >>>>>>> >>>>>>> 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 12, 2017 at 3:43 PM, Jacques Le Roux < >>>>>>>> [hidden email]> wrote: >>>>>>>> >>>>>>>> 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 >>>>>>>>>> www.hotwaxsystems.com >>>>>>>>>> >>>>>>>>>> On Sun, Feb 12, 2017 at 2:52 PM, Deepak Dixit < >>>>>>>>>> [hidden email]> wrote: >>>>>>>>>> >>>>>>>>>> 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 < >>>>>>>>>>> [hidden email]> wrote: >>>>>>>>>>> >>>>>>>>>>> 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 >>>>>>>>>>>> figure >>>>>>>>>>>> the >>>>>>>>>>>> actual command itself to create the new repositories. >>>>>>>>>>>> >>>>>>>>>>>> If you can help in this area it would be great, and I can focus >> on >>>>>>>>>>>> perhaps >>>>>>>>>>>> making sure the plugin API works correctly and updating >> buildbot. >>>>>>>>>>>> I >>>>>>>>>>>> already >>>>>>>>>>>> have OFBIZ-9182 setup for this task, so perhaps you can work >> over >>>>>>>>>>>> there >>>>>>>>>>>> on >>>>>>>>>>>> the actual restructuring, putting the commands and your thoughts >>>>>>>>>>>> in >>>>>>>>>>>> place >>>>>>>>>>>> on how to do it exactly. >>>>>>>>>>>> >>>>>>>>>>>> [1] >>>>>>>>>>>> http://stackoverflow.com/questions/360758/moving-a-subversio >>>>>>>>>>>> n-repository-to-another-server#360829 >>>>>>>>>>>> >>>>>>>>>>>> Cheers, >>>>>>>>>>>> >>>>>>>>>>>> Taher Alkhateeb >>>>>>>>>>>> >>>>>>>>>>>> On Sun, Feb 12, 2017 at 11:15 AM, Deepak Dixit < >>>>>>>>>>>> [hidden email]> wrote: >>>>>>>>>>>> >>>>>>>>>>>> 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 < >>>>>>>>>>>>> [hidden email] >>>>>>>>>>>>> >>>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> 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 repository in >>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk >>>>>>>>>>>>>> - Update the references in the website >>>>>>>>>>>>>> https://ofbiz.apache.org/source-repositories.html >>>>>>>>>>>>>> - Update the buildbot scripts (we might as well figure out why >>>>>>>>>>>>>> it >>>>>>>>>>>>>> >>>>>>>>>>>>>> fails >>>>>>>>>>>>>> >>>>>>>>>>>>> constantly lately) >>>>>>>>>>>>> >>>>>>>>>>>>> Any volunteers to help? >>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Taher Alkhateeb >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux < >>>>>>>>>>>>>> [hidden email]> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> 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" < >>>>>>>>>>>>>> [hidden email]> >>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> 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 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 apk file. >>>>>>>>>>>>>>>>>> -----邮件原件----- >>>>>>>>>>>>>>>>>>> 发件人: Taher Alkhateeb [mailto:[hidden email]] >>>>>>>>>>>>>>>>>>> 发送时间: 2017年1月11日 23:02 >>>>>>>>>>>>>>>>>>> 收件人: [hidden email] >>>>>>>>>>>>>>>>>>> 主题: Proposal to create a separate svn repository for the >>>>>>>>>>>>>>>>>>> OFBiz >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> official >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> plugins >>>>>>>>>>>>>>>> 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 plugins. The details of this proposal are as follows: >>>>>>>>>>>>>>> 1- Relocate OFBiz from http://svn.apache.org/repos/ >> asf/ofbiz/ >>>>>>>>>>>>>>>>>>> to >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all >>>>>>>>>>>>>>>>> trunk, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> branches >>>>>>>>>>>>>>> and tags underneath as is) >>>>>>>>>>>>>>>> 2- Create a new tree under >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to >> house >>>>>>>>>>>>>>>>>>> all >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> plugins >>>>>>>>>>>>>>>> 3- Remove /plugins/component-load.xml (any component in >>>>>>>>>>>>>> /plugins >>>>>>>>>>>>>> >>>>>>>>>>>>>>> will >>>>>>>>>>>>>>>>>> load automatically if it is enabled in >> ofbiz-component.xml) >>>>>>>>>>>>>>>> 4- Create a gradle task with the below syntax. This task >>>>>>>>>>>>>>>> downloads >>>>>>>>>>>>>>>>>> a >>>>>>>>>>>>>>>> plugin from subversion and places it in /plugins and runs >> any >>>>>>>>>>>>>> install >>>>>>>>>>>>>>>> logic >>>>>>>>>>>>>>>> that it may have >>>>>>>>>>>>>>>> Syntax: pullPluginSource -PpluginId=<plugin-id-here> >>>>>>>>>>>>>>>>>>> Example: pullPluginSource -PpluginId=birt >>>>>>>>>>>>>>>>>>> 5- Refactor the build scripts to cater for all the above >>>>>>>>>>>>>>>>>>> 6- Update README.md to reflect all the above >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> So for example, under this proposal, trunk is located in: >>>>>>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> And the birt component is located in: >>>>>>>>>>>>>>>>>>> http://svn.apache.org/repos/as >>>>>>>>>>>>>>>>>>> f/ofbiz/ofbiz-plugins/trunk/bi >>>>>>>>>>>>>>>>>>> rt >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> This would allow us to have in the future the ability to >>>>>>>>>>>>>>>>>>> provide >>>>>>>>>>>>>>>>>>> releases not only for the framework but the plugins as >>>>>>>>>>>>>>>>>>> well as >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> two >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> separate >>>>>>>>>>>>>>>> products. >>>>>>>>>>>>>>> What do you think? >>>>>>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Taher Alkhateeb >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> |
|
|
What does 13.07 have anything to do with this?
On Feb 12, 2017 3:49 PM, "Jacques Le Roux" <[hidden email]> 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 Le 12/02/2017 à 13:15, Deepak Dixit a écrit : > 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 < > [hidden email] > >> wrote: >> 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 < >> [hidden email] >> >>> wrote: >>> Great work Deepak! Thank you. >>> >>> On Sun, Feb 12, 2017 at 2:00 PM, Jacques Le Roux < >>> [hidden email]> 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 Github mirror best practices, here is >>>> Daniel's answer >>>> >>>> Daniel Gruno (Humbedooh)·11:54 AM: normally, git accounts for this in >>>> >>> its >> >>> own fashion >>>> >>>> We now need to document all... >>>> >>>> Thanks! >>>> >>>> Jacques >>>> >>>> >>>> >>>> Le 12/02/2017 à 11:36, Deepak Dixit a écrit : >>>> >>>> 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 < >>>>> [hidden email]> wrote: >>>>> >>>>> 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 be more discussed, and maybe voted, here >>>>>>> >>>>>>> Jacques >>>>>>> >>>>>>> >>>>>>> Le 12/02/2017 à 11:18, Deepak Dixit a écrit : >>>>>>> >>>>>>> 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 12, 2017 at 3:43 PM, Jacques Le Roux < >>>>>>>> [hidden email]> wrote: >>>>>>>> >>>>>>>> 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 >>>>>>>>>> www.hotwaxsystems.com >>>>>>>>>> >>>>>>>>>> On Sun, Feb 12, 2017 at 2:52 PM, Deepak Dixit < >>>>>>>>>> [hidden email]> wrote: >>>>>>>>>> >>>>>>>>>> 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 < >>>>>>>>>>> [hidden email]> wrote: >>>>>>>>>>> >>>>>>>>>>> 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 >>>>>>>>>>>> figure >>>>>>>>>>>> the >>>>>>>>>>>> actual command itself to create the new repositories. >>>>>>>>>>>> >>>>>>>>>>>> If you can help in this area it would be great, and I can focus >>>>>>>>>>>> >>>>>>>>>>> on >> >>> perhaps >>>>>>>>>>>> making sure the plugin API works correctly and updating >>>>>>>>>>>> >>>>>>>>>>> buildbot. >> >>> I >>>>>>>>>>>> already >>>>>>>>>>>> have OFBIZ-9182 setup for this task, so perhaps you can work >>>>>>>>>>>> >>>>>>>>>>> over >> >>> there >>>>>>>>>>>> on >>>>>>>>>>>> the actual restructuring, putting the commands and your thoughts >>>>>>>>>>>> in >>>>>>>>>>>> place >>>>>>>>>>>> on how to do it exactly. >>>>>>>>>>>> >>>>>>>>>>>> [1] >>>>>>>>>>>> http://stackoverflow.com/questions/360758/moving-a-subversio >>>>>>>>>>>> n-repository-to-another-server#360829 >>>>>>>>>>>> >>>>>>>>>>>> Cheers, >>>>>>>>>>>> >>>>>>>>>>>> Taher Alkhateeb >>>>>>>>>>>> >>>>>>>>>>>> On Sun, Feb 12, 2017 at 11:15 AM, Deepak Dixit < >>>>>>>>>>>> [hidden email]> wrote: >>>>>>>>>>>> >>>>>>>>>>>> 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 < >>>>>>>>>>>>> [hidden email] >>>>>>>>>>>>> >>>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> 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 repository in >>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk >>>>>>>>>>>>>> - Update the references in the website >>>>>>>>>>>>>> https://ofbiz.apache.org/source-repositories.html >>>>>>>>>>>>>> - Update the buildbot scripts (we might as well figure out why >>>>>>>>>>>>>> it >>>>>>>>>>>>>> >>>>>>>>>>>>>> fails >>>>>>>>>>>>>> >>>>>>>>>>>>>> constantly lately) >>>>>>>>>>>>> >>>>>>>>>>>>> Any volunteers to help? >>>>>>>>>>>>> >>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Taher Alkhateeb >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux < >>>>>>>>>>>>>> [hidden email]> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> 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" < >>>>>>>>>>>>>>> >>>>>>>>>>>>>> [hidden email]> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> 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 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 apk file. >>>>>>>>>>>>>>>>>> -----邮件原件----- >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> 发件人: Taher Alkhateeb [mailto:[hidden email]] >>>>>>>>>>>>>>>>>>> 发送时间: 2017年1月11日 23:02 >>>>>>>>>>>>>>>>>>> 收件人: [hidden email] >>>>>>>>>>>>>>>>>>> 主题: Proposal to create a separate svn repository for the >>>>>>>>>>>>>>>>>>> OFBiz >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> official >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> plugins >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> 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 plugins. The details of this proposal are as follows: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 1- Relocate OFBiz from http://svn.apache.org/repos/ >>>>>>>>>>>>>>> >>>>>>>>>>>>>> asf/ofbiz/ >> >>> to >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> trunk, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> branches >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> and tags underneath as is) >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 2- Create a new tree under >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> house >> >>> all >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> plugins >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> 3- Remove /plugins/component-load.xml (any component in >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> /plugins >>>>>>>>>>>>>> >>>>>>>>>>>>>> will >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> load automatically if it is enabled in >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> ofbiz-component.xml) >> >>> 4- Create a gradle task with the below syntax. This task >>>>>>>>>>>>>>>> downloads >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> a >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> plugin from subversion and places it in /plugins and runs >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> any >> >>> install >>>>>>>>>>>>>> >>>>>>>>>>>>>>> logic >>>>>>>>>>>>>>>> that it may have >>>>>>>>>>>>>>>> Syntax: pullPluginSource >>>>>>>>>>>>>>>> -PpluginId=<plugin-id-here> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Example: pullPluginSource -PpluginId=birt >>>>>>>>>>>>>>>>>>> 5- Refactor the build scripts to cater for all the above >>>>>>>>>>>>>>>>>>> 6- Update README.md to reflect all the above >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> So for example, under this proposal, trunk is located in: >>>>>>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> And the birt component is located in: >>>>>>>>>>>>>>>>>>> http://svn.apache.org/repos/as >>>>>>>>>>>>>>>>>>> f/ofbiz/ofbiz-plugins/trunk/bi >>>>>>>>>>>>>>>>>>> rt >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> This would allow us to have in the future the ability to >>>>>>>>>>>>>>>>>>> provide >>>>>>>>>>>>>>>>>>> releases not only for the framework but the plugins as >>>>>>>>>>>>>>>>>>> well as >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> two >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> separate >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> products. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> What do you think? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Taher Alkhateeb >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> |
Re: [DISCUSSION] Plugins: svn:external or Gradle Task? (was Re: Proposal to create a separate svn repository for the OFBiz official plugins)
|
|
In reply to this post by taher
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 <[hidden email] > 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 creating two > different repositories? I hope the answer is something like "because it is > too big" or "because it carried a lot of non-essential functionality > around" > > So breaking up the project brings the advantage of not having to _worry > about everything_ on each and every commit. These are two projects with two > release cycles and they don't need to be developed together simultaneously. > People can specialize and focus on different areas. > > The whole idea of breaking the system up and then using gradle's plugin API > for OFBiz is to remove the coupling between the two projects. If we > introduce svn externals then all we achieve is create two repositories > only to merge them again. Why! that's pointless! > > Two products means two buildbot scripts, two releases, two development > cycles, two different things! > > So to achieve true separation and decoupling, I suggest to avoid any hacks > like svn externals. > > On Sun, Feb 12, 2017 at 1:31 PM, Jacques Le Roux < > [hidden email]> wrote: > > > 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 svn repository for the OFBiz official plugins)' from the subject > > (I was just "lazy" here) > > > > Thanks > > > > 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 be more discussed, and maybe voted, here > >> > >> Jacques > >> > >> > >> Le 12/02/2017 à 11:18, Deepak Dixit a écrit : > >> > >>> 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 12, 2017 at 3:43 PM, Jacques Le Roux < > >>> [hidden email]> wrote: > >>> > >>> 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 > >>>>> www.hotwaxsystems.com > >>>>> > >>>>> On Sun, Feb 12, 2017 at 2:52 PM, Deepak Dixit < > >>>>> [hidden email]> wrote: > >>>>> > >>>> > > > |
Re: Proposal to create a separate svn repository for the OFBiz official plugins
|
|
In reply to this post by taher
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 <[hidden email] > wrote: > What does 13.07 have anything to do with this? > > On Feb 12, 2017 3:49 PM, "Jacques Le Roux" <[hidden email]> > 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 > > > > Le 12/02/2017 à 13:15, Deepak Dixit a écrit : > > > 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 < > > [hidden email] > > > >> wrote: > >> 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 < > >> [hidden email] > >> > >>> wrote: > >>> Great work Deepak! Thank you. > >>> > >>> On Sun, Feb 12, 2017 at 2:00 PM, Jacques Le Roux < > >>> [hidden email]> 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 Github mirror best practices, here is > >>>> Daniel's answer > >>>> > >>>> Daniel Gruno (Humbedooh)·11:54 AM: normally, git accounts for this in > >>>> > >>> its > >> > >>> own fashion > >>>> > >>>> We now need to document all... > >>>> > >>>> Thanks! > >>>> > >>>> Jacques > >>>> > >>>> > >>>> > >>>> Le 12/02/2017 à 11:36, Deepak Dixit a écrit : > >>>> > >>>> 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 < > >>>>> [hidden email]> wrote: > >>>>> > >>>>> 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 be more discussed, and maybe voted, here > >>>>>>> > >>>>>>> Jacques > >>>>>>> > >>>>>>> > >>>>>>> Le 12/02/2017 à 11:18, Deepak Dixit a écrit : > >>>>>>> > >>>>>>> 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 12, 2017 at 3:43 PM, Jacques Le Roux < > >>>>>>>> [hidden email]> wrote: > >>>>>>>> > >>>>>>>> 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 > >>>>>>>>>> www.hotwaxsystems.com > >>>>>>>>>> > >>>>>>>>>> On Sun, Feb 12, 2017 at 2:52 PM, Deepak Dixit < > >>>>>>>>>> [hidden email]> wrote: > >>>>>>>>>> > >>>>>>>>>> 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 < > >>>>>>>>>>> [hidden email]> wrote: > >>>>>>>>>>> > >>>>>>>>>>> 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 > >>>>>>>>>>>> figure > >>>>>>>>>>>> the > >>>>>>>>>>>> actual command itself to create the new repositories. > >>>>>>>>>>>> > >>>>>>>>>>>> If you can help in this area it would be great, and I can > focus > >>>>>>>>>>>> > >>>>>>>>>>> on > >> > >>> perhaps > >>>>>>>>>>>> making sure the plugin API works correctly and updating > >>>>>>>>>>>> > >>>>>>>>>>> buildbot. > >> > >>> I > >>>>>>>>>>>> already > >>>>>>>>>>>> have OFBIZ-9182 setup for this task, so perhaps you can work > >>>>>>>>>>>> > >>>>>>>>>>> over > >> > >>> there > >>>>>>>>>>>> on > >>>>>>>>>>>> the actual restructuring, putting the commands and your > thoughts > >>>>>>>>>>>> in > >>>>>>>>>>>> place > >>>>>>>>>>>> on how to do it exactly. > >>>>>>>>>>>> > >>>>>>>>>>>> [1] > >>>>>>>>>>>> http://stackoverflow.com/questions/360758/moving-a-subversio > >>>>>>>>>>>> n-repository-to-another-server#360829 > >>>>>>>>>>>> > >>>>>>>>>>>> Cheers, > >>>>>>>>>>>> > >>>>>>>>>>>> Taher Alkhateeb > >>>>>>>>>>>> > >>>>>>>>>>>> On Sun, Feb 12, 2017 at 11:15 AM, Deepak Dixit < > >>>>>>>>>>>> [hidden email]> wrote: > >>>>>>>>>>>> > >>>>>>>>>>>> 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 < > >>>>>>>>>>>>> [hidden email] > >>>>>>>>>>>>> > >>>>>>>>>>>>> wrote: > >>>>>>>>>>>>> > >>>>>>>>>>>>> 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 repository in > >>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk > >>>>>>>>>>>>>> - Update the references in the website > >>>>>>>>>>>>>> https://ofbiz.apache.org/source-repositories.html > >>>>>>>>>>>>>> - Update the buildbot scripts (we might as well figure out > why > >>>>>>>>>>>>>> it > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> fails > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> constantly lately) > >>>>>>>>>>>>> > >>>>>>>>>>>>> Any volunteers to help? > >>>>>>>>>>>>> > >>>>>>>>>>>>>> Cheers, > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Taher Alkhateeb > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> On Tue, Jan 31, 2017 at 5:19 PM, Jacques Le Roux < > >>>>>>>>>>>>>> [hidden email]> wrote: > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> 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" < > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> [hidden email]> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> 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 > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> 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 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 apk file. > >>>>>>>>>>>>>>>>>> -----邮件原件----- > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> 发件人: Taher Alkhateeb [mailto:slidingfilaments@ > gmail.com] > >>>>>>>>>>>>>>>>>>> 发送时间: 2017年1月11日 23:02 > >>>>>>>>>>>>>>>>>>> 收件人: [hidden email] > >>>>>>>>>>>>>>>>>>> 主题: Proposal to create a separate svn repository for > the > >>>>>>>>>>>>>>>>>>> OFBiz > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> official > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> plugins > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> 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 plugins. The details of this proposal are as > follows: > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> 1- Relocate OFBiz from http://svn.apache.org/repos/ > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> asf/ofbiz/ > >> > >>> to > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz (with all > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> trunk, > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> branches > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> and tags underneath as is) > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> 2- Create a new tree under > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins to > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> house > >> > >>> all > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> plugins > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> 3- Remove /plugins/component-load.xml (any component in > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> /plugins > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> will > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> load automatically if it is enabled in > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> ofbiz-component.xml) > >> > >>> 4- Create a gradle task with the below syntax. This task > >>>>>>>>>>>>>>>> downloads > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> a > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> plugin from subversion and places it in /plugins and runs > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> any > >> > >>> install > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>> logic > >>>>>>>>>>>>>>>> that it may have > >>>>>>>>>>>>>>>> Syntax: pullPluginSource > >>>>>>>>>>>>>>>> -PpluginId=<plugin-id-here> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> Example: pullPluginSource -PpluginId=birt > >>>>>>>>>>>>>>>>>>> 5- Refactor the build scripts to cater for all the > above > >>>>>>>>>>>>>>>>>>> 6- Update README.md to reflect all the above > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> So for example, under this proposal, trunk is located > in: > >>>>>>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/ofbiz/ofbiz/trunk > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> And the birt component is located in: > >>>>>>>>>>>>>>>>>>> http://svn.apache.org/repos/as > >>>>>>>>>>>>>>>>>>> f/ofbiz/ofbiz-plugins/trunk/bi > >>>>>>>>>>>>>>>>>>> rt > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> This would allow us to have in the future the ability > to > >>>>>>>>>>>>>>>>>>> provide > >>>>>>>>>>>>>>>>>>> releases not only for the framework but the plugins as > >>>>>>>>>>>>>>>>>>> well as > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> two > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> separate > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> products. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> What do you think? > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> Cheers, > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> Taher Alkhateeb > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> > |
Re: [DISCUSSION] Plugins: svn:external or Gradle Task? (was Re: Proposal to create a separate svn repository for the OFBiz official plugins)
|
|
In reply to this post by taher
On Sun, Feb 12, 2017 at 1:32 PM, Taher Alkhateeb <[hidden email]
> 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 creating two > different repositories? I hope the answer is something like "because it is > too big" or "because it carried a lot of non-essential functionality > around" > > So breaking up the project brings the advantage of not having to _worry > about everything_ on each and every commit. These are two projects with two > release cycles and they don't need to be developed together simultaneously. > People can specialize and focus on different areas. > > The whole idea of breaking the system up and then using gradle's plugin API > for OFBiz is to remove the coupling between the two projects. If we > introduce svn externals then all we achieve is create two repositories > only to merge them again. Why! that's pointless! > > Two products means two buildbot scripts, two releases, two development > cycles, two different things! > > So to achieve true separation and decoupling, I suggest to avoid any hacks > like svn externals. > +1 Jacopo |
«
Return to OFBiz - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |