Maven does awful things with console output - particularly in tests.
For tests, in the surefire configuration you can set
false for real time output. Also set it not to fork or
fork only once.
-Tim
On Sat, Aug 28, 2021 at 5:49 PM David Green wrote:
> Probably good advice but I was trying to
Probably good advice but I was trying to follow the direction of NetBeans
to use Maven as the preferred build tool.
At this point, for this semester, I am way too committed to Maven (it is an
online course with all the course content is done). This was a simple type
it in like the textbook
For those kind of projects use Ant or Gradle. They do not suffer from this
issue, and probably better suited for small student projects.
On Sat, Aug 28, 2021, 13:16 David Green wrote:
> Thanks for the reply and insight.
>
> That does work at the command line (as did running it from a jar file).
Thanks for the reply and insight.
That does work at the command line (as did running it from a jar file). I
am seeking to have it work in the NetBeans Output window and I found that
if I edited the Run (and Run File) Actions in the project properties to use
"java" instead of "exec", it does
In NetBeans 12.4 and verified to also behave this way on NetBeans
12.5-beta2, System.out.print is buffered such that it does not show up in
the NetBeans Output window until a System.out.println (or probably things
like program end, and some buffer full scenario).
Using JDK 15 and a Maven Project.
