4

I'm getting these errors when trying to build my app in Eclipse. Things started going downhill when the compiler warned me that my .project file was missing.

Then I tried to fix the project and now am getting these errors:

Errors occurred during the build. Errors running builder 'Android Resource Manager' on project 'net.learn2develop.Layouts.LayoutsActivity'. Preference node "org.eclipse.jdt.core" has been removed. Errors running builder 'Android Pre Compiler' on project net.learn2develop.Layouts.LayoutsActivity'. Path must include project and resource name: /net.learn2develop.Layouts.LayoutsActivity Errors running builder 'Java Builder' on project 'net.learn2develop.Layouts.LayoutsActivity'. Preference node "org.eclipse.jdt.core" has been removed.

I only have a red x at the top of my project, but not for any individual files within the project.

Any advice on how to recreate my .project file or resolve these Preference node errors?

I'm new to Android/Eclipse so details would be helpful.

Thanks

Mike Mackintosh
  • 13,917
  • 6
  • 60
  • 87
Jazzmine
  • 1,837
  • 8
  • 36
  • 54
  • BTW, I did add a .jar file as an external file but the Build Path process for it seemed to go well. I don't know if this is causing the errors. Thanks – Jazzmine Aug 03 '12 at 23:35
  • 1
    I solved the problem, I think, by creating a new workspace, moving a copy of my project files into the new workspace and then importing the project. Not sure how so many files got blown away before but starting from scratch seemed to take care of it. – Jazzmine Aug 04 '12 at 00:05
  • Came across this while searching for the same issue i faced in a project of mine. Try this answer. Should help you solve your issue. http://stackoverflow.com/a/14457430 – logRish May 16 '13 at 13:16

5 Answers5

7

Works for me : File -> Properties -> Java Compiler -> Configure Workspace Settings ...

Then Restore Default, Apply and restart Eclipse.

Alain Beauvois
  • 5,896
  • 3
  • 44
  • 26
  • 1
    Felipe, it's no a recipe for all problem, but it help in many cases and it's could be the first things to do when you're are this type of message. If doesn't work, read carefully the message and try to resolve each potential issues. – Alain Beauvois Nov 22 '14 at 15:41
6

I was able to fix these very annoying errors by deleting all my projects out of the workspace and then reimporting them. Similar to Jazzmine's solution but one less step. Now waiting to see if the errors come back...

Hayes Haugen
  • 822
  • 1
  • 7
  • 7
4

I solved the problem, I think, by creating a new workspace, moving a copy of my project files into the new workspace and then importing the project. Not sure how so many files got blown away before but starting from scratch seemed to take care of it.

Jazzmine
  • 1,837
  • 8
  • 36
  • 54
0

The basic problem is that when the Restore Defaults was applied, the Preferences code correctly discovered that there were no project-specific settings remaining in the node, so it removed the node. But WorkingCopyPreferences never discovers that fact, so a timebomb is ticking from then on.

Notice that since the JDT options pages all share a WorkingCopyManager, but each page only modifies a subset of the jdt.core settings, there is no way that any single page can tell whether restoring defaults for that page's settings will or will not cause the node to be removed. So it can't, e.g., cleverly call removeNode() on the WorkingCopyManager.

Sheelpriy
  • 1,675
  • 17
  • 28
0

Delete the project from the workspace and checkout again and configure the project... Its working for me in when I checkout from the SVN.

Parthasarathy Deva
  • 61
  • 1
  • 1
  • 3