The plugins are already published as zip archives in the implementation On Jan 31, 2017 5:09 PM, "Jacques Le Roux" <jacques.le.r...@les7arts.com> 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:slidingfilame...@gmail.com] >>> 发送时间: 2017年1月11日 23:02 >>> 收件人: dev@ofbiz.apache.org >>> 主题: 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 >>> >>> >> >> >
