What is configuration is in use for this (i.e. Netbeans version, Java version, Netbean...About) ?
What project are you using (i.e. how big is it)? Not sure if maybe this requires a larger project to trigger more indexing behavior but... 1. Running with 12.5 Beta2... 2. Created a very basic gradle java class with a HelloMain and a dependency HelloWorld class with an execute call defined and used elsewhere. 3. Selected the execute method and used "Find Usage" and it seems to work. .. 4. Refectored (renamed) "execute" method to "run" method and it seems to work 5. Created a very basic maven java class, copied the HelloWorld class from gradle to maven project which open Refactor dialog 6. Refactor preview showed what was to occur (i.e. change package from old to new) 7. Do Refactor executed successfully 8. Shift-Alt-O opens dialog and starts looking for "HelloWorld" which shows both projects versions of it. Possible Unrelated documentation issues, 1. When selected Find Usage on a given class, the dialog shows the below 2. Find out more" takes to https://netbeans.apache.org/wiki/Find_Usages_in_Compiled_Dependencies.asciidoc (not html version) and the pages does not exist. 3. Not sure if the site didn't get built correctly recently, the page is no longer available or the dialog needs to be updated to someplace else. Warning: Disclaimer: Searching for usages in compiled dependencies has certain limitations. Find out more. <http://wiki.netbeans.org/Find_Usages_in_Compiled_Dependencies> Eric Bresie ebre...@gmail.com On Fri, Aug 27, 2021 at 3:42 PM Eirik Bakke <eba...@ultorg.com> wrote: > (Starting a new thread as suggested by Geertjan...) > > I have seen broken refactoring operations as well. Most notably, "Find > Usages" on a Java method will sometimes miss call sites. I have also seen > methods and classes missing when searching from the Go to Symbol dialog. > Probably the same underlying cause. I don't know how to reproduce this, > however. > > For comparison, NetBeans 8.4 (pre-Apache, and with Java 8) was always > completely reliable. > > Exiting the IDE, deleting the cache directory, and starting the IDE again > have always fixed these problems for me. So I suspect indexing errors are > the cause. > > I used to see a lot of error messages relating to the IDE not being able > to parse a java file, although in later releases things have gotten a lot > better. I also have high hopes that the new "vanilla indexing" system (Java > indexing without the nb-javac plugin) may improve things. > > All of my projects are Maven-based NetBeans Platform module projects, with > Compile-on-Save enabled. > > -- Eirik > > -----Original Message----- > From: Geertjan Wielenga <geertjan.wiele...@googlemail.com.INVALID> > Sent: Monday, August 16, 2021 10:12 AM > To: dev <dev@netbeans.apache.org> > Subject: Re: VSCode > > Start a new thread on it and point to the specific issues, or create new > ones with steps to reproduce (I use NetBeans regularly including > refactoring, would like to see these issues), let's get it fixed. > > Gj > > -----Original Message----- > From: Ty Young <youngty1...@gmail.com> > Sent: Monday, August 16, 2021 10:09 AM > To: dev@netbeans.apache.org > Subject: Re: VSCode > > Just going to point out that refactoring(renaming methods, others) on > Netbeans is still broken... as it has been for years. >
