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 182618 - Add ability to identify the source of a JavaBean in the Palette Manager
Summary: Add ability to identify the source of a JavaBean in the Palette Manager
Status: NEW
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-23 21:58 UTC by devon_c_miller
Modified: 2010-03-23 21:58 UTC (History)
0 users

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 devon_c_miller 2010-03-23 21:58:32 UTC
Using mercurial it is very common to have multiple repositories, several of which contain the same project. 

I would like the ability to see which project/library/jar is being used by a bean in the Swing/AWT palette.

Currently, the only way for me to know which project the bean came from, is to look in ${userdir}/config/FormDesignerPalette/<category>/<item>.palette_item and look for the "name" attribute of the "resource" tag.

I want to see which repository "owns" the bean so I know where I need to pull and build for the palette "Refresh" to pick up the changed bean.