[
https://issues.apache.org/jira/browse/OFBIZ-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393199#comment-15393199 ]
Taher Alkhateeb commented on OFBIZ-7808:
----------------------------------------
A quick comment folks:
- createTenant has only 2 mandatory args (and we can even reduce it to 1)
- We agreed in an email thread to have only one mandatory argument for createComponent (we should start a Jira for that)
- We only have one argument for createAdminUserLogin
So is it worth creating interactive tasks for only one argument? If I am a beginner then I will not use the other flags but rather just the mandatory one.
I would imagine creating interactive tasks really worth it if I have a very complex build process to make it easy for users. So the only task that might slightly even qualify for being interactive is createTenant assuming the user is going for a non-derby database. At a point when a user knows how to switch from Derby to MySQL with all the setup needed I doubt this user would need help in passing arguments to the build system.
> 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
