ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacques Le Roux (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OFBIZ-9182) Create a separate svn repository for OFBiz official plugins
Date Sat, 18 Feb 2017 11:24:44 GMT

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

Jacques Le Roux updated OFBIZ-9182:
    Attachment: pullAllPluginsSource.log

I have quickly tried to create a pullAllPluginsSource task adding the code below
Index: build.gradle
--- build.gradle	(revision 1783441)
+++ build.gradle	(working copy)
@@ -745,6 +745,17 @@

+task pullAllPluginsSource(group: ofbizPlugin, description: 'Download and install all plugins
from source control') {
+    String[] pluginsList = new File('pluginsList.txt')
+    for (plugin in pluginsList) {
+        def svnUrl = "https://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk/" + plugin
+        def workspaceDir = "${rootDir}/plugins/" + plugin
+        installPlugin(plugin)
+    }
 // ========== Clean up tasks ==========
 task cleanCatalina(group: cleanupGroup, description: 'Clean Catalina data in runtime/catalina/work')
     doLast { delete "${rootDir}/runtime/catalina/work" }
But I got a weird issue. The task stacks the call to installPlugin and so also stacks Gradle
Daemons (I use it locally). So the memory increases fast and at some point you either get
ouf or memory, or if you care before the whole thing crashes anyway. See pullAllPluginsSource.log
and pluginsList.txt attached files.

It would have been quite cool but it's obviously not good. What would be the right way?

BTW "don't try that at home" ;) In a last attempt, I rebooted, cleared all possible memory
and tried it again. It sucked up all the ressources on my machines at a point I almost wanted
to make a hard reboot. But it finally stopped and freed the memory as I have never seen on
my machine, 1.5 GB used only on 16GB (see ULTIMATE TRY in pullAllPluginsSource.log). I'm though
curious how Linux would react...

> 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, 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

View raw message