|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
|
|
Three annoying bugs with NetBeans 6.11: Breakpoints in startup code don't get triggered in my web application. In other words, I set a breakpoint within a certain method that's called during initialization, and the debugger skips right by it. I know the code is being called because I'm logging to a log file. Later, after startup, the same breakpoint works perfectly. It's only during startup that breakpoints seem to be flaky. This makes debugging certain bugs difficult.
2: Often the project view will show the red error symbol over all my source code. I have to open a file from each "source group", and pause in the editor for six seconds, and the error symbols over all source code in that source group will disappear. The source code had no errors to begin with, so the IDE should have figured this out by itself. 3: Mercurial commit is finnicky. I often have to try over a dozen times before the commit actually takes. This is with a new project, with Mercurial integration configured through the IDE. FYI, I'm using Mercurial 1.0, which triggered a warning message in NetBeans. Despite these issues, I love the NetBeans 6.0 + 6.1 releases. |
|
|
Re: Three annoying bugs with NetBeans 6.1MassimoH wrote:
> 1: Breakpoints in startup code don't get triggered in my web application. In > other words, I set a breakpoint within a certain method that's called during > initialization, and the debugger skips right by it. I know the code is being > called because I'm logging to a log file. Later, after startup, the same > breakpoint works perfectly. It's only during startup that breakpoints seem > to be flaky. This makes debugging certain bugs difficult. > > 2: Often the project view will show the red error symbol over all my source > code. I have to open a file from each "source group", and pause in the > editor for six seconds, and the error symbols over all source code in that > source group will disappear. The source code had no errors to begin with, so > the IDE should have figured this out by itself. > > 3: Mercurial commit is finnicky. I often have to try over a dozen times > before the commit actually takes. This is with a new project, with Mercurial > integration configured through the IDE. FYI, I'm using Mercurial 1.0, which > triggered a warning message in NetBeans. > > Despite these issues, I love the NetBeans 6.0 + 6.1 releases. > I can respond only to the third issue you described. Could you elaborate more, what does not work? I am using Mercurial plugin without any problem (though it could be faster). When you push commit, nothing is committed or what exactly is the problem? The warning dialog is a bit confusing, we know. The module was implemented for the latest Mercurial version at that time. But it works with any newer and also with TortoiseHg. Martin |
|
|
Re: Three annoying bugs with NetBeans 6.1The commit just doesn't work. I select "commit" from the menus and I get a good message in the Mercurial console window, but nothing gets committed. Looking through my NetBeans log files I see this Mercurial exception (I recently filed under [Issue 134906]): SEVERE [org.openide.util.RequestProcessor] java.lang.ClassNotFoundException: org.ini4j.IniParser at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at org.apache.tools.ant.module.bridge.AntBridge$MaskedClassLoader.loadClass(AntBridge.java:667) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.ini4j.ServiceFinder.findServiceClass(ServiceFinder.java:142) Caused: java.lang.IllegalArgumentException: Provider org.ini4j.IniParser not found at org.ini4j.ServiceFinder.findServiceClass(ServiceFinder.java:146) at org.ini4j.ServiceFinder.findService(ServiceFinder.java:174) Caused: java.lang.IllegalArgumentException: Provider org.ini4j.IniParser could not be instantiated at org.ini4j.ServiceFinder.findService(ServiceFinder.java:178) at org.ini4j.IniParser.newInstance(IniParser.java:42) at org.ini4j.Ini.load(Ini.java:247) at org.ini4j.Ini.<init>(Ini.java:185) at org.netbeans.modules.mercurial.config.HgConfigFiles.loadSystemAndGlobalFile(HgConfigFiles.java:350) at org.netbeans.modules.mercurial.config.HgConfigFiles.<init>(HgConfigFiles.java:101) at org.netbeans.modules.mercurial.config.HgConfigFiles.getInstance(HgConfigFiles.java:114) at org.netbeans.modules.mercurial.util.HgCommand.doCommit(HgCommand.java:1651) at org.netbeans.modules.mercurial.ui.commit.CommitAction.performCommit(CommitAction.java:381) at org.netbeans.modules.mercurial.ui.commit.CommitAction.access$100(CommitAction.java:90) at org.netbeans.modules.mercurial.ui.commit.CommitAction$3.perform(CommitAction.java:237) at org.netbeans.modules.mercurial.HgProgressSupport.performIntern(HgProgressSupport.java:98) at org.netbeans.modules.mercurial.HgProgressSupport.run(HgProgressSupport.java:91) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:561) [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:986) |
|
|
Re: Three annoying bugs with NetBeans 6.1I've had this issue a couple of times in 6.1. One time every file in my project was marked with errors. The project depended upon another open project and all of its imports were marked as errors. Both projects built and compiled fine. If I recall correctly, to fix it, I tried the following: 1) opening a few files and waiting (that did nothing) 2) Restarting NetBeans (did nothing) 3) Closing the project and opening it again (did nothing) 4) Closing the project, restarting netbeans, and opening it again (did nothing). Finally, I just opened every single file in the project and it magically fixed itself. I'll add my own annoying bug (actually it was more amusing then annoying!) :) Somehow I managed to open the same file in two separate editor tabs. I don't know if it's a feature or a bug :) |
|
|
Re: Same file in two separate editor tabsjonaqua wrote:
> Somehow I managed to open the same file in two separate editor tabs. I > don't know if it's a feature or a bug :) It's a feature, of course! :-) In this case, it is really a feature - if you right-click on an editor tab, you can see item "Clone Document" in the pop-up. It does exactly what you describe - opens the same file in a separate editor tab. It allows you to work with two parts of the same file without permanent scrolling up and down. You can also drag the cloned tab to another are of the editor so you can see these two parts side by side, or one on top of the other. Marián |
|
|
Re: Three annoying bugs with NetBeans 6.1
MassimoH wrote:
And does it work from console? This may be connected to issue 134924 I've encountered yesterday. But as you said that if you try it more times, it proceeds eventually? This seems to be different from that issue... I see that you filed a bug 134906, thank you. I will continue in my comments there. Martin |
|
|
Re: Three annoying bugs with NetBeans 6.1jonaqua wrote:
> > MassimoH wrote: > >> 2: Often the project view will show the red error symbol over all my >> source code. I have to open a file from each "source group", and pause in >> the editor for six seconds, and the error symbols over all source code in >> that source group will disappear. The source code had no errors to begin >> with, so the IDE should have figured this out by itself. >> >> > > I've had this issue a couple of times in 6.1. One time every file in my > project was marked with errors. The project depended upon another open > project and all of its imports were marked as errors. > > Both projects built and compiled fine. If I recall correctly, to fix it, I > tried the following: > > 1) opening a few files and waiting (that did nothing) > 2) Restarting NetBeans (did nothing) > 3) Closing the project and opening it again (did nothing) > 4) Closing the project, restarting netbeans, and opening it again (did > nothing). > > Finally, I just opened every single file in the project and it magically > fixed itself. > > > I'll add my own annoying bug (actually it was more amusing then annoying!) > :) > Somehow I managed to open the same file in two separate editor tabs. I > don't know if it's a feature or a bug :) > there are still some problems with error badges - the issue http://www.netbeans.org/issues/show_bug.cgi?id=121950 should summarize this cases. If your problem is none them, please file a new issue, providing as many information about your project configuration as you can. Probably the problem is that IDE cannot find some class for some reason and marks its usages in other code as error. If you open this class and modify it (it's enough to add space) the IDE will reparse it and the error badges should be removed. Regards Jirka |
| Free Forum Powered by Nabble | Forum Help |