Problems compiling, checking in, …

Strange behavior after miscellaneous tests -> Delete Cache

If you are sure that the development environment should exhibit a different behavior than it actually does, you should delete the cache:

 

Identify the cache directory in NetBeans under Help/About.

Afterwards close the project in NetBeans and exit NetBeans.

 

  • If classes are executed unexpectedly, deleting "index" is enough.
  • If subversion is not working properly, "svncache" should be deleted.
  • In all other cases the complete contents of the cache directory should be deleted.

 

NetBeans-Editor: "Duplicate class error" 

If the class name is underlined wavily and the error message "Duplicate class error" is displayed even though there is no other class in the project with the same name, then it is possible that NetBeans has not updated the cache correctly.

 

This problem may occur if only upper and lower case have been changed.

 

Workaround:

Delete the directory "index" in the cache directory (see above).

 

After restarting, NetBeans should not report the error anymore.

 

 

Problems checking out 

If you choose "Grpxx_ueb01" as the project name instead of "grpxx_ueb01" while creating a new project and establish a connection to the repository, a new directory "Grpxx_ueb01" beside the already existing "grpxx_ueb01" is created in the repository.

If you check out all the group directories under Windows, problems will arise as Windows considers these two directories identical but encounters differing contents.

 

Solution:

Check out all directories of your group using TortoiseSVN using the RepoBrowser of TortoiseSVN. Delete the empty directory "grpxx_ueb01" and then execute a commit.

 

Using NetBeans you can re-name your project now. Don’t directly change upper case to lower case to avoid further conflicts. Instead make a detour via a different name (example "Grpxx_ueb01" -> "Grpxx_ueb01a" -> "grpxx_ueb01”; every arrow stands for a “rename” AND a “commit”).

 

 

Problems committing

When you encounter irresolvable problems committing assignment 1 (with NetBeans and TortoiseSVN), you should

 

  • Close the project in NetBeans.
  • In the Windows file explorer check out the directory grpxx_ueb01 from the directory into a directory xxx with Tortoise.
  • Copy the current local files to where the recently checked out files are (and overwrite them).
  • Commit the directory xxx.
  • Delete the local directories xxx and grpxx_ueb01 and check out grpxx_ueb01 into the directory grpxx_ueb01.

Afterwards you should be able to continue working with NetBeans normally. If you continue to have problems you can close NetBeans again and delete the cache directory (see above).

 

 

Permanent problems with NetBeans SVN

Maybe the integrated SVN kit keeps causing problems? At home you should also use the JavaHL-Client.

 

For that you install a subversion client from CollabNet. If you start NetBeans afterwards, it’ll automatically detect that JavaHL is available and chooses that version. You can control NetBeans/Tools/Options/Team/Versioning/Subversion: JavaHL should be specified as "Preferred Client" and the path to the just installed libraries is now visible.