I get the following error when trying to "update" my eclipse project :
failed due to an internal error (took 0:00.337)
Error: Problem writing resource
'/sspaceex/src/PLWL_implementations/CVS/Template'.
A resource already exists on disk
'/home/ray/workspace2/sspaceex/src/PLWL_implementations/CVS/Template'.
Error: A resource already exists on disk
'/home/ray/workspace2/sspaceex/src/PLWL_implementations/CVS/Template'.
***
Any idea why this error and how to get rid of this?
You can right-click on your project then Maven > Update Project..., then select Force Update of Snapshots/Releases checkbox then click OK. This isn't completely same as -U: When you have old metadata file that references to a version that does not exist in repositories, updating snapshots doesn't work.
You can use Maven to set up the files needed for eclipse: mvn eclipse:eclipse. This will produce the following files for each module: . classpath file.
To enable Maven nature, right click on the project and in the context menu, select Configure → Convert To Maven Project. M2E Plugin enables the Maven nature and adds pom. xml to the project. Likewise, we can use Maven → Disable Maven Nature from the project context menu to convert a Maven project to a regular project.
Error: Problem writing resource
'/sspaceex/src/PLWL_implementations/CVS/Template'.
A resource already exists on disk
'/home/ray/workspace2/sspaceex/src/PLWL_implementations/CVS/Template'
Try to close as many active process as possible to check if another application does not "block" that resource.
As Narayan suggests in the comments, if it exists, check if you can delete it manually (outside eclipse) before attempting another refresh in eclipse.
The server reported an error while performing the "
cvs update
" command:
sspaceex: cvs update: nothing known about `doxygen/htmlclasscontinuous__sets_1_1sequence__transform__coll__graph.md5'
That should mean that the resource is removed from the file system, but not removed from CVS (i.e. on CVS server, an entry exists for this resource).
That is consistent with the failed update which was unable to write in that directory.
Doh,
I had to updated project configuration. This created the folder that Eclipse didn't like. Then close the project. Then reopen it. Then update project configuration again. Do a little dance and song, and violla!
In that order.
Cheers, M
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With