[
https://issues.apache.org/jira/browse/OFBIZ-9182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906485#comment-15906485 ]
Jacques Le Roux commented on OFBIZ-9182:
----------------------------------------
Thanks Taher great work!
I'll answer to your last related message in the dev ML. To not make my answer too verbose there, I have a question here.
Maybe I read it wrong but reading the documentation I thought we would have a .svn directory in each plugin
bq. Download all officially supported plugins from source control (currently subversion) and place them inclusive of *their ".svn" directory* in /plugins.
Actually we have only one . svn for all plugins, and I very like it like it like that, much easier for maintenance, thanks! So maybe we should make the documentation more clear?
Also when I run pullAllPluginsSource I get
{code}
C:\projectsASF\ofbiz-framework>gradlew pullAllPluginsSource
:pullPluginsFromSvn
:pullAllPluginsSource
:installAllPlugins
No install task defined for plugin assetmaint
No install task defined for plugin bi
No install task defined for plugin birt
No install task defined for plugin cmssite
No install task defined for plugin ebay
No install task defined for plugin ecommerce
No install task defined for plugin example
No install task defined for plugin exampleext
No install task defined for plugin hhfacility
No install task defined for plugin ldap
No install task defined for plugin lucene
No install task defined for plugin myportal
No install task defined for plugin passport
No install task defined for plugin pricat
No install task defined for plugin projectmgr
No install task defined for plugin scrum
No install task defined for plugin solr
No install task defined for plugin webpos
{code}
I guess it's OK (no specific tasks to do OOTB in each plugins) but maybe we should document that in the the README? To avoid questions on this subject (and prevent my RTFM reflex ;)) or make answers easier by pointing to the documentation
> 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)
Locked
