[jira] [Commented] (NETBEANS-2735) Gradle - Custom tasks (in gradle.properties) do not propagate to sub-projects
[ https://issues.apache.org/jira/browse/NETBEANS-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16917117#comment-16917117 ] Mathieu Fournier commented on NETBEANS-2735: It would be very useful in any project that contains lots of subprojects to avoid to recreate a custom task for every sub-project. * As a workaround for issue NETBEANS-2737 (we could override the "test" action on the root project and not have to do it on all sub-projects) * To be able to exclude "long" tests when running "test" action * Add a "build all" task that builds the project and compiles the tests * Any custom task that can apply to all sub-projects of a project... > Gradle - Custom tasks (in gradle.properties) do not propagate to sub-projects > - > > Key: NETBEANS-2735 > URL: https://issues.apache.org/jira/browse/NETBEANS-2735 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.0 > Environment: Windows 10 > NetBeans 11.0 > RedHat's OpenJDK 11.0 >Reporter: Mathieu Fournier >Assignee: Laszlo Kishalmi >Priority: Major > > When we create a task via the "Run Gradle"/"Tasks..." screen on the root > project, it won't show in the context menu for sub-projects. It is only > available on the root project. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-2735) Gradle - Custom tasks (in gradle.properties) do not propagate to sub-projects
[ https://issues.apache.org/jira/browse/NETBEANS-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915720#comment-16915720 ] Laszlo Kishalmi commented on NETBEANS-2735: --- Right now that is by design. Do you have a use case, how would you use it if these actions were kind of "inheritable" from the root project? > Gradle - Custom tasks (in gradle.properties) do not propagate to sub-projects > - > > Key: NETBEANS-2735 > URL: https://issues.apache.org/jira/browse/NETBEANS-2735 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.0 > Environment: Windows 10 > NetBeans 11.0 > RedHat's OpenJDK 11.0 >Reporter: Mathieu Fournier >Assignee: Laszlo Kishalmi >Priority: Major > > When we create a task via the "Run Gradle"/"Tasks..." screen on the root > project, it won't show in the context menu for sub-projects. It is only > available on the root project. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
