You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@netbeans.apache.org by "Antonio Marques (Jira)" <ji...@apache.org> on 2021/02/23 01:52:00 UTC
[jira] [Comment Edited] (NETBEANS-5141) Support custom global
gradle arguments and gradle JVM arguments
[ https://issues.apache.org/jira/browse/NETBEANS-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17288780#comment-17288780 ]
Antonio Marques edited comment on NETBEANS-5141 at 2/23/21, 1:51 AM:
---------------------------------------------------------------------
That may be a solution to the JVM args, but what about the gradle args?
For instance, when I run one my projects from the Kelemen plugin it says something like:
{{Executing: gradle build}}
{{Arguments: [-x, test, -x, check, -PcmdLineArgs=--cmd.arg1=value1 --cmd.arg2=value2, -Pcustom-gradle-arg1, -Pcustom-gradle-arg2=VAL2, --stacktrace, -c, /Users/.../settings.gradle]}}
{{JVM Arguments: [-Xmx1g, -XX:MaxMetaspaceSize=512m, -XX:+HeapDumpOnOutOfMemoryError]}}
These gradle args are usually user-specific but not project-specific within the same user.
(The JVM args aren't actually very important for our use case.)
was (Author: entonio):
That may be a solution to the JVM args, but what about the gradle args?
For instance, when I run one my projects from the Kelemen plugin it says something like:
{{Executing: gradle build}}
{{Arguments: [-x, test, -x, check, -PcmdLineArgs=--cmd.arg1=value1 --cmd.arg2=value2, -Pcustom-gradle-arg1, -}}{{Pcustom-gradle-arg2=VAL2}}{{, --stacktrace, -c, /Users/.../settings.gradle]}}
{{JVM Arguments: [-Xmx1g, -XX:MaxMetaspaceSize=512m, -XX:+HeapDumpOnOutOfMemoryError]}}
These gradle args are usually user-specific but not project-specific within the same user.
(The JVM args aren't actually very important for our use case.)
> Support custom global gradle arguments and gradle JVM arguments
> ---------------------------------------------------------------
>
> Key: NETBEANS-5141
> URL: https://issues.apache.org/jira/browse/NETBEANS-5141
> Project: NetBeans
> Issue Type: New Feature
> Components: projects - Gradle
> Reporter: Antonio Marques
> Assignee: Laszlo Kishalmi
> Priority: Major
>
> In the Kelemen plugin ([https://github.com/kelemen/netbeans-gradle-project)] it is possible to set global arguments to add to the gradle command line, as well as to the gradle JVM command line (Preferences \ Miscellaneous \ Gradle \ Scripts and Tasks). This is essential if your build scripts respond to custom parameters that you don't want to replicate across every specific project. The Kelemen plugin uses two textareas, of line-separated options. I don't see such a feature in the current implementation, though there are places in the Preferences where it could be placed.
> This may only be useful for some, but for those of us for whom it is useful, it's essential. Until it's in place, our only option is to keep using the Kelemen plugin (which I have nothing against, but there must be a reason why there's s separate implementation on NB).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@netbeans.apache.org
For additional commands, e-mail: commits-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists