[ 
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

Reply via email to