Bug 198808 - [Misc] QuickFix to checkout dependant project
Summary: [Misc] QuickFix to checkout dependant project
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2007-08-03 09:16 EDT by Thorbjørn Ravn Andersen CLA
Modified: 2019-09-06 15:32 EDT (History)
1 user (show)

See Also:

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 Thorbjørn Ravn Andersen CLA 2007-08-03 09:16:58 EDT 
Build ID: Europa

Steps To Reproduce:
1.Create projects A and B and let B be in the build path for A
2.Check both in CVS at the same location
3.Remove projects A and B from workspace
4.Check out A but not B.  Message "Project 'timejob-jetty-6.1.1' is missing required Java project: 'axsToolbox'" appears in problem pane.
5. Select QuickFix on this problem line.
6. "Check out B from same location as A" should be a suggested fix, which will just check out B as if "Check out" had been selected from CVS view.


More information:
Comment 1 Michael Valenta CLA 2007-08-08 09:07:10 EDT 
That certainly would be the ultimate in usability. Unfortunately, it would be very difficult to pull off. First of all, CVS would need the ability to contribute a QuickFix to a particular type of Java problem. I don't know if that is possible but, even if it is, CVS would then need to know where to get the missing project.
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:32:35 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.