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.
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.
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.
regards,
-mbien
On 17.11.24 00:35, Will Hartung wrote:
Can I use the Maven Indexer CLI to maintain the maven index that NB
manages internally?
Specifically, I'd like to just have it run "routinely" (like, say,
overnight) to keep the local index up to date.
More specifically, I never want to see "unpacking index..." progress
bar in my IDE ever again.
It is a never ending pain point of frustration when it occurs.
I tend to leave my machine running for weeks on end, NB constantly
open, and, inevitably if I have to restart NB, it's likely not because
I "want to", but because "something happened" that forced a restart.
And, inevitably, it triggers a reload or whatever of the index and
shuts me down for far too long while it does whatever it does. Or
simply having to be conscious of the concept of "oh I better launch NB
so it can go through that update while I do something else".
Just now, I was doing something in NB. I started it days ago, and just
let it sit. And, of course, now, for my 10 line "hello world" project
I was messing with, off it goes. I was simply trying to update the pom
file to a later plugin version. "Oh, so sorry, updating the Index, so
go suck an egg meat sack, I'm busy". As if "oh, they started me, but
I'm going to do this lazily when they NEED it, instead of right away
when I launch." Thanks a lot.
So, if I can externalize the process to run on something elses time
(i.e. not mine), all the better.
And my brief research led me to the discovery that the Maven Indexer
has a CLI (and that's all I know, that there is something called
"Maven Indexer", and that it has a CLI, and that the NB maven.index
module in NB has a reference to it). So I was curious if that could be
used to handle this task.
Or, of course, is there some other way to never get blocked by the
indexer.
Thanks!
Regards,
Will Hartung
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
