[jira] [Commented] (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=17289601#comment-17289601 ] Laszlo Kishalmi commented on NETBEANS-5141: --- Well, when I designed the UI I found that putting all tasks in the context menu could be overkill, at least for my projects. The other plugin does not have a Navigator, so putting all tasks there was a necessary. Right now we have a Task Navigator, also with favorites. As of the alien source dir, I might change the current error node representation to a package node with a warning badge. Still doing that is a bad practice! > 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-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-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=17289448#comment-17289448 ] Antonio Marques commented on NETBEANS-5141: --- Imo it's not an IDE's job to completely disallow us from doing things the tools themselves allow (in this case, gradle). It's one thing to not have a UI for it, or not to write code to support it, but quite another to go the extra mile to make it impossible. But as I mention above, that's deeply seated in the NB team's mindset, and it would be a waste of everyone's time to debate it, so since I can work around that I'm glad I checked before I opened a ticket. As to the UI's '-x test', it's behaving as expected now, so I don't know how to replicate it anymore. I'll keep an eye on it. Thank you for helping me through this - using the Kelemen plugin with Java 11+ was just not feasible, at least in the projects I have here. There's still things about it that I like - e.g. it automatically adds all gradle tasks to the project's context menu - but that's outside the scope here. I'm unsure if this issue should continue open, as the drive for it is just not significant at this point. > 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-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-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=17288839#comment-17288839 ] Laszlo Kishalmi commented on NETBEANS-5141: --- As of "-x test". On the Tools > Options > Java > Grade > Execution > Global Execution Options By default it is marked Skip check which results a "-x check", however under that there is a Skip test that results a '-x test' for usual execution. If that would not happen it is a bug. As of including sources from other parts of the filesytem, that's a bad practice. Just imagine what shall the IDE do, if in this case a file in "websockets" theoretically belongs to two project which might have (and usually does) two different classpath which one shall the IDE use? That's why the error nodes are displayed for such a source directories. In this case if you use includeBuild, then there is no need (unless there is something really wrong here), to add the sources that way. Just add a dependency with group:artifact:version in the dependencies. Gradle will take care of the paths. Also there is a bug in NetBeans 12.2 which results an IAE on imported builds, that has been fixed in 12.3-beta3 > 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-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-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=17288826#comment-17288826
]
Antonio Marques commented on NETBEANS-5141:
---
OK, your proposal seems to work. Moreover, the user's gradle.properties file is
even show in each project's tree, which allows easy checking/editing.
I haven't found a way to add *-x test* (being on macOS, using *GRADLE_OPTS* is
more work than it's worth), but I added
{code:groovy}
test.onlyIf { gradle.startParameter.taskNames.contains('test') }
{code}
to *build.gradle*. I do have the option checked in the Preferences, but it
doesn't seem to translate to every project in a build chain.
Now I'll pose an offtopic question, lest I go open a dumb issue (I did search
for this, but no luck so far): In a number of projects, we have sources outside
the project root, and we've always included them thus:
{code:groovy}
sourceSets {
main {
java {
srcDirs 'src/main/java'
srcDirs '../websockets/src/main/java'
...
{code}
Now, it happens that the plugin seems to ignore those sources. Not, however,
during the build phase, the project builds fine, but the external source dirs
don't appear in the project navigation AND the classes in them aren't picked up
by dependent projects. (I should point out that the dependent projects are
setup independently, not as a gradle nested project; they include the main
project via *includeBuild*). Again, the dependent projects build OK, but the
IDE complains all over about the 'missing' classes. The only place those
external sources are shown is in the project properties dialog.
Many years ago I had a similar problem with external sources and had to end up
using Eclipse(!). It was nothing gradle-related, of course.
> 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-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-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=17288796#comment-17288796 ] Antonio Marques commented on NETBEANS-5141: --- I'll try that and get back to you, thanks. > 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-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-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=17288784#comment-17288784 ] Laszlo Kishalmi commented on NETBEANS-5141: --- Hmm, I do not see why those user-specific arguments can't be placed into the user's gradle.properties file at $GRADLE_HOME/gradle.properties Telling the truth, implementing such a feature might not be a hard one. But those kind of customization usually leads to : It work in command line, why does it not in my IDE, then it turns out that we have some customization in the IDE. I see your point, but what is the usecase, that can't be solved without this feature? > 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-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-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 commented on NETBEANS-5141:
---
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-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-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=17288741#comment-17288741 ] Laszlo Kishalmi commented on NETBEANS-5141: --- Setting org.gradle.jvmargs is an option. NetBeans honors that. > 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-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-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=17288539#comment-17288539 ] Antonio Marques commented on NETBEANS-5141: --- Is this something that has a workaround, is it a no-go, or is it just low priority? > 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-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
