This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
On Services -> Maven repositories, right-clicking on a repository and choosing Update Index does not download the update index and reparses it. Product Version = NetBeans IDE Dev (Build 20130110-1f77a08481ab) Operating System = Windows 7 version 6.1 running on amd64 Java; VM; Vendor = 1.7.0_01 Runtime = Java HotSpot(TM) 64-Bit Server VM 21.1-b02
are you positive that the update has changed? in pre 7.3 (maybe 7.2) times there was a bug that caused the entire index recreation everytime update index was triggered, now we only check if there's updates and if not (indexer downloads a single properties file to see) we don't do anything. And there is a new index, we only download the diff, so even the processing will be much faster.
was meant to be "are you positive that the remote index has changed?"
Yes, I am. In this particular instance, I saw a commit in bitbucket from the Maven release plugin in an internal project, 30 minutes or so after it had been pushed. When I tried to use code completion for the desired release number, I got nothing, so I updated the index. Since I saw no progress bar being displayed, I closed the pom which I was modifying, hit update again, opened the pom again and it hadn't worked yet. So I manually entered the version number in the pom file and built my project and it worked.
(In reply to comment #3) > Yes, I am. In this particular instance, I saw a commit in bitbucket from the > Maven release plugin in an internal project, 30 minutes or so after it had been > pushed. When I tried to use code completion for the desired release number, I > got nothing, so I updated the index. Since I saw no progress bar being > displayed, I closed the pom which I was modifying, hit update again, opened the > pom again and it hadn't worked yet. So I manually entered the version number in > the pom file and built my project and it worked. can you see the new version in repository browser? eg. when expanding the nodes or when triggering "Find"? What repository manager are you using? The index on the server might not be immediately updated once new content lands on the repository. It could be updated eg. once a day by a scheduled tasks taht crawls the local storage, contacts remote repository it proxies etc..
Sorry for the delay, this notification got lost. I could see it in the index. We use an internal Nexus installation.
I still cannot reproduce locally. For me the index diff gets downloaded correctly when I experiment with my local nexus instance. Please note that the updating is fully under maven indexer control. it first checks the properties file on the server to learn if there are updates. It would be worthwhile if you could check the file manually. Both on the server and in local cache (mavenidex/ subfolder). If they are equal, then as far as the indexer is concerned, there are not update (I think), based on the files, the indexer also decides if entire index or only update is downloaded. I've double checked the pom completion and AFAIK the values once completed are not cached
tried again with latest dev builds and it works for me. I get updates from my local nexus instance. please reopen with more details.