This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Output window breaks slowly printed lines | ||
---|---|---|---|
Product: | projects | Reporter: | crosati <crosati> |
Component: | Ant | Assignee: | Jesse Glick <jglick> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | ||
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 56341 | ||
Attachments: |
System.out from MacOS X console
System.out from NB6 Output window How System.out from NB6 Output window should be |
Description
crosati
2007-11-02 17:58:25 UTC
please add both outputs as attachments. Issuzilla itself formats the text of comments. Are there any tab characters in the output? No tabs characters. As I can see issuezilla formatted correctly. However, I will attach the outputs. Claudio Created attachment 52407 [details]
System.out from MacOS X console
Created attachment 52408 [details]
System.out from NB6 Output window
Created attachment 52409 [details]
How System.out from NB6 Output window should be
the problem is probably somewhere in ant integration pulling the text from the application. I've tried to create a simple netbeans module that takes the correct output file and prints directly in the output window and it seems to produce correct layout. reassigning for evaluation Need some test case to reproduce. Is your application especially slow to print such lines? If it takes more than 250msec within a single line, an extra newline may be inserted. This was the only way to fix issue #56341. To write all the (wrong) output the application takes a little bit more than 30 sec. This means a mean time of 100ms per line. Confirmed for an example like public class SlowOutput { private SlowOutput() {} public static void main(String[] args) throws Exception { for (int i = 0; i < 20; i++) { System.out.print("some"); Thread.sleep(250); System.out.println(" text"); Thread.sleep(250); } } } If printing an individual line takes >250msec, a newline will be inserted, since Ant infrastructure is not able to print text without line breaks so it needs to be flushed (in case the app is e.g. waiting for input at a prompt). Since most people use println() on a complete line, this is not usually an issue, but if you print some text w/o NL and then do some computation before finishing the line, it will be observable. Workaround if necessary is just to buffer up text and print complete lines. Why this problem didn't occurred in NB 5? As I said, this change was necessary to fix issue #56341. |