Bug 102577 - Automatically suggest classpath addition of project in workspace
Summary: Automatically suggest classpath addition of project in workspace
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-03 05:30 EDT by Alex Blewitt CLA
Modified: 2005-07-20 19:20 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Blewitt CLA 2005-07-03 05:30:43 EDT
If I have 2 projects in my workspace, and one depends on another (but I haven't set it up that way yet), 
it should be possible to prompt to add that project the current one's classpath. For example:

Project A
package a;
class A {}

Project B
package b;
import package a;
class B { A xxx; }

then an auto-suggestion could come up with 'Add project A to project B's classpath'.  It might be 
beneficial if this auto-suggestion could be done at the project level, rather than the class level, since 
it's really an issue with the project's classpath and not necessarily with the individual files -- but I don't 
think Eclipse has an easy way to fix classpath entries outside of a Java source file. This may also be 
related to bug 102576 which deals with suggestions of classpaths during import.

This suggestion comes from interpreting a non-Eclipse viewers handle on how 'stupid' Eclipse is, just 
because he didn't know how to set the classpath:

http://www.javalobby.org/java/forums/m91837490.html