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 27481 - Check and update Java Hierarchy
Summary: Check and update Java Hierarchy
Status: CLOSED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: All All
: P1 blocker (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on: 26754 27642
Blocks: 27637 28450
  Show dependency tree
 
Reported: 2002-09-20 15:13 UTC by Svata Dedic
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: TASK
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Svata Dedic 2002-09-20 15:13:49 UTC
Java Hierarchy implementation should work well
with the project environment. Check its usage of
FileSystems and convert it to use ClassPath API
and project settings.
Comment 1 Tomas Hurka 2002-11-11 13:45:35 UTC
Done in prj40_prototype branch. 
This work triggered huge changes in Java module.

Overview of important changes
1) There are two new methods
org.openide.src.ClassElement.forName(
	org.netbeans.api.java.project.JavaProject project, 
              String name)
and
org.openide.src.ClassElement.forName(
	org.netbeans.api.java.project.JavaProject  project, 
	Class name)
These two new methods replace ClassElement.forName(String name) and
ClassElement.forName(Class clazz). The old forName() methods without
project
context are deprecated and should not be used.
2) All project-specific code were removed from JavaDataObject
including all
project-specific cookies. This functionality was moved to new class
JavaMember. Cookies previously available in JavaDataObject are now
part of
ProjectMember environment.
3) Java module now uses Looks (thanks to Tomas Zezula) instead of
Nodes. 
It means that everything, which uses JavaNode and Nodes from 
org.openide.src.nodes package will not work and needs to be rewritten 
to use Looks. Node factories also will not work.
4) Parts of Java module was rewritten to use new projects
infrastructure.
  This includes parser, code synchronization, import management tool,
JavaEditor, override methods

Things that still do not work:
1) Due to nonexistent Java platform you need to manually add rt.jar to
classpath. Otherwise parser is not able to parse any source file.
2) New from template wizard does not work
3) copy, move Java file does not have project context and therefore
does not
update package statement in affected file
4) some property sheets, customizers and actions are missing in new
Looks
implementation of Java elements.
5) Due to missing project context, package rename does not update
package
statements in Java sources
6) Class and interface synchronization still uses FileObject
attributes to
store its settings
7) Up-to-date badge does not work.
Comment 2 Jan Becicka 2003-11-25 14:04:37 UTC
As described in
http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss the
current work on projects prototype has been stopped.

Marking issue as VERIFIED --->
Comment 3 Jan Becicka 2003-11-25 14:13:45 UTC
---> CLOSED