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.

Bug 254313

Summary: Add Maven search that uses the online APIs instead of the local index
Product: projects Reporter: emi <emi>
Component: MavenAssignee: Tomas Stupka <tstupka>
Status: NEW ---    
Severity: normal CC: hmichel, markiewb
Priority: P3    
Version: 8.1   
Hardware: All   
OS: All   
Issue Type: ENHANCEMENT Exception Reporter:

Description emi 2015-08-12 13:39:19 UTC
Maven Central seems to have a REST API for search. It would be ideal when adding a dependency not to use the local index but just query online.

This could be a flag in the Maven setting page where the user could pick between local/index or online search.
Comment 1 maxnitribitt 2015-08-13 09:33:16 UTC
In addition to the slowness, ome popular providers do not (and will never) provide an index, example:

https://bintray.com/bintray/jcenter

Code completion and search is broken with these providers, errors in the code are shown where there are no errors before build has run.

Maybe make it P2? (Prevents users from completing work without significant or inefficient legwork)

mkleint mentioned there's already an abstract search API with index search as only implementation.
Comment 2 emi 2016-08-23 07:39:35 UTC
While I would want this to be part of the official distro, the new API hooks Tomas added allow my plugin to search Maven central online and avoid the index download.

See https://bitbucket.org/emilianbold/maven.search.remote/downloads

So I'm not closing this yet (since I want this to be an option in NetBeans proper) but it's much less of a pain in NetBeans 8.2
Comment 3 _ gtzabari 2016-08-23 15:04:52 UTC
max,

How will online search help with bintray?

emi,

The link you provided isn't a well-package plugin, so I agree there is still a strong need for this to go into Netbeans proper. Perhaps you could file your code as pull request?
Comment 4 emi 2016-08-23 15:28:10 UTC
@_ gtzabari: what kind of problems did you run into with the plugin?