Community
Participate
Working Groups
Build ID: 3.2 Steps To Reproduce: 1. Invoke "Import Existing Project" 2. Select "Root directory" option 3. Type in UNC name (such as \\servername\sharename") an press Browse to see projects in that location. 4. Select a project and click Finish (does not matter if you copy files into your workspace, I did not). More information: The results in your workspace after import will be different depending on what 'sharename' is pointing to. 1) If it points to a project folder within workspace, you will get proper project imported; 2) If it points to a project folder which was copied out of workspace, it will result in imported EMPTY project (this is what our customers need to do), but 3) If you map network drive to the same share with project outside workspace (from #2 above), you will get a proper project with all its contents imported.
Alex I can't replicate this. When you are talking about "copied out of the workspace" do you mean exported out or dragged out? Either way are you trying to import projects that already have one with the same name in the workspace? If so they will be filtered out of the list.
Copied out means go to windows explorer (no Eclipse), select a folder that is a project root and copy it to C:\. Then create a brand new workspace (no project) and follow the steps to import the files from C:\<PROJECT_NAME>, only use a UNC name instead of drive/folder. I am trying to simplify our customer usercase, but this is the essence of what they are doing.
John, did we postpone full UNC path support? PW
This works in 3.5 M6. I imported from a UNC path using "Import existing project", and it worked regardless of the location of the project. I tried both with and without copying project contents and both cases work fine.
