No, I use Netbeans and just turned off incremental deploys. That bug was just too brutal. I have a decent machine, and our app isn't that huge, so full deploys aren't crippling, and were nothing compared to the incremental deploys when it did a full deploy. Whatever benefit we were getting from the incremental deploys (which were speedy) were lost when we did a full deploy, just killed us.
So, we punted and went with the standard full deploy. At least it was consistent.
Now that they're fixing the bug, I hope to be able to use the incremental deploy.
I was also quite disappointed to learn the cause of the bug.
The code they was literally:
while(int c = inputStream.read() != -1) {
outputStream.write(c);
}
One of the first things we learned Back In The Day was how horribly inefficient that kind of I/O is, that you should always use buffered I/O to limit I/O and call overhead. A classic anti-pattern over 30 years old.
Apparently, the coders didn't learn that detail, and the system they tested on didn't suffer from it.
XP, though, obviously did. Disappointing to see that level of code in Netbeans.
[Message sent by forum member 'whartung' (whartung)]
http://forums.java.net/jive/thread.jspa?messageID=284517