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.
Preface: i'm using a DEV release of Netbeans 4.0 and pheraps this is a temporaney defect. Anyway, on dev 200410241800 (and on the previous version) when i wrote an initialized array, the Reformat Code mess the identation. So, this example: public class TestBug { /** Creates a new instance of TestBug */ public TestBug() { } public void dummy() { double[] m_VertexArray = { 1,2,3, 4,5,6, 7,8,9}; System.out.println("Wrong ident"); } } after the "Reformat Code" option, become: public class TestBug { /** Creates a new instance of TestBug */ public TestBug() { } public void dummy() { double[] m_VertexArray = { 1,2,3, 4,5,6, 7,8,9}; System.out.println("Wrong ident"); } } and somtimes i obtain this exception: Annotation: Exception occurred in Request Processor java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:787) at java.util.HashMap$KeyIterator.next(HashMap.java:823) at org.netbeans.modules.beans.PatternGroupNode$BeanParsingListener.resourceParsed(PatternGroupNode.java:475) at org.netbeans.modules.javacore.JMManager$6.run(JMManager.java:1277) at org.openide.util.Task.run(Task.java:136) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:330) [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:686)
CME in BeanParsingListener should be fixed since dev build 200410251800.
I've tried the dev build 200410251800, but the problem remains.
*** Issue 50833 has been marked as a duplicate of this issue. ***
I'll try to find a fix for 4.0
Issue should be addressed to TM 4.1, raising priority
*** Issue 51247 has been marked as a duplicate of this issue. ***
testcase from issue #51243 before indentation: public enum Operation { PLUS { double eval(double x, double y) { return x + y; } }, MINUS { double eval(double x, double y) { return x - y; } }, TIMES { double eval(double x, double y) { return x * y; } }, DIVIDE { double eval(double x, double y) { return x / y; } }; // Do arithmetic op represented by this constant abstract double eval(double x, double y); } after: public enum Operation { PLUS { double eval(double x, double y) { return x + y; } }, MINUS { double eval(double x, double y) { return x - y; } }, TIMES { double eval(double x, double y) { return x * y; } }, DIVIDE { double eval(double x, double y) { return x / y; } }; // Do arithmetic op represented by this constant abstract double eval(double x, double y); }
*** Issue 52907 has been marked as a duplicate of this issue. ***
another testcase from issue #55920: IndexColorModel colorModel = new IndexColorModel(8, 2, new byte[]{(byte) (background.getRed()-1), (byte) background.getRed()}, new byte[]{0, (byte) background.getGreen()}, new byte[]{0, (byte) background.getBlue()}, 0);
*** Issue 55920 has been marked as a duplicate of this issue. ***
*** Issue 56329 has been marked as a duplicate of this issue. ***
*** Issue 56743 has been marked as a duplicate of this issue. ***
Btw: this issue makes reformat code unusable if there are several arrays in the source file. Each such array moves the rest of source code to the right so the end of the file can be shifted e.g. by half of editor window. Adding fix-in-41 sw as this is quite annoying and has lots of dups. Remove the whiteboard if it's not feasible to fix.
Setting the statement continuation indent from 8 to 0 solves the problem. Anyway IMHO the indentation is broken because if it's set to 8 it should return back to correct level after the end of array declaration.
*** Issue 57918 has been marked as a duplicate of this issue. ***
Removed the fix-in-41 sw, we should address this issue in 4.2. Thanks.
*** Issue 59074 has been marked as a duplicate of this issue. ***
*** Issue 59077 has been marked as a duplicate of this issue. ***
Target milestone is obsolete, please re-evaluate. Thanks.
There's another wrong format on NB 4.1 if (dir!=null) for (int j=0;j<dir.length;j++) { String act=dir[j]; ; } instead of if (dir!=null) for (int j=0;j<dir.length;j++) { String act=dir[j]; ; } Pheraphs is the same issue.
*** Issue 61588 has been marked as a duplicate of this issue. ***
*** Issue 62240 has been marked as a duplicate of this issue. ***
Maybe P2 is justified, given how many duplicates there are...
Increasing priority to P2. It happens with Anagram game, it was observed on usability study and I've seen this bug too many times. Discussed on nbusers and nbfeedback, too.
We'll try to fix this into 5.0. At least we'll try to align next statement to the line which is preceded by the command delimiter which should avoid incorrect shifting the whole rest of the file.
We'll try to fix this into 5.0. At least we'll try to align next statement to the line which is preceded by the command delimiter which should avoid incorrect shifting of the whole rest of the file.
Making this a duplicate of issue 49306 (considering that one is older) as there is the same cause of the problem - the formatter bases the formatting according to the '{' which is incorrect for the arrays initialization commands. *** This issue has been marked as a duplicate of 49306 ***