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 < [email protected]> 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 < > [email protected]> 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 < >>> [email protected]> 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 < >>>> [email protected]> 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 < >>>>> [email protected]> 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 < >>>>>> [email protected] >>>>>> >>>>>>> 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 < >>>>>>> [email protected]> 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" < >>>>>>>>> >>>>>>>> [email protected]> >>>>>>> >>>>>>>> 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:[email protected]] >>>>>>>>>>>> 发送时间: 2017年1月11日 23:02 >>>>>>>>>>>> 收件人: [email protected] >>>>>>>>>>>> 主题: 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 >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>> >> >
