Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "FAQ How do I report a bug in Eclipse?"

m
Line 1: Line 1:
To manage and track Eclipse bugs and feature requests, the
+
To manage and track Eclipse bugs and feature requests, the Eclipse Project uses Bugzilla. The main entry point to the Eclipse Bugzilla can be found at https://bugs.eclipse.org.
Eclipse Project uses Bugzilla. The main entry point to the Eclipse
+
Bugzilla can be found at https://bugs.eclipse.org.
+
  
 +
Do not be shy; post a bug if you see something wrong, even if you  are in doubt whether it really is a bug. The committers of the relevant component will quickly decide what to do with your bug report. Also do not  think, <i>Someone else will report the bug or at least the Eclipse developers themselves will see something so obvious.</i> Even  the obvious things need to be documented and reported to be fixed. Your help is crucial in continuously improving the quality and robustness of the Eclipse Platform.
  
 +
Before posting a bug, be sure to check whether it has already been posted. You can use the Eclipse Bugzilla search engine. Search instructions
 +
can be found at the Bugzilla page under the heading  '''Help With Bug Reporting'''.
  
Do not be shy; post a bug if you see something wrong, even if you
+
In short, Bugzilla is split up in &#147;products,&#148; representing  the major areas of interest in Eclipse: C Development Tools (CDT),  Eclipse Modeling Framework (EMF), JDT, and so on. To post a bug on the generic Eclipse infrastructure, choose '''Platform'''. Choose the component, such as UI, that you want to provide feedback on, and be sure to follow the  
are in doubt whether it really is a bug. The committers of the relevant
+
component will quickly decide what to do with your bug report. Also do not
+
think, <i>Someone else will report the bug or at least the
+
Eclipse developers themselves will see something so obvious.</i> Even
+
the obvious things need to be documented and reported to be fixed.
+
Your help is crucial in continuously improving the quality and robustness
+
of the Eclipse Platform.
+
  
 +
bug-writing guidelines mentioned on the bug report Web site. You will need a password to access Bugzilla. This is mainly for your own protection; the intent is to keep the spammers out.
  
 +
Writing good bug reports or feature requests is an acquired skill. A great place to learn the basic etiquette is, &#147;How to Ask  Questions the Smart Way,&#148; by Eric Raymond and Rick Moen. Note that Eric and Rick are not affiliated with Eclipse, and you should not contact them with your Eclipse questions. Their article is linked from eclipse.org and can be found easily on the Web using your favorite search engine.
  
 
+
Keep in mind that the Eclipse committers are few, and the community is large.  Bugzilla tracks thousands of defects and requests, and the committers have limited time to investigate vague, poorly described, or inaccurate reports.  Always include the Eclipse build number in your bug report, which can be found in the '''Help &gt; About''' dialog.
Before posting a bug, be sure to check whether it has already been posted.
+
You can use the Eclipse Bugzilla search engine. Search instructions
+
can be found at the Bugzilla page under the heading
+
'''Help With Bug Reporting'''.
+
 
+
 
+
 
+
In short, Bugzilla is split up in &#147;products,&#148; representing
+
the major areas of interest in Eclipse: C Development Tools (CDT),
+
Eclipse Modeling Framework (EMF), JDT,
+
and so on. To post a bug on the generic Eclipse infrastructure, choose '''Platform'''.
+
Choose the component, such as UI, that you want to provide feedback on,
+
and be sure to follow the
+
 
+
bug-writing guidelines mentioned on the bug report Web site.
+
You will need a password to access Bugzilla. This is mainly for
+
your own protection; the intent is to keep the spammers out.
+
 
+
 
+
 
+
Writing good bug reports or feature requests is an acquired skill.
+
A great place to learn the basic etiquette is, &#147;How to Ask
+
Questions the Smart Way,&#148; by Eric Raymond and Rick
+
Moen. Note that Eric and Rick are not affiliated with Eclipse, and
+
you should not contact them with your Eclipse questions.
+
Their article is linked from eclipse.org and can be found easily
+
on the Web using your favorite search engine.
+
 
+
 
+
 
+
Keep in mind that the Eclipse committers are few, and the community is
+
large.  Bugzilla tracks thousands of defects and requests,
+
and the committers have limited time to investigate
+
vague, poorly described, or inaccurate reports.  Always include
+
the Eclipse build number in your bug report, which can be found
+
in the '''Help &gt; About''' dialog.
+
 
+
 
+
  
 
== See Also: ==
 
== See Also: ==
 +
*[[FAQ How can I search the existing list of bugs in Eclipse?]]
 +
*[[FAQ What do I do if my feature request is ignored?]]
 +
*Eric S. Raymond and Rick Moen, "How to Ask Questions the Smart Way" (http://www.catb.org/~esr/faqs)
  
 
+
{{Template:FAQ_Tagline}}
[[FAQ_How_can_I_search_the_existing_list_of_bugs_in_Eclipse%3F]]
+
 
+
 
+
[[FAQ_What_do_I_do_if_my_feature_request_is_ignored%3F]]
+
 
+
 
+
Eric S. Raymond and Rick Moen, &#147;How to Ask Questions the Smart
+
Way&#148; (http://www.catb.org/~esr/faqs)
+
 
+
<hr><font size=-2>This FAQ was originally published in [http://www.eclipsefaq.org Official Eclipse 3.0 FAQs]. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the [http://www.eclipse.org/legal/epl-v10.html Eclipse Public License v1.0].</font>
+

Revision as of 16:03, 17 June 2006

To manage and track Eclipse bugs and feature requests, the Eclipse Project uses Bugzilla. The main entry point to the Eclipse Bugzilla can be found at https://bugs.eclipse.org.

Do not be shy; post a bug if you see something wrong, even if you are in doubt whether it really is a bug. The committers of the relevant component will quickly decide what to do with your bug report. Also do not think, Someone else will report the bug or at least the Eclipse developers themselves will see something so obvious. Even the obvious things need to be documented and reported to be fixed. Your help is crucial in continuously improving the quality and robustness of the Eclipse Platform.

Before posting a bug, be sure to check whether it has already been posted. You can use the Eclipse Bugzilla search engine. Search instructions can be found at the Bugzilla page under the heading Help With Bug Reporting.

In short, Bugzilla is split up in &#147;products,&#148; representing the major areas of interest in Eclipse: C Development Tools (CDT), Eclipse Modeling Framework (EMF), JDT, and so on. To post a bug on the generic Eclipse infrastructure, choose Platform. Choose the component, such as UI, that you want to provide feedback on, and be sure to follow the

bug-writing guidelines mentioned on the bug report Web site. You will need a password to access Bugzilla. This is mainly for your own protection; the intent is to keep the spammers out.

Writing good bug reports or feature requests is an acquired skill. A great place to learn the basic etiquette is, &#147;How to Ask Questions the Smart Way,&#148; by Eric Raymond and Rick Moen. Note that Eric and Rick are not affiliated with Eclipse, and you should not contact them with your Eclipse questions. Their article is linked from eclipse.org and can be found easily on the Web using your favorite search engine.

Keep in mind that the Eclipse committers are few, and the community is large. Bugzilla tracks thousands of defects and requests, and the committers have limited time to investigate vague, poorly described, or inaccurate reports. Always include the Eclipse build number in your bug report, which can be found in the Help > About dialog.

See Also:


This FAQ was originally published in Official Eclipse 3.0 FAQs. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the Eclipse Public License v1.0.

Copyright © Eclipse Foundation, Inc. All Rights Reserved.