IntelliJ Ultimate - Issue with Maven 'Maven Artifact Search' Not Returning Results
Answered
I'm trying to add dependencies in IntelliJ Ultimate using the "Generate Dependencies" feature. However, when I open the "Search for Artifact" window and type a keyword, no results are displayed. It should return relevant dependencies related to the search term, but it doesn't show anything. How can I resolve this issue?


Please sign in to leave a comment.
Hello, Gianmarco!
Thank you for reporting this!
This issue might be caused by the issues with IDEA's repository indices or connectivity problems.
Could you please try reindexing the repositories (Maven Tool Window → [Project Name] → Repositories → [Right-click a Repository] → Reindex repository).
If the issue persists please share the logs (Help → Collect Logs and Diagnostic Data).
You can upload the logs using our upload service, in that case please share the Upload ID.
I tried the proposed solution of:
Could you please try reindexing the repositories (Maven Tool Window → [Project Name] → Repositories → [Right-click a Repository] → Reindex repository).
I did it with both my local and central repositories. Now, after this, the error was partially resolved. When I search by artifact, the error still persists, but when I search by class, the results do appear. I should also mention that if I reindex the local repository three times, I get an error when searching by class. It says "loading" and stays stuck there.
I’m sending you what you requested. Thank you in advance for your response.
Note: When reindexing the local repository, a notification appeared saying "scanning artifacts," but no notification appeared when reindexing the central repository.
Upload ID: 2024_09_20_7efX8oNtmdVjGLv32Gnr27
Gianmarco Lavado Thank you for the update and for uploading the logs!
Please try the following:
Maven” folder found inside the System DirectoryAlso, please let me know if there are any proxies, firewalls or other solutions that may block / alter the network traffic in your environment.
Hopefully this is helpful, the search field appears to behave as expecting regex input.
In my case I tried
.serand see expected resultsHowever if I simply typed
seras I imagine most people would, I see undesirable results or nothingFuture updates should help alleviate frustrations.
Regards,