You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Taher Alkhateeb (JIRA)" <ji...@apache.org> on 2017/03/17 11:34:41 UTC

[jira] [Closed] (OFBIZ-9182) Create a separate svn repository for OFBiz official plugins

     [ https://issues.apache.org/jira/browse/OFBIZ-9182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Taher Alkhateeb closed OFBIZ-9182.
----------------------------------
    Resolution: Fixed
      Assignee: Taher Alkhateeb

Work in here is more-or-less done. The plugin system is now fully in place, buildbot is updated, and the plugin API is complete.

What remains should go in new JIRAs including:
- splitting buildbot into two scripts, one for ofbiz-framework and one for ofbiz-plugins
- deciding on release strategy
- setting up a maven repo
- removing the dependencies of ofbiz-framework on ofbiz-plugins

WIP, will issue other JIRAs later

> Create a separate svn repository for OFBiz official plugins
> -----------------------------------------------------------
>
>                 Key: OFBIZ-9182
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-9182
>             Project: OFBiz
>          Issue Type: Improvement
>    Affects Versions: Upcoming Release
>            Reporter: Taher Alkhateeb
>            Assignee: Taher Alkhateeb
>            Priority: Minor
>              Labels: gradle, plugins, subversion
>         Attachments: OFBIZ-9182-subversion-embedded.patch, pluginsList.txt, pullAllPluginsSource.log
>
>
> This issue is related to the discussion found in [this thread|https://s.apache.org/aohk] in which the community approved restructuring our repositories. To achieve this task the following needs to be done (in this order)
> # Update the gradle scripts to assume that no plugins exist in the plugins directory by default and no component-load.xml exists. It should follow the same logic in loading the components as found in the ComponentContainer class. Also the activation and deactivation of plugins happens in ofbiz-component.xml, not in component-load.xml
> # Add a new task to gradle called pullPluginSource that retrieves a plugin from subversion and defaults to the official plugins repository of Apache OFBiz. This task mostly serve "Trunk" because it always needs the latest source code of the plugins.
> # delete plugins/component-load.xml
> # move all plugins to a new repository called http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins
> # move the core framework to a new repository called http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework
> # fix buildbot to point to the new framework location
> # update documentation where applicable including README.md



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)