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 206786 - Standard library volumes and/or definer based on Maven artifacts
Summary: Standard library volumes and/or definer based on Maven artifacts
Status: RESOLVED WONTFIX
Alias: None
Product: projects
Classification: Unclassified
Component: Libraries (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: Tomas Zezula
URL:
Keywords: API
Depends on: 194744
Blocks: 134677 200107
  Show dependency tree
 
Reported: 2011-12-29 14:57 UTC by Jesse Glick
Modified: 2016-07-07 08:39 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2011-12-29 14:57:01 UTC
Bug #206752 comment #6 notes that many library definitions in the IDE (for use from Ant projects) merely bundle standard open-source libraries which would not otherwise need to be in the installation. It would be nice to be able to define a library which just refers to Maven artifact coordinates, having those artifacts be downloaded (to the repository) if and when the library is ever used, with sources and javadoc attached as well.

In other cases like bug #200107 comment #2, we would rather not register the library by default, but let it be defined in the above manner if and when a project with a broken reference to it is opened. The current technique of downloading an NBM with the library from AU is quite clumsy. We could in fact consider using this system for JUnit.

It would also be great if Library Manager permitted a library based on Maven artifacts in this way to be customized naturally - by editing the coordinates rather than using a file chooser. This would make it easier to upgrade the version of a library.

Of course the 'maven-pom' volume of any such library should be defined, so that if some module does attempt to add it as a dependency to a Maven project using ProjectClassPathModifier, it will be interpreted correctly.

MavenIndexingOnePager has some old but still largely valid ideas.
Comment 1 Tomas Zezula 2012-01-02 08:29:16 UTC
Makes sense.
As far as I remember P. Zajac implemented similar feature for NB 4.x.
Comment 2 Martin Balin 2016-07-07 08:39:08 UTC
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss