Community
Participate
Working Groups
1. In Project Explorer View use New -> Project -> Projects from CVS 2. Enter some CVS project details to checkout a working copy of some existing (java) project with an ant build script (like freecol); choose a cvs module 3. The wizard offers you to select a "method of check out": choose "Check out as project configured using the New Project Wizard". 4. Choose a cvs branch. 5. In the New Project Wizard choose "Java/Java Project from Existing Ant Buildfile" --> The wizard now expects that the file system path to the ant build file is given -- before the checkout takes place. One has to checkout the project as a pure java project and then add an Ant builder to get what's wanted.
I see your point and I'm also find it uncomfortable to work with. A solution, I can think of, would introduce a radio button which when set to on would change the behavior of the associated Browse button. It would enable a user to browse the module he/she is checking out in order to point an ant buildifle. However, I'm really concerned with the impact it would caused to the New Project Wizard. I don't think we would like to 'pollute' the New Project Wizard with such a kludge. If you have a different idea I will be happy to hear it.
I'd rather propose to only invoke the New Project Wizard after the initial checkout is completed. This might be the least invasive change (but I have really no idea) because New Project Wizard can work like on a local project. So the New Project Wizard could be left (almost?) unchanged -- provided that the working copy is recognized as a version controlled project later. BTW, inside the New Project Wizard you can choose a CVS Project even if the wizard has already been invoked by "Import CVS Project". You can make a nice endless loop this way -- but don't have to :-)
I understand the issue, but the team has other ones to address. Patches will be acceptable.
We've been brain-storming with Szymon about possible solution of this issue. Among other we've had an idea to copy the New Project Wizard to CVS component or at least extending some of it's classes. Nevertheless we both agreed that launching the New Project Wizard after the check out would be the best solution.
The main problem is that the New Project Wizard will only work if the project doesn't exist. If you check out the project first and then run the wizard, you will not be able to configure the project you just checked out. There are a couple of ways I can think of to try and address this: 1) Come up with an API that would allow the New Project Wizards to fetch the content and then configure the project (perhaps using EFS) 2) Create a Wizard (or modify the New Project Wizard) that will configure an existing Java project to be an Ant build Java project (basically make it so that at least some New Wizards can be used on existing projects thuis allowing the solution mentioned in comment 4). IMHO, option 1 is a cleaner solution.
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.
