Community
Participate
Working Groups
Build ID: I20080617-2000 Steps To Reproduce: 1. File->New->Java Project. 2. In the first panel, in the frame entitled "Contents", the option "Create project from existing source" should be renamed to "Create project files in specific directory." More information: I am suggesting this change because the new text more closely matches the function of this item: the project files are put in the selected directory, and code can be linked in from any location regardless of where the project files are. You are not actually bound to put the source in the same directory as the project files.
>Create project files in specific directory." This is one part of it but it also creates a project. I don't like it too much. Maybe we could change it to "Create project FOR existing source" This would better indicate that the source is left where it is. Markus, what's you take on this?
The main intention of the second option is not only to create project files, but to detect existing project files and/or existing source files and to set up the build path accordingly. Linking in source folders is an advanced operation that can be done on the second page (for both workspace and external projects). "Create project files in specific directory" would make the main intention less clear.
Ah, perhaps this shows my inexperience with Eclipse :-). Maybe an explanation of my motivations might show why I suggested this. I was setting up a project in Eclipse to be used by multiple developers via source control--a pretty big first step for someone who's never used the Eclipse before. Due to our source tree's organization, I had to separate the .project and .classpath files from the main source tree itself. The only way that I found to do that was to start the project with the "Create project from existing source" option and then specify where I wanted the project files to go before linking in the source. It was never apparent to me that the "Create project from existing source" option actually builds a project from the source it finds on disk. If you two think that this is a more advanced usage, then I'm fine with keeping the original text. It's just that I found the real power of this option to be the fact that it let's you specify where the project files go regardless of where the source is.
Markus and I discussed this again: actually the source is parsed and used for setup in both cases and this is also shown by the info at the bottom of the wizard. A nice solution is to replace the 'Contents' group with location selection from the simple project wizard (see attached picture).
Created attachment 133343 [details] Picture of location section
Created attachment 150205 [details] patch Changed the project location selector UI as per the discussion.
The patch does not exactly what I expect: I would expect that the initial section of the wizard looks exactly like the one for a simple project i.e. same labels, mnemonics (if possible without conflicts) and no extra group. Trivial: - update copyright when touching a file (NewWizardMessages.java and ref-wizard- java-project.htm) HINT: ask Raksha for the copyright update save action plug-in which will automatically update the copyright for *.java files on save.
Deepak, please check whether you could easily use org.eclipse.ui.internal.ide.dialogs.ProjectContentsLocationArea. If so, we might want to make that class API.
Created attachment 150334 [details] reworked patch Made the initial section of the new Java project wizard looks exactly like the one for a simple project. Using org.eclipse.ui.internal.ide.dialogs.ProjectContentsLocationArea was leading to a lot of changes, hence I have not used that.
Patch is good. Committed to HEAD. Available in builds > N20091022-2000.
Verified for 3.6 M3 using I20091026-1800.
