Evaluate Changelogic without registration!
  

Diagnosing Problems with Changelogic


If you use Changelogic version 1.x, please follow the link: Diagnosing Problems with Changelogic V-1.x


This is the guide that our support usually follows when diagnosing a problem.


Problems with build script

Problem is related to CVS

  • Are there any unresolved conflicts? Conflicts are indicated by C followed by a space and name of the conflicting file or warning “file example.java had a conflict and has not been modified”.
  • Conflicts in files that haven't been touched? Probaby CVS/Entries files out of sync. See FAQ.
  • What version of CVS client are you using? Check if it isn't CVSNT (cvs -v). Valid versions of CVS are 1.11.x.
  • Is the problem related to CVS authentication (PAM authenticate error)? Check if CVSROOT-s in environment variable CVSROOT, CVS/Entries files and changelogic-personal.properties CVSROOTs do match. It is advisable to NOT specify cl.vcs.rooturl for CVS in changelogic-personal.properties.
  • Does CVSCheck report the problem?
    • Entries files are out of sync. Check if it can be fixed with cvs update. See FAQ.
  • Is it a new project? Check if branch “latest” and first version tag are available. Check if first version tag matches the one set on project's detail form. See Installation.
  • Is the problem in partial checkout or CVS says "*PANIC* administration files missing"? Make sure there is no file or directory named “CVS” or “cvs” one level up from working directory.
  • Are the “CVS” metafile directories missing in your checkout? Make sure you did not use Eclipse CVS client to manage your working copy, it is not compatible with the command line client.

If your problem is not listed here, try looking it up from original CVS FAQ.


Problem is related to anything else in build script

  • Cannot connect to server? Check if cl.rooturl in changelogic-personal.properties is correct. See the next bullet about HTTPS. Does the server in rooturl ping? Is telnet connection to port 80 accepted?
  • Are you using SSL/HTTPS? Read FAQ. Check if the certificate you are trying to validate against is signed with the same CA certificate you registered in your keystore.
  • Is the problem related to Changelogic authentication? Check if your authentication code is from the same project and you are in correct working directory.
  • What version of Ant are you using? Valid versions begin with 1.6.x. Check if Ant is not locally compiled (although it shouldn't, it still turned out to be problem at least once). Check if there could be two different installations of Ant. Check ANT_HOME environment variable.
  • Check if there could be two different installations of Ant. Check ANT_HOME environment variable.
  • If you just downloaded code from VCS, your changelogic-build.xml could be older than the JAR files intended for its use. If the client seems to blunder before or during upgrading itself, try downloading changelogic-build.xml from manually: name menu -> Supporting files -> changelogic-build,xml
  • Is the problem related to version upgrade of Changelogic? Try ant changelogic_upgrade once more. Check changelog for more information.
  • Ant says: «Target `xxx' does not exist in this project». Check what targets are specified to be executed in changelogic-project.properties file and if they exist in build.xml file. Check ant -projecthelp.
  • Problem regarding a path (cl.fs.integrationDir) on Windows? Check that either forward slashes or double backslahes are used in path names in files changelogic-project.properties and changelogic-personal.properties.

Problem is related to build script environment installation

  • Cannot run Ant? Check if there are no spaces in PATH-s. Check if ANT_HOME does not end with slash (\ or /).
  • Cannot run keytool? Check if you are using JDK not JRE.
  • Cannot run Java? Check if JAVA_HOME/bin is in PATH.

Problems with web interface


Please describe the problem to Changelogic support, the more context you provide, the faster we can solve the problem.