BioJava Mailing Lists

BioJava has two main mailing lists :



In order to avoid SPAM both lists only accept postings from list members. Anybody can become a list member, so please subscribe before you post. If you send without being subscribed your mail might get stuck in the moderation loop, which can cause several weeks of delay (no fun to read through all that spam).

biojava-l general discussion list

This list is intended for general discussion, advice, questions, offers of help, announcements, expressions of appreciation, bugs found in release code and requests for features.

* To post or receive list email you need to sign up for the list.
* Post general issues to
* You can also view the archive.

biojava-dev developers list

This list is intended for more technical discussions about API design, bugs in CVS development code, performance issues and things that might not be of interest to the more casual user.

* To post or receive list email you need to sign up for the list.
* Post general issues to
* You can also view the archive.

List rules

  • Post in text format only. If you post in HTML or RTF the antispam software is likely to quarantine your email for at least a week.
  • Don’t attach files. They will also cause the spam filter to kick in. You will also cause problems to people with low bandwidth connections (some of us check this list on the road).
  • Don’t flame. Keep it constructive. Pleasingly we have never had a flame war on the list, we would like to keep it that way.
  • Job vacancies can be posted but only if relevant to the list, i.e they should be aimed at bioinformatics or genomics java programmers. If you are not sure ask one of the core team first. (Note: consider posting jobs to the job list at 1).
  • Never spam!
  • Off topic issues should be kept to a minimum. The subject line should be pre-pended with [Off Topic] or similar

Bug Reports

Bugs in released code should be reported via GitHub

All bug reports should contain:

  • BioJava version (eg 4.2.0).
  • OS (eg Linux, OSX 10.8, Windows XP, SuSE 9.2 etc).
  • A stack trace of any exception (complete if possible).
  • Example code that exposes the bug.
  • Accession number of a record that causes I/O problems (if appropriate).