[
https://issues.apache.org/jira/browse/OFBIZ-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393613#comment-15393613 ]
Pierre Smits commented on OFBIZ-7808:
-------------------------------------
As a solution to this discussion we could consider adding the following two elements to the build.gradle:
# apply from: 'implementationSpecificBuild.gradle'
# ant.importBuild 'build.xml'
And provide skeletons for both (and not being under the control of the project through e.g. .ignore)
The first will enable adopters to develop their deployment specific Gradle tasks, and the second will enable the existing adopters to re-use their existing custom Ant tasks with out having to spend effort regarding migration.
The added value is also that the contributors of project can focus on OOTB solutions and functions.
> 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
