Bugs

• Priority 1
• New, Assigned and Reopened
• Resolved in the last week

JDT Developer Documents

• bug annotation conventions
• smoke test
• common ui message issues
• coding conventions

  Additional rules used in the JDT UI project:

  • instance variables start with an f prefix
  • non final static variables start with an fg prefix
  • we use the compact assignment form (a= b, i.e. no space on the left of equals)

• Leak Pass Scenarios

Articles and Talks

• JDT Fundamentals (Tutorial at EclipseCon 2010)
• JDT Fundamentals (Tutorial at EclipseCon 2008)
• Unleash the Power of Refactorings in your Products (Talk at EclipseCon 2007)
• Unleashing the Power of Refactoring (Article at Eclipse Corner)
• Abstract Syntax Tree (Article at Eclipse Corner)
• more Eclipse Corner articles

Plug-ins

The JDT UI component consists of the following plug-ins:

Main Plug-ins:

• org.eclipse.jdt.ui
• org.eclipse.jdt.core.manipulation
• org.eclipse.ltk.core.refactoring
• org.eclipse.ltk.ui.refactoring

JUnit integration:

• org.eclipse.jdt.junit.core
• org.eclipse.jdt.junit
• org.eclipse.jdt.junit.runtime
• org.eclipse.jdt.junit4.runtime

Tests:

• org.eclipse.ltk.core.refactoring.tests
• org.eclipse.ltk.ui.refactoring.tests
• org.eclipse.jdt.ui.tests
• org.eclipse.jdt.ui.tests.refactoring
• org.eclipse.jdt.text.tests

Documentation:

• org.eclipse.jdt.doc.user
• org.eclipse.jdt.doc.isv

Mailing List / Newsgroup

• jdt-ui-dev@eclipse.org (post, archives)
• For user questions: eclipse.tools.jdt (web interface)

Greasemonkey scripts (aka user scripts)

JDT UI developers are heavy users of bugs.eclipse.org. Since we could not stand the increasing number of UI bloopers in Bugzilla, we created the jdtbugzilla.user.js Greasemonkey script to ease our daily pain. The script always works with the latest release of Firefox, Greasemonkey, and bugs.eclipse.org.

Over time, we also added quick links and tweaks to improve our work experience. The team-specific tweaks are being configured at the top of the script.
After installing the default script, you can override some or all of these settings locally by editing the file <firefox-profile>/gm_scripts/JDT_UI_Bugzilla_Add-On/jdtbugzilla.config.js. Just copy a var xxx= ...; declaration from the script, remove the var, and change the value to suit your needs.

For comments and enhancement requests, please use bug 390332 or file a new bug. If someone from the Bugzilla team wants to talk about the UI bugs, please also file a bug or directly talk to Markus.

Here are some of the improvements in the script (see comments in the source for full details):

• clicks all the useless (edit) links
• makes the Advanced Search page usable without having to scroll (removes garbage and increases option list heights)
• fixes alternating gray/white background for enhancements in buglist.cgi (classic skin)
• removes Eclipse.org headers to save space
• adds a fixed "Bug <id>: <summary>" header on top for easy triple-click, copy, paste
  hint: the link is in the short https://bugs.eclipse.org/<id> form
• adds quick links for frequently used CCs, Assignees, Products, Components, Resolutions, Target Milestones, Git repositories, etc.
• adds bug category combos (to insert "[work area]" prefixes into summary)
• fixes various layout bugs on show_bug.cgi
• renders Assignee next to Reporter
• moves the Status fields to a useful position (between Target Milestone and Assignee in the settings block)
• fixes attachment links (click on attachment predictably opens the attachment -- separate [diff] link opens patch viewer)
• makes the security group checkboxes less likely to be clicked inadvertently (only checkbox is clickable; label is not)
• offers two links for email addresses: simple for pasting as CC / with full name to use as Git author
• adds easy-to-copy bug <id> comment <no> text
• adds more Save Changes buttons
• fixes wrapping-preview in Additional Comments field