[
https://issues.apache.org/jira/browse/OFBIZ-9182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876850#comment-15876850
]
Jacques Le Roux commented on OFBIZ-9182:
----------------------------------------
OK, not only that. It did not work for me. So I thought you needed to remove
all your gradle folder (the one under your username, where the cache is also).
Else, at least on Windows, Gradle is unusable. Any time you try to use it, it
spawns as much as processes and consoles your machine can support just to the
point it crashes. But unfortunately even removing gradle folder did not work.
After(? )/While(? ) downloading the Internet, same issue again!
>From the daemon-xxxx.out.logs it seems the issue lies-in/is-related-with
>"build.gradle line: 1030", ie
bq. exec { commandLine gradleRunner, '--no-daemon', 'installPlugin',
"-PpluginId=${pluginId}" }
BWT, doing so I noticed this minor, *unrelated* point to the resources
consumption issue I face, that you can also find in daemon-xxx.out.logq and is
worth to be noted here than to forget.
POM relocation to an other version number is not fully supported in Gradle :
xml-apis:xml-apis:2.0.2 relocated to xml-apis:xml-apis:1.0.b2.
Please update your dependency to directly use the correct version
'xml-apis:xml-apis:1.0.b2'.
Resolution will only pick dependencies of the relocated element. Artifacts and
other metadata will be ignored.
> 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
(v6.3.15#6346)
