Unresolved items on a newly created sanbox
![](http://jazz.net/_images/myphoto/f6794698ad5be1b65cc4da287de4679d.jpg)
This is regarding getting source code from Eclipse RTC. After creating a new workspace and code loading into the sandbox , I am getting unresolved items as well as project out of sync also, even though the code was newly loaded to sand box.
5 answers
![](http://jazz.net/_images/myphoto/f6794698ad5be1b65cc4da287de4679d.jpg)
Check the file encoding you're using as your Eclipse preferences. Eclipse tends to use a defailt of CP1252, but often what you really want is UTF-8. To avoid this happening accidentally, I edited
eclipse.ini
so that under
-vmargs
I include
-Dfile.encoding=UTF-8
.
![](http://jazz.net/_images/myphoto/f6794698ad5be1b65cc4da287de4679d.jpg)
Another thing that can happen is where the Eclipse .project file is source controlled, but you're using a different version of Eclipse from the person that delivered the most recent .project file. In those cases, Eclipse can detect that and then "upgrade" the .project file. If that was the case, you typically just see a pending change for that file.
![](http://jazz.net/_images/myphoto/f6794698ad5be1b65cc4da287de4679d.jpg)
If you load a repository workspace to disc, you should not get pending changes to check in.
If you have stuff like auto formatter or something like that you could see these issues as well. So make sure you understand what the server SCM contains and set your workspace to a reasonable default before loading.