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 49649 - Support SPI: visual classpath customizer
Summary: Support SPI: visual classpath customizer
Status: RESOLVED DUPLICATE of bug 150357
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Projects UI (show other bugs)
Version: 4.x
Hardware: All All
: P2 blocker (vote)
Assignee: Milan Kubec
URL:
Keywords: API
Depends on:
Blocks: 41837
  Show dependency tree
 
Reported: 2004-09-28 18:05 UTC by Jesse Glick
Modified: 2008-10-20 07:38 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
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 Jesse Glick 2004-09-28 18:05:02 UTC 
Should provide GUI panel for displaying a
classpath, with reordering; add/remove using
project, jar, or library; unremovable items;
icons; tooltips; etc.
Comment 1 Jesse Glick 2004-09-29 14:54:06 UTC 
Probably not usable for web apps anyway, since they have a slightly
different GUI - note checkbox column for each CP entry...
Comment 2 Milan Kubec 2008-10-16 13:32:26 UTC 
Is this really needed?
Comment 3 Milos Kleint 2008-10-16 13:38:42 UTC 
I would close it as wontfix. What are the usecases here?
Comment 4 Jesse Glick 2008-10-17 23:20:06 UTC 
David would know best.
Comment 5 David Konecny 2008-10-19 22:29:14 UTC 
As part of issue 150357 I will take some of existing classes implementing classpath customization and put them into
friend API module (java.api.common) and make them reusable for J2EE/Web projects. In that respect this could be closed
as dupl of issue 150357.

Re. usecases - classpath is Java concept and so all of classpath related code (if possible) should be within Java
domain. It is quite a lot of code which become non-trivial and history shows that all clones in J2EE/WEB are still
identical to its J2SE ancestor (minus changes caused by bugfixing). The checkbox/editbox shown in some of Web/J2EE
classpath customizers is visual part which is project type specific but underlying data model is in principal the same
(current classpath data model is implemented as list of ClassPathSupport.Item's and in issue 150357 I enhanced it with
Properties for an additional attributes). This data model is what I think should definitely be reused - parsing
properties and project.xml and creating memory model; altering model with different types of classpath items: project,
libary (global or shared), jar (absolute or relative or variable based path; javadoc and sources jars); handling broken
references; saving changed model; etc. All this should be reusable.
Comment 6 Milan Kubec 2008-10-20 07:38:43 UTC 

*** This issue has been marked as a duplicate of 150357 ***