Browse files

Added section on how to do bug reports.

  • Loading branch information...
jhunter committed Sep 12, 2000
1 parent 1201372 commit 2d4f26908a0598b31a0a62d72db3780ea7adef8f
Showing with 15 additions and 0 deletions.
  1. +15 −0 core/README.txt
@@ -30,6 +30,7 @@ or on Unix:
That's it!
Building instructions
@@ -82,3 +83,17 @@ samples
To learn the details of what each target does, read the build.xml file. It is
quite understandable.
+Bug Reports
+Bug reports go to the jdom-interest list at But *BEFORE YOU POST*
+make sure you've tested against the LATEST code available from CVS (or the
+daily snapshot). Odds are good your bug has already been fixed. If it hasn't
+been fixed in the latest version, then when posting *BE SURE TO SAY* which
+code version you tested against. For example, "CVS from October 3rd". Also
+be sure to include enough information to reproduce the bug and full exception
+stack traces. You might also want to read the FAQ at to find
+out if your problem is not really a bug and just a common misunderstanding
+about how XML or JDOM works.

0 comments on commit 2d4f269

Please sign in to comment.