[
https://issues.apache.org/jira/browse/OFBIZ-7972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489681#comment-15489681 ]
Taher Alkhateeb edited comment on OFBIZ-7972 at 9/14/16 7:31 AM:
-----------------------------------------------------------------
Okay this new patch delivers the following:
- Fix the documentation in README.md
- Renamed removePlugin and addPlugin to deactivatePlugin and activatePlugin as per Michael's suggestion
- Introduce a task called removePlugin that in addition to uninstalling a plugin also deletes it from the filesystem as recommended by Michael and Gil.
- Make the componentResourceName capitalized (Thank you Gil for the code snippet)
was (Author: taher):
Okay this new patch delivers the following:
- Fix the documentation in README.md
- Renamed removePlugin and addPlugin to deactivatePlugin and activatePlugin as per Michael's suggestion
- Introduce a task called removePlugin that in addition to uninstalling a plugin also deletes it from the filesystem as recommended by Miachael and Gil.
- Make the componentResourceName capitalized (Thank you Gil for the code snippet)
> Create a (PoC) plugin system for OFBiz based on Gradle
> ------------------------------------------------------
>
> Key: OFBIZ-7972
> URL:
https://issues.apache.org/jira/browse/OFBIZ-7972> Project: OFBiz
> Issue Type: Improvement
> Affects Versions: Upcoming Branch
> Reporter: Taher Alkhateeb
> Assignee: Taher Alkhateeb
> Priority: Minor
> Labels: plugin, proof-of-concept, system
> Attachments: OFBIZ-7972.patch, OFBIZ-7972.patch
>
>
> This JIRA houses the attempt to create a plugin system for OFBiz based on gradle. The plugin system should have the following features:
> - It is independent of the version control system, file system, operating system and any other environment tools surrounding OFBiz. Instead, it should be fully integrated with OFBiz.
> - It should unify the way OFBiz is extended, both for official supported plugins and for third party plugins
> - The plugin system takes advantage of the concept of a "component" in OFBiz and utilize it as the building block for plugins
> - The plugin system supports the concepts of "Repository" and "Dependency Management". If possible, the plugin system will utilize these concepts directly from Gradle instead of writing them from scratch.
> The initial API for the plugin system will be small and expands as needed. The API should include the following gradle tasks:
> - createPlugin: creates a new plugin based on templates and place it in the plugins directory
> - installPlugin: Activate a plugin and run Install. Plugin must exist in /specialpurpose
> - uninstallPlugin: Deactivate a plugin and run its uninstall script
> - publishPlugin: publish a plugin to local maven repository
> - pullPlugin: download a plugin with its dependencies (plugins) from a repository and install them
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
