[
https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386596#comment-15386596 ]
Jacques Le Roux commented on OFBIZ-7910:
----------------------------------------
This is interesting Pierre, but I'd wait to have more directions and possibly actions to put in this file. When looking at Taher's last explanations about the differences between hot-deploy and "plugins" components
http://markmail.org/message/w57kadgs5kewwvjsbq. * The difference between createComponent and createPlugin is that the plugin resides in /plugins instead of hot-deploy and added to component-load.xml and also contains a build.gradle file designed specifically for plugins. This script contains standard tasks like install, uninstall, perhaps even upgrade. The magic work for plugins will be in their build scripts to integrate tightly with OFBiz.
I begin to wonder if hot-deploy components would not be less interesting than "plugins" components. Actually, I think we need to think more about the differences between hot-deploy and "plugins" components, and maybe dare to ask this question: "Could we not have only plugins?". Will it else not be confusing for users? Maybe another discussion about those 2 concepts is worth a new thread on dev ML?
> Improve component template(s) to work with the Gradle solution
> --------------------------------------------------------------
>
> Key: OFBIZ-7910
> URL:
https://issues.apache.org/jira/browse/OFBIZ-7910> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
> Reporter: Pierre Smits
> Assignee: Jacques Le Roux
> Attachments: OFBIZ-7910-Resources-build.gradle.patch
>
>
> Currently the component generated with the createComponent task doesn't have the means to work with the Gradle build solution visavis dependency management.
> The reason for this is that no build.gradle template exists that need to be copied into the new component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
