Reporting Errors

This first pre-release of TMBrowse should be treated as alpha quality software. It has not yet been given a thorough testing and there could be some nasty bugs lurking within...beware! However, if you do find a bug or if you find something you think is a bug, you can help us by reporting it. There are two ways to report bugs, and the preferred way is that you do both!

The first way to report a bug is to send an email to the tm4j-users mailing list. This is currently a relatively low-traffic list (typically a few messages a week), and is the best forum for asking questions about TMBrowse and other TM4J project releases. To subscribe to the list, please visit https://lists.sourceforge.net/mailman/listinfo/tm4j-users.

The second way to report a bug is to file a bug report on the TM4J SourceForge bug-tracker. This is a good way to ensure that your bug gets fixed (eventually). You can enter bugs without being logged in to SourceForge, but if you do have a SourceForge account, logging in before you enter the bug means that we can contact you if we have any progress to report or further questions to ask. You can find the bug tracker at https://sourceforge.net/tracker/?group_id=27895&atid=391879. Please use the Category "TMBrowse" for your bug reports.

Which ever method you use, there are certain pieces of information which will make it much easier for us to get to the bottom of any problem that you do have. Please ensure that your bug reports include at least the following:

  1. The servlet container you are using (include the version number of the servlet container and of the JDK that you are using too).
  2. Your config.xml settings
  3. Any error messages appearing on the console of your servlet container.
  4. The relevant parts of any log files generated by your servlet container.

If you are not sure that what you are seeing is a bug, ask a question on the mailing list, we'll do our best to help!