HomeDocumentation > Developer's guide > Apache Geronimo Development Tools Project > How to open a bug for Geronimo Eclipse Plugin

Geronimo Eclipse Plugin (GEP) issues are tracked in JIRA in the GERONIMODEVTOOLS project.
Questions about GEP can be asked on the Geronimo mailing lists.
Eclipse Platform or WTP issues should be opened under the Eclipse Bugzilla.
Other questions pertaining to Eclipse, WTP, or any Eclipse Project should be asked on the Eclipse Newsgroups.

It is always good to search Apache Geronimo mailing lists before opening a bug. You can search the archive of following Geronimo mailing list Geronimo Apache Geronimo Users Apache Geronimo Developer. If you are sure that the problem you hit is a bug go ahead and follow the steps mentioned below.

There are numerous bug fixes coming with each release of Apache Geronimo and Geronimo Eclipse Plugin (GEP). If you are using an older version of Geronimo/Geronimo Eclipse Plugin, try using the latest available versions and see if you hit the same issue.

Search the GERONIMODEVTOOLS JIRA issue tracking database to see if your bug has already been reported, or maybe even fixed. You may be able to add additional information to a previously reported bug.

Reporting a GEP bug

  1. Launch Report a GEP Bug.
  2. Once done you will have to login. You can create a account in case you do not have one. This will help you to track the progress on the bug you reported.
  3. Once done select CREATE NEW ISSUE.
  4. On the next screen select Project as Geronimo Devtools and for issue you can check out the help against he issue drop down box.
  5. On the next page Select the version in which you hit the issue. In case you are using an older version of Geronimo/Geronimo Eclipse Plugin it is suggested you use the latest version and try hitting the same issue.
  6. Select the version in which you expect the issue to be fixed.
  7. Mention the environment correctly which may include your operating system, Java version, Geronimo version, GEP version. In case this is a build failure specify your maven version as well.
  8. Give the description as a series of step towards the bug you have found.
  9. You can also attach your application, test case to recreate the issue, screenshots etc.