I just found out how to screw (and to repair) Subclipse in five minutes.
Maybe someone of the Subclipse team might accept this as a bug and
develop a fix for it in a future release.
Screwing Subclipse HOW-TO:
- Open Package Explorer in Java Perspective
- Create Java Project
- Add several source folders in addition to the automatically created "/src"
- Put Java sources into that source folders but not in /src.
- Add project to SVN
(till here, quite usual usage of Eclipse)
- Mark one of the source folder nodes.
- CTRL-C to copy
- Mark the project node.
- CTRL-V to paste
(I thought this will ask me for the new name, but it just puts the copy
into /src)
- Open /src node
- Mark the Java source (you will see that Subclipse thinks this is under
version control, because the copy-paste also copied the .svn folder!).
- DEL to delete the source found in /src
- Eclipse complains about problems with removing the folder
- Subclipse marks the folder as to be removed from SVN
- Now you're screwed. You cannot solve this from withing Eclipse!
Solution:
- Open CMD.exe, CD into the project, RD /s /q src to remove the src
folder (which in turn will remove the .svn folder created incidentially
by copy-paste).
- Then MD src to create the empty folder again.
- In Eclipse, mark the Project node, press F5 to refresh.
- Now you're back at where you started.
Hint:
If you want to copy a source folder, you manually need to create an
empty folder in Eclipse, then copy the Java source files. Once you try
to copy a complete source folder, Eclipse also copies the .svn folders...
Have Fun
Markus
Received on Fri Oct 20 10:12:01 2006