Bugzilla – Full Text Bug Listing
| Summary: | [Import/Export] import existing projects cannot find projects in child directories using 1.5 VM | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | fred carter <fred.carter> |
| Component: | IDE | Assignee: | Platform UI Triaged <platform-ui-triaged> |
| Status: | RESOLVED INVALID | QA Contact: | Prakash Rangaraj <prakash> |
| Severity: | normal | ||
| Priority: | P5 | CC: | eclipse |
| Version: | 3.2 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
fred carter
Note: Problem only happens when using JDK 1.5.0_07. Starting from jdk 1.4.2_08, things work as expected. Fred which 1.5 VM are you using? Which revision? Using Sun JDK 1.5.0_07: java -version output:
java version "1.5.0_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode, sharing)
Also, for reference, an example .project file is:
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>agentClient</name>
<comment>agentClient project in the main branch (generated)</comment>
<projects>
<project>soa</project>
<project>wsutility</project>
<project>utility</project>
<project>csharp</project>
<project>nunit</project>
<project>containerClient</project>
<project>cdo</project>
<project>xmlaccess</project>
<project>intermediaryClient</project>
<project>policyManagerClient</project>
</projects>
<buildSpec>
<buildCommand>
<name>org.eclipse.jdt.core.javabuilder</name>
<arguments>jar</arguments>
</buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.jdt.core.javanature</nature>
</natures>
</projectDescription>
and a .classpath is
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" path="src">
</classpathentry>
<classpathentry kind="src" path="gensrc">
</classpathentry>
<classpathentry kind="src" path="tests">
</classpathentry>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER">
</classpathentry>
<classpathentry kind="output" path="classes">
</classpathentry>
<classpathentry kind="con" path="org.eclipse.jdt.USER_LIBRARY/BuildlibInteg">
</classpathentry>
<classpathentry kind="con" path="org.eclipse.jdt.USER_LIBRARY/BuildlibLocal">
</classpathentry>
</classpath>
I use Sun's 1.5.0_04 VM and don't have any problems locating projects in workspace directories. Do you have several different workspaces or just one workspace in your c:\dev\main directory. I have a setup where I have c:\workspaces and a bunch of workspace directories beneath that directory. Using 3.2 RC7, and my 1.5 VM, the wizard finds projects if i select the c:\workspaces directory or if I select one of the workspace directories in c:\workspaces (e.g. c:\workspaces\workspace1, which has a bunch of projects in it). (In reply to comment #4) > ... The c:\dev\main contains a bunch of directories (about 120), most of which contains a .project & .classpath. The workspace itself is elsewhere (in the sense that the eclipse workspace is elsewhere and the source is not imported). I am still having troble replicating the problem. The directory with the projects is not a workspace (i.e. there is no metadata), correct? How did the projects get to the c:\dev\main directory in the file system - perhaps by exporting them to teh file system from a workspace? (In reply to comment #6) > ... .project & .classpath files are generated. So they could be faulty. However, since they work individually, I'm assuming not. Big project, periodically have to work on different code paths. So I have anttask extensions that generate .{project,classpath} files when needed. start eclipse, create new workspace, import all, and tell it to build. Works reasonably well in with JVM 1.4.2_08, not with 1.5.0_07. Just tried switching VM to 1.5 in existing workspace. That generates startup error: "Path for project must have only one segment" Oh, you are generating your own .project and .classpath files. Can you attach them to this bug? (In reply to comment #8) > Oh, you are generating your own .project and .classpath files. Can you attach > them to this bug? > see comment #3 I now have Sun JDK 1.5.0_07 and tried to replicate the problem using the .project and .classpath files provided and could not. Are there any stack traces in the log file after you get the error message "Path for project must have only one segment"? I have the same problem: I cannot import existing projects. The import existing projects wizard does not list any project :-(. I'm using 1.5.0_06... Ah -- I know the reason why I could not import some projects: I had already projects with the same name in my workspace. They were closed and I used to hide closed projects... Had nothing to do with the java vm! If you have projects nested in the file system, this could be a dup of bug 144610. Wassim - one more import/export bug for you. :) (In reply to comment #12) > Ah -- I know the reason why I could not import some projects: I had already > projects with the same name in my workspace. They were closed and I used to > hide closed projects... > > Had nothing to do with the java vm! > Following this closing this bug. Also from 3.5 if your workspace already has the projects (closed/opened) the Import Wizard will show you a nice warning :-) |