Missing project in Java build path – project settings

Import two Java projects for the eclipse workspace:

> MainProject > SecondProject

Mainproject. Is required on the construction path of secondproject

Before migrating the source code of the two projects to team foundation server, mainproject is referenced in the properties of secondproject through "Java build path" – > Item label Everything is fine

Now, after importing the two projects from TFs into a clean eclipse workspace through the team Explorer everywhere plug-in, the mainproject project in the project tab and the add... Button dialog box is no longer visible

Interestingly, mainproject is also not visible. For example, in the project – > clean up... Dialog box, but it is visible in the project properties – > Project Reference dialog box

What could be the problem???

Eclipse version 3.6 2(Helios SR2),TFS 2010 SP1

Attachment: if I add < classpathentry kind = "SRC" path = "/ mainproject" / > manually to Classpath, displaying the error "project 'secondproject' is missing the required java project: 'mainproject'"

Solution

I may be completely wrong, but it sounds like eclipse may not treat the TFs project you imported as a "Java" project (eclipse also supports "normal" projects, etc.) When you view * in the package hierarchy of a project Java files, do they have a pure blue "J" in their respective icons, or are they "hollow"?

If the former is true, eclipse will treat your project as a java project, which will be completely confused. You can ignore my answer;)

If the latter is true, the project will not be configured as a "java project" This may be a real mess... But in this case, a solution may be to rename your existing project to another project (such as mainprojectold, secondprojectold), create new "mainproject" and "systemproject" projects as new "Java" projects, and then copy all source code from the old source folder to the new source folder I don't know much about team foundation server, but I think you can reconnect your new projects with TFs and republish them as Java projects

edit

The bottom line is that if the latter is true, it sounds like the project configuration XML file does not enter the TFs, and how eclipse should handle the project (normal, Java or other) TFs after the initial import I've seen this in CVs and SVN, so I think it's a fairly common problem in any version control system supported by eclipse TFs may be included in that heap

The content of this article comes from the network collection of netizens. It is used as a learning reference. The copyright belongs to the original author.
THE END
分享
二维码
< <上一篇
下一篇>>