On Sat, Nov 16, 2024 at 6:17 PM Michael Bien <mbie...@gmail.com> wrote:
> Hi, > > the index updates happen in the background, can you clarify what you > mean by being "blocked by the indexer"? It shouldn't block anything. > A specific example is in the pom file, you can go to a dependency, blank out the version field, CMD-SPACE for the autocomplete, and it will show you "all" of the versions available. There are times when I do that and I get an "Incomplete result, still processing indices" or something like that message. At that point, I'm effectively stuck. > If it happens at a time you don't want it to run and it already started > (e.g low battery), you can simply cancel the task and it won't try again > for a few hours or toggle remote index downloads in the options. > If I run into it again, I can try to cancel and see if those messages go away. > One way to keep it up to date would be to let NB check on startup or > daily for updates (also in the indexer options). Note, that this doesn't > mean that every check automatically results in an update, since it will > only update if the remote index actually published a new segment. > > There is no supported way to manage the index externally atm. The index > import is a bit customized and drops a few fields. It might still work > but the footprint might be larger and this is not tested. > > > Also keep in mind that remote index downloads are completely optional. > In case you don't use maven or NetBeans that often: NetBeans does also > scan the local maven cache, so most features will be still functional > even though information about the newest artifacts won't be available > until they are in the cache. > I use NB extensively and maven exclusively, so for me I don't consider this optional. Thanks for the info. Regards, Will Hartung
