You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 21, 2019. It is now read-only.
Netbeans platforms is executed using nbexec that take into account various configurations as Look and Feel and various java options like available memory.
On the other hand, surefire directly execute test classes with a simple java call. Hence, any problem related nbexec configuration cannot be tested.
Is it in the roadmap of this project to provide a testing mechanism using nbexec? Does anyone already encounter this kind of issue and found a workaround?
The text was updated successfully, but these errors were encountered:
Hi, I'm not sure this will answer your question but it is possible to add add args and systemproperties to surefire configuration
@{argLine} -J-Xmx12g -J-Xss2m -J-Xms12g -J-Dsun.java2d.noddraw=true
I don't know the args for changing le L&F but is should be possible I guess
Yes indeed. But there seems to be options specific to nbexec. I don't know much about this launcher, could it be completely replaced by arLine options. My attempts to add the look and feel by that method failed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Netbeans platforms is executed using nbexec that take into account various configurations as Look and Feel and various java options like available memory.
On the other hand, surefire directly execute test classes with a simple java call. Hence, any problem related nbexec configuration cannot be tested.
Is it in the roadmap of this project to provide a testing mechanism using nbexec? Does anyone already encounter this kind of issue and found a workaround?
The text was updated successfully, but these errors were encountered: