Hi! NetBeans gets artifact information from two places:
it watches your .m2/repository folder and creates a local index for it. This is enabled by default and is pretty quick. This it how it knows about your snapshot builds, downloaded sources of your dependencies etc. Optionally it does also download the remote index from maven central and keeps it up to date whenever updates are available. Before doing that it asks for permission via a notification, since the maven central index grew over time and has some storage overhead. New segments for the remote index are supposed to be published on a weekly basis, but I saw it falling behind a few times - looks like that is the case right now again. So unfortunately forcing an update won't work since there is nothing to update atm. To find possible updates (analog to dependabot) you could run the global "Compute Libyear" goal which will list update options with some extra stats. (right click on project -> Run Maven) or even define your own goals which update poms and put it on a toolbar button. (e.g eu.maveniverse.maven.plugins:toolbox:dependency-versions -Dapply=true) btw: If you use 2.40.5 once, directly or indirectly, NB will learn that it exists, since it would be in the local index. regards, -mbien On 12/10/25 11:55, Tilman Hausherr wrote: > > Hello, > > Somehow Netbeans "knows" what versions of a dependency are available when > pressing CTRL-SPACE (see screenshots below). This is great, however it is > often behind, even after builds are run. In the screenshots the latest > version is 2.40.5, but Netbeans only "knows" until 2.39.5. Is there a way to > get netbeans to update its own knowledge more often? (The screenshots are > from the Apache Tika pom.xml) > > Tilman > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
