This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
tested on NB41. RC1 build with installed Eclipse Importer 1.1.15 ------ Created new workspace in eclipse3.1m6 with basic project in it and opened it in importer as eclipse workspace, pressed next push button and message: the workspace in directory "E:\eclipse3.1m6\workspace\" is invalid. Old workspaces from eclipse3.1m5 works fine.
Reproduced under linux as well.
Fixed in trunk. There is a new element in a .classpath file (hope that only one). Pavle could you verify it - it'll go into release41. Checking in src/org/netbeans/modules/projectimport/eclipse/wizard/ProjectSelectionPanel.java; new revision: 1.20; previous revision: 1.19 Checking in src/org/netbeans/modules/projectimport/eclipse/ClassPathParser.java; new revision: 1.4; previous revision: 1.3 Checking in manifest.mf; new revision: 1.27; previous revision: 1.26
Verified with importer 1.1.16 I'm gonna check importing projects from eclipse 3.1m6 more deeply though.
Just adding myself to CC:
Fixed in release41 as well. Checking in manifest.mf; new revision: 1.26.4.1; previous revision: 1.26 Checking in src/org/netbeans/modules/projectimport/eclipse/ClassPathParser.java; new revision: 1.3.14.1; previous revision: 1.3 Checking in src/org/netbeans/modules/projectimport/eclipse/wizard/ProjectImporterWizard.java; new revision: 1.11.6.1; previous revision: 1.11 Checking in src/org/netbeans/modules/projectimport/eclipse/wizard/ProjectSelectionPanel.java; new revision: 1.19.2.1; previous revision: 1.19
I am seeing the exact same symptom. Using Eclipse 3.1.0 (with all updates). With both Netbeans 4.1 (with all updates) and 5.0 (9/15 daily pre-release build) tried to use the Eclipse project importer. The "Workspace Location" dialog objects to other directories, and accepts "c:\workspace" (all quite proper). The "Projects to Import" dialog presents an empty list (there are in fact 10 Eclipse projects in the directory), along with the complaint: "The workspace in a "C:\workspace\" directory is invalid." I do not know if this should be the same issue continued, or opened as a new issue - given that the symptom appears identical.
Strange. Please be sure that you are not trying to import project from "First-time started Eclipse IDE" - you need to exit/restart it. Since it seems that the Eclipse will create some important metadata when you exit the ide. After you start it second time you don't need to exit it anymore. If this is not your case please run the NetBeans IDE with the parameter: -J-Dprojectimport.logging.level=FINEST This will turn on some logging information. Then attach the output log as an attachment here. This could help a lot. Thanks.
> I do not know if this should be the same issue continued, or opened as a new > issue - given that the symptom appears identical. Probably better to file a new issue. Since this one was really fixed ;)
Created attachment 24960 [details] Log file as requested on 9/19/2005
Started netbeans 4.1 with the options "-J-Dprojectimport.logging.level=FINEST" as requested, saw the same symptoms, and the log file is attached. Tried and succeeded in importing the Eclipse project in question on another computer. The workspaces on the two machines differ, so the issue is apparently with one of the other projects.
Oh yes - this is months of daily activity past the "First-time started Eclipse IDE", so the metadata (quite a lot of it - on inspection) is there.
Thanks for the log. There is a new element I didn't count with it. I'll consider rewriting of some parts of code. Thanks for the cooperation.
Sorry for late response, I was quite busy with works on other parts of IDE. Seems to me that you chose to not use default system libraries for your project's JDK which is... quite OK :) But Eclipse Importer didn't take this into account. Either I will enhance importer to take this into account or at least fix it to pass and ignore additional external jars added to the used JDK (in that case I would file another issue and CC you). I'm not sure how hard it will be to impolement know.
CCing pbannister who reported the last problem I'm going to solve. See my previous comment. You must CC yourself if you want to be informed about progress. Or remove if not ;)
Fixed. Import now passes and prints out an INFO that this is currently unsupported with link to the issue 70733 - issue for supporting additional jars on the classpath. CC yourself there if you want to be informed. Also verifying is appreciated (as soon as new version of Eclipse Importer is on AutoUpdate center - version 1.23). Checking in test/unit/projectimport/eclipse/PreferredVMParserTest.java; initial revision: 1.1 Checking in projectimport/eclipse/PreferredVMParser.java; new revision: 1.4; previous revision: 1.3
Backported for 5.0 autoupdate, should appear there in a day or so.
verified in NB 5.0