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 248971 - Move NPM/CNDJS/Bower libraries nodes under Libraries node
Summary: Move NPM/CNDJS/Bower libraries nodes under Libraries node
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: Web Project (show other bugs)
Version: 8.1
Hardware: All All
: P3 normal (vote)
Assignee: Tomas Mysik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-28 09:34 UTC by Vladimir Riha
Modified: 2015-05-25 11:15 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Riha 2014-11-28 09:34:57 UTC 
If you have NPM/CNDJS/Bower libraries in JavaWeb project, their "libraries nodes" are displayed directly under project node. The "problem" is that there is already general Libraries node for Java libraries with 2 subnodes, JDK and GlassFish (if used). It would be probably "cleaner" to move NPM/CNDJS/Bower nodes under this general Libraries node. Thank you


Product Version: NetBeans IDE Dev (Build web-main-1606-on-20141128)
Java: 1.7.0_71; Java HotSpot(TM) Client VM 24.71-b01
Runtime: Java(TM) SE Runtime Environment 1.7.0_71-b14
System: Linux version 3.13.0-35-generic running on i386; UTF-8; en_US (nb)
Comment 1 Tomas Mysik 2014-11-28 09:40:57 UTC 
Will try to do it. Thanks.
Comment 2 Tomas Mysik 2015-05-25 10:58:09 UTC 
Unfortunately, this is kind of WONTFIX. The reason is that the Libraries node comes from java.api.common module. This API class would need to be extended but I am not sure whether it worths and whether Tomas would agree, of course :)

So, guys (Láďo + Tomáši), let me know whether I should try to do it or not.

Thanks.
Comment 3 Tomas Mysik 2015-05-25 11:09:04 UTC 
BTW Láďo, what we can easily do is to set a different node name (something instead of generic "Libraries"). Please let me know if you have any idea.

Thanks.
Comment 4 Vladimir Riha 2015-05-25 11:15:07 UTC 
Thanks, in such case I'd probably leave it as it is. Adding some "Libraries-like" node with new name would reduce the number of nodes only by 1 and I don't think it is worth it