Bug 207863 - Import Project from CVS should scan for Java source directories
Summary: Import Project from CVS should scan for Java source directories
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.3.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-29 17:42 EDT by Mike C CLA
Modified: 2019-09-06 16:15 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike C CLA 2007-10-29 17:42:43 EDT
You should be able to go:

File -> Import From -> CVS
Select a CVS project, it is imported to the local machine.
Then Eclipse JDT should scan the project and identify what directories contain source files and configure the project as such. It should also automatically pick up ant/maven/etc... files.

At the moment, when I import from CVS, I get no 'Java' tabs in the Project Properties window, and apparently no way to add the 'Java' tabs into said window.
Comment 1 Jerome Lanneluc CLA 2007-10-30 07:29:40 EDT
Is there something that can be done at the UI level ?
Comment 2 Martin Aeschlimann CLA 2007-10-30 07:54:06 EDT
JDT doesn't know CVS, and CVS doesn't know Java.

What could be done is a extension point offered by team, called when a project is imported, that allows JDT to detect and configure the new project.
Comment 3 Michael Valenta CLA 2007-10-30 08:52:57 EDT
I'm not sure that approach will scale. If there are 100 implementors of that extension, would CVS instantiate them all to see if they want to configure the project? This would lead to a lot of plug-ins being activated that the user may never actually use. However, this type of solution could be considered if there was a declarative way for JDT (and other tools) to provide a project tester (e.g. if the project contains files with the .java extension). We could use the EFS API to perform the declarative tests before any code is loaded.
Comment 4 Martin Aeschlimann CLA 2007-10-30 09:26:53 EDT
Agree that the design needs to avoid unnecessary plugin activation. Some ideas:

- Offer a UI: Import as 'Java project', 'PDE project', 'C project'... and let the user choose
- As you suggest, have declarative tests as expressions on the extensions to get good candidates


Comment 5 Eclipse Webmaster CLA 2019-09-06 16:15:34 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.