Community
Participate
Working Groups
To easily duplicate projects, I copy the .project and .classpath files to a new directory in the workspace, change the files appropriately for the new project (e.g. modify the paths) and then import the new project. This used to work just fine for me, but today it was failing with an error "XML format error in '.classpath' file of project P: Bad format". I finally discovered two ways to fix this. One was to convert the .classpath file from UTF-8 to ASCII (which removes the BOM character from the front of the file). Then the import worked without error. The other way around it was to import the file and suffer the error message, then explicitly add the workspace default JRE library to the project using the Configure Build path dialog. I am guessing that there might be other workarounds and that merely saving the project files after making a change tricks eclipse into recognizing the .classpath file (which was completely correct, by the way). Interestingly, the .classpath file gets saved as a UTF-8 file and eclipse has no problem reading it. So I think this is only a problem on import.
Support for BOM-file has been improved. Please try again with Eclipse 3.5 and reopen if it still fails. Closing as WORKSFORME.
Verified for 3.6M1
Verified for Neon.3 Release (4.6.3) After updating project from an SVN server using "Subversive SVN" and "SVNKit".
Verified for Neon.3 Release (4.6.3) Condition: After updating project from an SVN server using "Subversive SVN" and "SVNKit". Fix used: In Project > Properties > Java Build Path Suppress JRE System Library -> Apply -> Add JRE System Library -> Apply
