[
https://issues.apache.org/jira/browse/OFBIZ-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395682#comment-15395682 ]
Pierre Smits commented on OFBIZ-7808:
-------------------------------------
Actually it is both appropriate and good.
Both elements define how adopters can extend the existing build.gradle without having the risk of conflicts (through svn up) when build.gradle gets upgraded by the project.
And the two skeletons could be treated by the project the same way as it does with respect to the hot-deploy folder.
It offers control for the project and flexibility (and risk mitigation) for the adopter.
> Add Gradle Interactive tasks
> ----------------------------
>
> Key: OFBIZ-7808
> URL:
https://issues.apache.org/jira/browse/OFBIZ-7808> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: Trunk
> Reporter: Jacques Le Roux
> Assignee: Jacques Le Roux
> Fix For: Upcoming Branch
>
>
> As explained in OFBIZ-7772 and OFBIZ-7773 we want to test the possiblity to add Gradle Interactive tasks using
https://github.com/tkruse/gradle-groovysh-plugin> The idea is to have a good general solution to allow users to not feel a funtional regression with the 3 interactive tasks we had before, namely
> create-component
> create-admin-user-login
> create-tenant and all tasks it depends on
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
