1 last changed: $Date: 2002/12/08 06:04:49 $. 2002 mir-coders
2 --------------------------------------------------------------------------
6 Please read this file before sending in a bug report or patch.
10 Send comments, bug reports, patches, etc. to mir-coders@lists.indymedia.org
12 please also take the time to enter a bug in our bug-tracking system:
14 https://prod.indymedia.nl/mantis
18 Please specify the relevant versions of the software that you are running Mir
19 under. i.e JVM name and version (IBM, Sun,..), what compiler was used
20 (javac or jikes), tomcat version.
22 Of course, you should always specify what version of Mir you are running. If you
23 are running a version check'out of CVS, please specify when you checked it out
24 and from which branch (e.g MIR_1_0, HEAD..). Also if you can specify the
25 versions of relevant files using "cvs status".
27 If you received an Exception while running Mir, please mail in the "Oops" you
28 got (if you got one) and try to find and error in one of the Mir/log/* files.
29 Also, a stack trace can usually be found in one of the tomcat log files. For
30 example, in tomcat4 you can look at the .../logs/catalina.out file or the
31 .../logs/localhost_log.yyyy-mm-dd.txt, where the date is of the last time
32 tomcat was started. Under the Debian package installation, the tomcat logs can
33 be found under /var/log/tomcat... It is probably similar for other
34 distributions. If you are using the tarball from jakarta.apache.org, the logs
35 dir. is directly in the root of the tomcat tree.
40 Please send in patches that are a diff between an unmodified tree and your tree
43 diff -Nur standard-mir-dir your-mir-dir