Mailing-List: contact notifications-help@ofbiz.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ofbiz.apache.org
Date: Sat, 4 Feb 2017 11:15:52 +0000 (UTC)
From: "Jacques Le Roux (JIRA)" <jira@apache.org>
To: notifications@ofbiz.apache.org
Message-ID: <JIRA.13036146.1484817446000.33506.1486206952411@Atlassian.JIRA>
In-Reply-To: <JIRA.13036146.1484817446000@Atlassian.JIRA>
References: <JIRA.13036146.1484817446000@Atlassian.JIRA> <JIRA.13036146.1484817446795@jira-lw-us.apache.org>
Subject: [jira] [Commented] (OFBIZ-9182) create a separate svn repository
 for OFBiz official plugins
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 04 Feb 2017 11:16:00 -0000


    [ https://issues.apache.org/jira/browse/OFBIZ-9182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15852746#comment-15852746 ] 

Jacques Le Roux commented on OFBIZ-9182:
----------------------------------------

As I said already, the pb with gradle-svntools-plugin is it does not handle property (yet?) so I don't see how at this stage
bq.  svn externals could be an implementation detail then embedded inside pullPluginSourceAll
Morevoer as setting an svn:externals is only a matter of a property commit (done once) I don't see the need to have that embedded inside pullPluginSourceAll at all

Moreover IMO pullPluginSource is only interesting if we can pass an URL for non ASF repos.

But I agree we can go on with restructuring the OFBiz repo branch, and discuss further on dev ML if we should use svn:externals or not. I think we already put all the arguments on the table.

> 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
>            Priority: Minor
>              Labels: gradle, plugins, subversion
>         Attachments: OFBIZ-9182-subversion-embedded.patch
>
>
> 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)