[
https://issues.apache.org/jira/browse/OFBIZ-9182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877884#comment-15877884
]
Jacques Le Roux commented on OFBIZ-9182:
----------------------------------------
No no, I'm not assuming anything. I don't need to use plugins. It was just the
daemons which run amok and started again and again, continuning to try to
install plugins despite I did only ask to run OFBiz. Daemons are optional, so
it's not really an issue for me. Just that I was unlucky with my try and reading
bq. It is also possible to destabilize the Daemon (and build environment in
general) by running builds that do not release resources correctly. This is a
*particularly poignant* problem when using Microsoft Windows as it is less
forgiving of programs that fail to close files after reading or writing.
at https://docs.gradle.org/current/userguide/gradle_daemon.html I guess I got
those issues you can have with daemons in Windows (I did not report it all, it
was really exhausting).
I only reported here for people who could cross the same in unrelated
situations. I agree is not the best place for that, but since I started here...
> 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)
