So if trying to do this inside the workspace, the tracking folder Eclipse wants to create will already exist - it would be where the user downloaded code to. I know that when importing from outside the Eclipse workspace, Eclipse itself will want to create a project folder within the workspace for project settings/tracking, which will essentially have the same project name. If trying to use this code to import in to the workspace folder newProject.create(newProjectDescription, monitor) will throw the exception .resources.ResourceException: Invalid project description. This works as long as the target folder is outside the workspace. I use the createProject function to get an IProject reference, then pass this to the importProject function. The code works for importing projects that are located outside the workspace. The downloaded source code has never been loaded in an Eclipse environment beforehand, so the download target is simply the source root folder.
The source code the user downloads is placed in the target folder BEFORE calling the code below.
The only user intervention is the user decides where the project will go on disk, and that means they can choose any folder, including one in the Eclipse workspace. Essentially the scenario is source project is downloaded to disk, then needs to be loaded in to the IDE without user intervention. I have reviewed the older questions around creating projects programmatically within Eclipse, which I need to do from a plugin.
0 kommentar(er)
