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 < [email protected]> 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 < >> [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 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >
