Skip to main content
Jump to: navigation, search

Mylyn/Contributor Reference

< Mylyn
Revision as of 17:53, 27 March 2012 by (Talk | contribs) (Maintenance Branches)

See also: helpwanted bugs, eclipse dev, source repository, website repository

Project Structure

The Mylyn project is structured into sub-projects that address different areas of Application Life-cycle Management. Please see Mylyn/Charter for the top-level project charter.

Artifacts are published in a number of Mylyn/Repositories. The main repository aggregates sub-projects that participate in Mylyn releases. The participating projects are listed in the project plan. The main Mylyn update site features are mature components that are supported by the Mylyn project committers and may be distributed as part of the Eclipse Downloads.

Sub-projects are encouraged to provide a framework component and reference implementations called Connectors that extend Mylyn to different task management systems and focus the artifacts that you work with when you activate a task (formerly called Bridges).

Feature Maturity

Mylyn features vary in UI maturity and availibility of support. The following is a guideline for what it takes to move from experimentation through to maturity. (Note that this is partially based on the Eclipse project lifecycle and could converge further with that lifecycle if Mylyn were split into a separate incubation project or subprojects.)

Mature: packaged Eclipse downloads and available via main update site

  • UI quality: Eclipse SDK features have set a very high quality and UI consistency bar that needs to be met in order to make it possible to improve users' productivity with Eclipse.
  • UI simplicity: the Mylyn project's goal is to simplify and streamline the user experience. A simple and self-evident UI also helps ensure a manageable support burdeon on the component.
  • Availability of support: the feature must have an owner or organization with a long-term commitment to the quality of the feature and the ability to provide responsive support for feedback on that feature.
  • Responsiveness to feedback: the feature owner and other contributors must process and prioritize user feedback and respond to the highest priority needs in a timely manner (e.g. blockers and critical bugs need to be fixed within one release of being submitted, key enhancements help the feature evolve to meet users' needs).

Incubation: available via the nightly update site

High quality components that meet most but not all of the above criteria. To graduate, sufficient community feedback must be available on the quality and usability of the component (e.g. 100+ resolved bugs) and committers must vote to determine whether component meets the UI quality and simplicity guidelines.

Sandbox: available via the Incubation update site

  • Unsupported components used for experimentation and not intended for daily use.
  • Community interest and contributions determine which experimental features move from the Sandbox into Extras.

Creating New Components

Most sub-projects host a framework component and one or more reference implementations. When new code is brought into Mylyn it may be added as a sub-project, sub-sub-project or as a component of an existing project. The right organisational structure depends on the needs of the development community and the scope and process of the existing projects. Criteria that could qualify a component to be split out as a separate project:

  • A component requires incubation status (e.g. for parallel IP) but the framework project has already matured.
  • The committer set of the component is not a subset of the committer set of the framework project.
  • A component wants to release more frequently than its framework project, i.e. it follows it's own project plan.
  • A component publishes its own APIs and its scope and community are significant that it requires its separate management structure such as a Bugzilla product, news group etc.

Getting Started

The Mylyn project places a very high value on community contributions. This document is intended to help those interested in contributing to Mylyn. It communicates our conventions and discusses ways to get your contributions prioritized.

Individual Contributors

A significant portion of Mylyn contributions have been made by individuals wanting to make the tool or framework work better for them. There are several ways that individuals can get involved with the project:

  • Mentoring: if you are an experienced user, you can support newcommers by providing feedback using the community channels
  • Casual contribution: we have a large number of very valuable casual contributors who provide patches for their pet bugs, or enhancements that either they would find valuable or that they want to share with others. If you are interested but don't know where to start look first through the short list of bugday bugs, and then through the longer helpwanted list.
    • bugday bugs: a short list of highly relevant bugs for getting started
    • helpwanted bugs: a longer list of all bugs targeted at community contributions
  • Working towards commit rights: The Eclipse and Mylyn development processes make it easy to make regular contributions without requiring commit rights, but frequent contributors may be interested in earning commit rights. Commit rights come with a significant overhead of user support as well as the need to follow the project's priorities for contributions. They require you to participate in the planning and of the project, and allow you influence the direction of the tool and framework. If you are interested in becoming a committer we recommend letting one of the existing committers know so that they can mentor you and help build a trust relationship. It can also help to identify a separable component of the project that you are interested in taking responsibility for, since Mylyn commit rights are assigned per-component.

Integrators and Vendors

Those building both closed and open source tools on top of Mylyn may be interested in evolving the Mylyn APIs to ensure that that the framework meets their needs. We welcome such contributions just as we welcome individuals making improvements to the tool, since they help make Mylyn a better framework for all. The Individual Contributor points above apply to integrators and vendors interested in contributing or earning commit rights. In addition, the following tips may be of interest:

  • If interested in exploring Mylyn integration, consider dialing into the our weekly call and adding an agenda item on the Mylyn Meetings page.
  • Vendors are welcome, so make yourself known. We recommend using your company name for Bugzilla email addresses. If you have a product built on Mylyn and need a bug fixed, we recommend voting for it with that email address. The Mylyn project prioritizes bugs according to how much overall benefit they will have to users, and as such commercial integrations are an important part of that prioritization. If the bug does not fit with the project's priorities we will encourage you to provide a patch.
  • Consider making a bug titled "support integration with <your tool>". We use these bugs for discussing integration issues particular to a specific tool or technology and leave them open for ongoing API or UI discussion needs.



The recommended way to work with Mylyn sources is by checking them out of Git. Doing this makes it easy to try the latest changes and work with patches and ensures that you can easily browse the source code and documenation using Eclipse's facilities.


Install Eclipse and get it configured for developing Java 5 applications.

  • Unless targeting a particular Eclipse release, download the latest Eclipse milestone release.
  • Associate J2SE-1.5 with your installed JRE via the Window -> Preferences -> Java -> Installed JREs -> Execution Environments. Note that to get rid of JRE association warnings you may need to download older JREs, e.g. from:
  • To install additional JRE profiles or if you are unable to obtain a J2SE 1.5 installation install Add PDE/API Tools Environment Descriptions from the Eclipse project repository that corresponds to your Eclipse environment, e.g.


The source code is hosted in Git. Each sub-project has a separate repository that is accessible through the git, ssh and https protocol. For anonymous access use git or https. Committers need to use ssh or https.

Web access to the Git repositories

Release Tags: Each release is tagged with R_. For example, Mylyn 2.2.0 for Eclipse 3.4 is tagged as R_2_2_0 and the branched Eclipse 3.3 plug-ins are tagged R_2_2_0_e_3_2.

Active branches

Also see policy for supported Eclipse versions. Branched projects, if any, are updated with each release.

Maintenance Branches

Changes should be committed to master and cherry-picked onto maintenance branches to be included in service releases.

  • e_3_8_m_3_7_x     Mylyn 3.7.x stream (corresponds to Mylyn Docs 1.6.x)

End-of-life branches

  • e_3_7_m_3_6_x     Mylyn 3.6.x stream for Eclipse 3.7
  • e_3_7_m_3_5_x     Mylyn 3.5.x stream for Eclipse 3.7
  • e_3_6_m_3_4_x     Mylyn 3.4.x stream for Eclipse 3.6
  • e_3_6_m_3_3_x     Mylyn 3.3.x stream for Eclipse 3.6
  • e_3_5_m_3_3_x     Mylyn 3.3.x stream for Eclipse 3.5
  • e_3_4_m_3_3_x     Mylyn 3.3.x stream for Eclipse 3.4
  • e_3_5_m_3_2_x     Mylyn 3.2.x stream for Eclipse 3.5
  • e_3_4_m_3_2_x     Mylyn 3.2.x stream for Eclipse 3.4
  • e_3_3_m_3_2_x     Mylyn 3.2.x stream for Eclipse 3.3
  • e_3_4_m_3_1_x     Mylyn 3.1.x stream for Eclipse 3.4
  • e_3_3_m_3_1_x     Mylyn 3.1.x stream for Eclipse 3.3
  • e_3_4_m_3_0_x     Mylyn 3.0.x stream for Eclipse 3.4
  • e_3_3_m_3_0_x     Mylyn 3.0.x stream for Eclipse 3.3
  • e_3_4_m_2_x     Mylyn 2.x stream for Eclipse 3.4
  • e_3_3_m_2_x     Mylyn 2.x stream for Eclipse 3.3
  • e_3_2_m_2_0     Mylyn 2.0 stream for Eclipse 3.2
  • e_3_3_m_1_0     Mylyn 1.0 stream for Eclipse 3.3M4
  • e_3_2_m_1_0     Mylyn 1.0 stream for Eclipse 3.2
  • e_3_1     Mylyn 0.6 for Eclipse 3.1


  • Web site     for updating PSF File
  • can be used for manual checkout

Target Environment

Mylyn depends on a number of libraries from other Eclipse projects. The org.eclipse.mylyn.releng project provides target environment definitions that specify all required dependencies. After following the steps under Checkout go to Window > Preferences and open the Target Platform page. Select one of the mylyn target definitions. Generally, mylyn-dev-base is the recommended choice.

  • mylyn-dev-base - Targets the lowest support Eclipse version. Includes sources and additional integration features for development.
  • mylyn-dev-latest - Targets the highest support Eclipse version. Includes sources and additional integration features for development.
  • mylyn-e* - Target defintions used by the build. May only contain the minimal requirements excluding sources.

API Baseline

An API baseline for the latest releases is available from the download archive. Follow these instructions to configure the API baseline in your workspace:

  1. Extract a version of Eclipse Classic (SDK) to a directory that matches the version of your current target platform
  2. Extract the Mylyn API baseline zip archive to the eclipse/plugins directory from the extraced SDK
  3. Add the baseline under Windows > Preferences > Plug-in Development > API Baselines pointing to the eclipse/plugins directory from the extracted SDK


The general policy is that plug-ins should not have any errors or warning markers since these indicate potential problems or API insufficiencies. In practice, we do not have the capacity to address all warnings or the cost outweighs the benefit or warnings result out of intentional design decisions, e.g. usage of deprecated APIs for maintaining backwards compatibility.

To reduce the number of warnings we have established the following policies for usage of internal packages:

  1. Plug-ins are allowed to use internals within the boundaries of their component (e.g. o.e.m.bugzilla.ui may access internals of o.e.m.bugzilla.core). We have generally allowed that through x-friends relationships in plug-in manifests.
  2. It's generally okay to use provisional APIs. We have made these accessible through classpath filters: Project Properties > Java Build Path > Libraries > Plug-in Dependencies > Access rules. It's common that plug-ins have a rule to make org/eclipse/mylyn/internal/provisional/** accessible.
  3. In cases where platform internals need to be accessed due to a lack of API it's okay to make the specific classes or packages accessible. These cases should be documented on bug 233055.
  4. Test plug-ins are allowed to use all internals.

Additionally, it is recommend to create custom filters in the workspace to hide remaining warnings that will not get addressed in the short time. Filter can be configured through the view menu of the Markers view.

JUnit Tests

Each component has it's own All<Component>Tests suite. If not familiar with running PDE JUnit tests, refer to the Eclipse Documentation.

Tests that connect to repositories require a $HOME/.mylyn/ file that specifies authentication information. The file needs to have the following content:

user: <user>
pass: <pass>
  • For <user> use For <pass> use mylyntest. If you have any trouble making this work email
  • Add the following to the test configuration under Arguments -> VM Arguments: -enableassertions -Xmx384M

Test suites in org.eclipse.mylyn.tests:

  • AllTests: all automatic tests, should always pass, run as a JUnit Plug-in Test
  • AllHeadlessStandaloneTests: do not require workbench, can run as JUnit Test, subset of AllTests
  • AllConnectorTests: all automatic tests for repository connectors, requires network access

Test suites in org.eclipse.mylyn.tests.ui:

  • AllUiTests: all automatic SWTbot-based UI tests

Test suites in org.eclipse.mylyn.tests.performance:

  • AllPerformanceTests: all performance tests

Manual tests

The manual tests can be found on the Mylyn Testing page.

  • Component owners are responsible for maintaining their respective manual tests and ensuring they are covered two days prior to release.

Trac Connector


Self-hosting, also known as working bootstrapped (i.e. self-hosted) makes eating your own dog food easier and avoids having to update to dev builds.

The following is an example of how to set up a bootstrap workspace, work and runtime workspace. The result is an folder with the following three workspaces:

  • Mylyn-Bootstrap
  • Mylyn-Work
  • Mylyn-Runtime

Please follow the steps:

  • Download and install Eclipse 3.7 or later
  • Start Eclipse and create an workspace called Mylyn-Bootstrap
  • Install dependencies using File > Import > Install Software Items from File: mylyn-bootstrap.p2f
  • Import projects using File > Import > Team Project Set: mylyn-dependencies.psf
  • Switch to the Git Repository Exploring Perspective and clone the Git repositories listed under Mylyn/Contributor_Reference#Checkout
  • Use Import Projects from the Git Repository Exploring Perspective to add the projects to your workspace
  • Create a new Launch Configuration:
    • SelectRun -> Run... -> create a new Eclipse Application.
    • Call the application Mylyn Work.
    • On the Main tab, set the Location
      • You can use an existing workspace
      • You can create a new workspace (e.g. Mylyn-Work)

Launching with this launch configuration will give you a second workbench with Mylyn. This workbench will be created based on the target platform (the workbench you're launching from) and the installed plugins. This workspace needs to be setup following the steps under #Setup:

Do your development in the Mylyn-Work workspace. Whenever your changes make it into master that you would like to use, close your Mylyn-Work workspace, pull from Git in the Mylyn-Bootstrap workspace, and then re-launch your Mylyn-Work workspace.


  • The launching workspace will typically consume very little memory.
  • Working in bootstrap mode means you have the source code checked out at least twice, once to bootstrap Mylyn, and once to actually develop.
  • You must have two distinct workspaces, you can't bootstrap into the same workspace as you launch from.
  • It is possible to run in debug mode so that the changes apply to the workspace immediately after synch, but this can cause problems with the running workspace if classes change or go missing. This is because the hot-swap virtual machine can only change method bodies, not class definitions.


All contributions to Mylyn need to be made using Mylyn since it links source changes to tasks and contexts, making open development and collaboration easier. Using Mylyn ensures that:

  • All Bugzilla reports have a corresponding task context, making them easy to reopen or pick up by you and by others.
  • All commits correspond to a single Bugzilla report, making it easy to navigate from changes to bugs.

Getting Started

  • Use Bugzilla for all of your communication. This helps committers track the contribution.
  • Before setting out to contribute to a bug report, post on the bug report describing your intention. This helps committers guide the contribution and avoids problems with patches going stale due to related work being done concurrently.
  • For contribution ideas see #Individual_Contributors to find an enhancement that interests you, file a new bug of your own, or email mylyn-dev for ideas.


Following these steps will help get your patches applied more quickly.

  1. Before implementing the functionality post a brief proposal of the implementation and UI changes/additions and get a committer's feedback. The committer should be either the component owner.
  2. Post a patch to the core functionality with reasonable unit test coverage (see below). Thorough unit test coverage is typically required if API methods are affected.
  3. After that's applied iterate on the UI proposal if needed and the post the patch to the UI.
  4. Note that the smaller you make patches and the more focused they are on individual and well-tested units of functionality the more quickly they will get applied.


We use votes in order to track the general interest in a particular bug. Bugs with more votes are more likely to get fixed. However, we also have numerous "[connector]" bugs that are open, but out of the scope of the project. We encourage all in the community to vote for bugs, since it helps contributors prioritize work. If you notice a vote from a committer on a bug, the likely reason is that they would like to see the fix as well, even though the current priorities may mean that it is not planned for the near future (e.g. a UI enhancement while API is being prioritized).


In order to make your patch get applied as quick as possible, we recommend the following workflow:

  1. Comment on the corresponding bug, asking whether a committer or another contributor has any suggestions for the implementation approach.
  2. Propose a design, mentioning the key use cases, implementation, tests coverage, and UI changes or additions (if applicable).
  3. After a committer iterates with you on the design, prefix the summary of the bug report with "[patch]", and wait for review.
  4. Note that the review process might involve iterating on the patch, especially if there are UI changes or additions involved.


  • Each patch should correspond to a single bug report, and a single patch should be made for each set of changes to be reviewed.
  • A task context should be attached to each patch to make applying and evolving it easier.
  • With few exceptions patches should be accompanied by a JUnit test, and in general unit tests are one of the most valuable and long-lived contributions. If you are having trouble writing a test (e.g. trickiness verifying what happens in the UI) comment on the corresponding bug report so that we can point you at similar test cases or consider extending the test harness if needed.
  • Minimize the amount of changes to existing code to make review easier.
  • Synchronize often to ensure you have the latest code. Once you start modifying resources, put the Synchronize view in Outgoing mode and press the Change Set button so that the changes are tracked per task.
  • Before creating a new JUnit test class class check the components test suite for similar test cases (e.g. AllTasklistTests).
  • Add an @author tag to each class that you create or make significant modification to, placed below any existing author tags, e.g.: @author Rob Elves
  • Ensure that there is no console output.
  • If tempted to copy code from either Mylyn or any other part of Eclipse, please first comment on the bug that you intend to do so. The need to copy code is often indicative of the need for us to provide additional modularity, and creates a maintenance burden for the project. If you do copy code, please put an @see link in the Javadoc for the method or class that has the copied code.


  • Ensure there are no build errors, warnings, and that tests pass.
  • Commit your changes to your local Git repository
  • Drag and drop the commit from the History view to the task editor. This will open the attach wizard. Alternatively you can create the patch manually:
  • On the preview page verify that:
    • Patches are rooted at the root of the Git repository
    • Patches only contain relevant changes
  • Check off the Patch and Attach Context checkboxes in this wizard page.
  • Add a description of issues addressed and comment on what testing was done to validate it (e.g. unit test coverage, manual tests performed). Also indicate any changes made to the existing UI in the comment (e.g. reordering of menu actions). Also indicate if patch is intended to resolve bug report or further work is required.

Writing Tests

Writing tests along with patches is key to ensuring that it is possible for committers to maintain the new functionality added by the patch. When writing tests look for the All<component>Tests class in the tests plug-in for that component, identify a test that is similar to the functionality that you are adding, and use that test as an example of how to add additional coverage. Tests can sometimes take longer to write then the change itself, but a committer will always be willing to assist you in designing the test or extending the mock test harness to make it easier to write.

The key things to ensure is that your test covers is the addition or change to the existing functionality. For API changes it is often sufficient to have the public method covered. When writing tests for UI components, the simplest way of testing will often involve a combination of unit and black-box testing, for example, relying on other parts of the Mylyn UI to be set up (e.g. the Task List view). Consider the case of adding functionality for pre-selecting a repository in the New Task dialog, writing a test can take the following form (refer to NewTaskWizardRepositorySelectionTest):

  • Create a mock repository
  • Add a task to the mock repository
  • Set the selection on the Task List (new functionality uses this selection)
  • Invoke the wizard and assert that the selection was set correctly on the viewer (wizard is a black box, all we care about is the contents of the viewer)
  • Dispose the wizard dialog, remove the mock repository and the mock task

When writing UI tests note that asynchrous updates, such as refresh, can make testing challenging. Note that several UI components have a method on them to set synchronous execution for the purpose of testing, and if such a method is lacking it can be added.


Mylyn uses the Eclipse code conventions. See #Links for references.


If contributing a feature with icons or other graphics feel free to ask a committer to generate the graphic for you. If interested in contributing graphics you can find all of the source files (e.g. Photoshop) here: mylyn/graphics/ui.


For larger changes consider submitting a code review through Mylyn's Gerrit instance. To use the review server a few steps are required.

Register a Gerrit Account

To use the review server a few steps are required:

Once the account has been created contact Steffen Pingel to get the account added to the trusted users group which has the required permissions to create code reviews.

Add Gerrit as a Git Remote

Gerrit is added as another remote to the local clone of a Mylyn Git repository. For example, the .git/config file for the Mylyn Tasks git repository would specify these additional remote:

[remote "gerrit"]
  url = ssh://
  fetch = +refs/heads/master:refs/remotes/gerrit/master
  push = HEAD:refs/for/master

If you are not able to connect to through SSH on port 29418 you can instead setup a password for HTTP access. In this case the url in the remote configuration needs to specify a different url:

[remote "gerrit"]
  url =
  fetch = +refs/heads/master:refs/remotes/gerrit/master
  push = HEAD:refs/for/master

Make sure you are using Git Client version 1.7.2 or later. Earlier versions might have problems connecting to the Gerrit Server.

Additionally, these settings are recommended:

  createchangeid = true
  autosetuprebase = always

Add Gerrit as a Task Repository

You can add as a task repository in the Task Repositories view and create queries to bring your code reviews into your task list.

Create a Code Review

  • Create a topic branch
git checkout -t origin/master -b bug#123-my-topic-branch
  • Commit to the branch. Ensure that a Change-Id header is included in the commit message.
  • Submit the code review
git push gerrit

Update a Code Review

  • Check out the topic branch
  • Update to the latest master
git pull
  • Commit changes
git commit -a --amend
  • Update code review
git push gerrit

Squash Commits

Gerrit creates one code review per commit. If you committed multiple times you can always squash commits later using interactive rebase, e.g. to merge the last two commits into one commit use this command:

$ git rebase -i HEAD~2

This opens an editor to modify the commit history. If you change pickin the second line of the editor to fixup that commit will be merged with the previous commit when you exit the editor.

Merging Contributions

The Git repositories on are mirrored hourly from Hence, any changes that are merged by Gerrit are automatically overridden and do not propagate back to Once bug 283749 is resolved Mylyn will switch to using infrastructure but for now approved contributions will still need to go through the standard process. That means, once a code a review is approved a patch needs to be created and attached to a bug report to track the IP in accordance with the Eclipse process.


The Eclipse Charter explains how developers can gain commit rights.


Committers should:

  • Sign up for all of the project mailing lists.
  • Read the newsgroup regularly, and respond to posts in their area of expertise.
  • Respond to mylyn-dev email in their area of expertise.
  • Watch and update all wiki pages related to components that they contribute to.


Mylyn committers are required to follow these communication guidelines. Our philosophy is that the user is always right, even if it takes time to figure out how or why they are right. Our project thrives on the feedback of users, whether they are seasoned experts or newbies. Feedback defines how the tool should work, how it should be simplified, and how it should evolve.

  • All feedback contains information, and it is the responsibility of committers to turn that information into actions. This can mean improving the implementation, simplifying the workflow, clarifying the documentation, or noting a duplicate request. Making the actions we take clear helps communicate this philosophy to our growing user community and encourages high-quality feedback.
  • If users do not provide enough information or do not take the time to provide accurate information, they should be prompted to provide the necessary details. If they do not do so in a timely manner, the feedback is incomplete and can be resolved without taking action.
  • Show respect to others in the community, whether they are making correct or incorrect assumptions about the tool or technology. When someone makes incorrect assumptions it is because we have not done our job well enough, or because the platforms we build on are making it hard for us to do our job well enough. Identifying those cases is important so that we can provide feedback to those platforms and find work-arounds.
  • Never turn feedback or discussion away by flaming, being condescending, short, or insulting in any community communication forum. Forms of humor that work for face-to-face communication, such as sarcasm, are usually best avoided because they can result in misinterpretation, especially when there is a language or cultural barrier.

Handling Inappropriate Communication

In the vast majority of cases, following the above guidelines has lead to the high quality communication that our user and contributor community has thrived on. However, the openness of our communication channels has been abused in the past. These scenarios are typically marked by overly opinionated, non-technical and insulting posts on bugs in and in other forums. The communication may have technical elements or technical points, but the points are communicated in an overly opinionated way with a disregard for the opinions of others involved in the dialog. If encountering such communication, make sure to read the Wikipedia Entry on Flaming, especially the "Causes of flaming" section.

Note that invoking the process listed below should be the exception, and not the rule. Projects with like-minded committers can experience the Groupthink bug, which is why high quality open communications channels are so important to helping the project evolve. However, abuse undoes the openness that we strive for by making the channels intimidating or unfriendly to newcommers. Follow these steps if you encounter such communication:

  • Make one or two attempts to steer the conversation back on a technical path.
  • If that doesn't address the problem, enter the following text as the third comment:
 Ignoring comment per:
  • Avoid following up again. Send the bug ID to the project lead who will assess the problem.

To comment on these guidelines please use bug 216157


  • Any user-reported bug should be resolved by one of: code improvements, documentation/FAQ improvements, or being marked a duplicate of another bug. All but the last require attaching a context.
  • Be judicious in marking bugs for LATER, because this typically communicates that the bug will never be resolved. Do this only if the bug does not fit in with the current scope of the project but is related to the mission. Otherwise mark P4/P5 and "helpwanted" to encourage a contribution that is not part of our current prioritization and plan.
  • When naming bugs, try to describe the use case or problem instead of the implementation unless there is no ambiguity in how the fix should be implemented. If the implementation approach helps with queries append it.
    • Bad: task list working set
    • Good: support nesting top level task list elements, e.g. via working sets


  • Use the Eclipse bug severity with this exception: bugs marked as Trivial are enhancements, that can be easily implemented.


  • helpwanted: bugs that are beyond the current priorities for the project. Note that some bugs marked for an upcoming milestone can be marked as helpwanted. This indicates that the project committers would like to see the bug solved for the milestone and will actively contribute to a solution, but that the bug is more likely to be fixed in a timely manner with the help of additional contributors.
  • bugday: these are a special category of helpwanted bugs that are intended to be mast accessible or rewarding for new contributors interested in helping the project to tackle. See the Bug Day FAQ for more information. In order to keep this list focused on the most relevant bugs it is capped at 24 and should be reviewed periodically.
  • contributed: bugs that were resolved through a contribution from a non-committer.
  • plan: bugs that are part of the project plan (see below).

Tags The project uses the following tags in the summary of bugs on (bug 215853):

[activity]      - bugs related to improving work flow
[api]           - bugs that require API changes; every API change has a corresponding bug which is tagged that way
[bridge]        - requests for structure bridges
[connector]     - requests for connectors
[context]       - bugs related to the context framework
[discussion]    - discussion items
[editor]        - bugs related to the Task Editor
[e3.2][e3.3]    - bugs specific to a particular version of Eclipse
[folding]       - bugs related to active folding
[framework]     - bugs that address internal implementation details that do not require API changes
[linux]         - bugs specific to Linux (Gtk)
[m2.3.1]        - bugs that are fixed in a particular maintenance version of Mylyn
[mac]           - bugs specific to Mac OS (Cocoa, Carbon)
[multi monitor] - bugs related to multi monitor environments
[new uex]       - new user experience
[patch]         - bugs that have a patch attached that is pending for review or waiting to be applied; 
                  the tag is removed after the patch has been applied or if a review requested changes
[performance]   - bugs that indicate severe performance problems
[planning]      - requests for planning features
[refactor]      - request for non-functional refactorings
[regression]    - bugs that indicate regressions
[sandbox]       - bugs that affect components in the sandbox
[standalone]    - bug related to usage of Mylyn outside of the Eclipse environment
[update]        - update manager and P2 related bugs
[usage]         - usage monitoring related bugs
[web connector] - bugs in the Web Templates connector
[website]       - bugs related to the web page on (use Doc component for that?)
[win]           - bugs specific to Windows (Win32, WPF) 
[workflow]      - requests for integration of task and repository workflow
[working sets]  - bugs related to working set support
[search]        - bugs related to desktop search (see bug 349351)


The goal of bug triage to minimize the overhead for committers and to maintain a manageable backlog. Each (new) bug that is filed is processed as follows:

  • Major bugs or regressions are marked P1. If necessary the bug is escalated and scheduled for the current milestone.
  • Other bugs are marked P2.
  • Enhancements requests that should be considered for a future release are generally marked P3.
  • Other enhancement requests are marked P4 and tagged as helpwanted if they can be resolved through a community contribution.
  • If a request is out of scope of the project it is marked P5 or preferably closed. P5 bugs should not be marked helpwanted.

The backlog consists of all tasks scheduled for -- with a priority of P2 or higher. User stories are tagged with the plan keyword.

Bugs are assigned as following:

  • New bugs are and bugs that need user input.
  • Bugs that have been responded to and severity and priority has been set.
  • other: The owner is committed to completing the task for the scheduled milestone or within a reasonable time frame in the future if the bug is scheduled for --.


The goal of planning is to schedule a list of bugs for the milestone that concludes the next release cycle. When the milestone is reached all bugs with a priority of P3 or higher are expected to be completed. It is important that planning takes existing resources into account to avoid over-committing. Predictable release deliverables will enable integrators to plan their own progress based on the Mylyn framework and aid the growth of the ecosystem.

Before every release planning is done by triaging the entire backlog. Bugs marked with the plan keyword become part of the official release plan. Planning bugs marked P1 are committed items, other bugs are proposed items. Half way through a release cycle the plan is reviewed and P1/P2 bugs in the backlog are reconsidered for the milestone to accommodate for regressions and major bugs that were submitted after initial planning.


The list of bugs that are scheduled for a milestone serves as a log that documents changes to release artifacts. In order to preserve historical information captured by the change log bugs that have been resolved should not be moved to other milestones once a milestone has been released.

If a defect reoccurs or a bug requires further work a new bug should be created and linked to the resolved bug. It is recommended to add a comment on the resolved bug that points to new bug and describes the reason for its creation.


Git repositories can be accessed in Eclipse via EGit. Mylyn uses the following conventions for Git repositories:

  • It is strongly recommended to rebase before pushing to keep the revision history flat as possible:
git pull --rebase

The branch.autosetuprebase setting automates that:

git config branch.autosetuprebase always

See also:


Mylyn is built regularly by jobs running on the Hudson server.

Heartbeat Test Jobs

Each sub-project has its own build job triggered by Git activity that runs all tests for the sub-project.

Integration Test Jobs

Integration tests run against the Git integration build repository that includes all sub-projects as submodules. Integration tests are triggered by the mylyn-release job.

mylyn-integration-e3.5       - Eclipse 3.5: All tests excluding repository tests
mylyn-integration-e3.6       - Eclipse 3.6: All tests excluding repository tests
mylyn-integration-e3.7       - Eclipse 3.7: All tests including repository tests against all supported versions
mylyn-integration-e4.1       - Eclipse 4.1: All tests including repository tests against all supported versions
mylyn-integration-standalone - Java 1.6   : Tests designed to work outside of an OSGi environment

The full suite of repository tests is only run on the most recent Eclipse platforms. Running the full suite is expensive and a Bugzilla or Trac specific test that fails on Eclipse 3.5 is very likely to also fail on Eclipse 3.7.

Release Jobs

Release and snapshot artifacts created by release jobs are published to

mylyn-3.5.x-release  - e_3_7_m_3_5_x branch
mylyn-3.6.x-release  - e_3_7_m_3_6_x branch
mylyn-release        - master branch


The Mylyn build is based on Maven/Tycho. The minimum required Maven version is 3.0.

  • The org.eclipse.mylyn/org.eclipse.mylyn-parent module specifies a parent pom with common settings. This pom is published to the Mylyn Maven repository.
  • The org.eclipse.mylyn/org.eclipse.mylyn-target module specifies a target definitions. These are published to the Mylyn Maven repository.


mvn package

To skip execution of tests use -Dmaven.test.skip=true


To run tests invoke the following command:

mvn integration-test


  • Check out the org.eclipse.mylyn.all project.
  • Run git submodule init to initialize sub modules
  • Run git submodule update to update sub modules to the latest integration build
  • Run mvn package to build release artifacts.

The Release Howto describes how to build and publish official Mylyn releases.


The build defines profiles to build Mylyn against different targets. Profiles can be activated by passing -P<profile> to mvn.

  • implicit-target - build against nightly repositories, this is the default
  • explicit-target - build against a target definitions in org.eclipse.mylyn/org.eclipse.mylyn-target, needs to be activated through property -Dexplicit-target
  • ganymede, galileo, indigo, juno, e4.1, e4.2 - build against a specific Eclipse release (requires -Dexplicit-target)


Properties control certain aspects of the build such as execution of tests or optional analysis of source code. Properties can be set by passing -D<property>=<value> to mvn. All properties are initialized to sensible default values and are optional.

  • tycho-version - version of Tycho to use for building
  • analysis.skip - set to false to run code analysis (default: true)
  • test.skip - set to false to run tests (default: ${maven.test.skip})
  • sign.skip - set to false to run code signing (default: true)
  • pack.skip - set to false to run pack repositories (default: false)
  • promote.skip - set to false to copy artifacts to download location (default: true)


Mylyn uses the Eclipse code conventions with these minor additions (bug 214179):

Tags: Mylyn uses the following tags in the code:

  • TODO: The following code needs to be reviewed.
  • TODO API: Indicates that a method or class needs to be reviewed.
  • TODO API x.y: This API is going to change for version x.y. Should include a description how it is going to change.
  • TODO e3.4: Make a change in the future specific to an Eclipse version.
  • XXX: The implementation uses a temporary work around that should be replaced by a proper solution in the future.
  • XXX SDK: The code uses internals of the Eclipse platform.
  • FIXME: Should only be used in very rare cases as a reminder that the marked code does not work as expected. Code marked as FIXME should not be distributed in a release.
  • FIXME REVIEW: Review the code before the next version is released

Creating new plug-ins and features

File a bug that describes the purpose of the new plug-ins and the proposed names. Then add an item to the weekly meeting agenda to discuss the request with other committers. Once consensus has been reached follow the steps below.

To retain consistency of layout and settings, new projects should always be created by copying an existing project rather than creating plug-in or feature projects from scratch.

Steps for creating a new plug-in or feature:

  1. Copy an existing project on disk, e.g. to create an org.eclipse.myconnector.core bundle do the equivalent of running cp -a org.eclipse.mylyn.bugzilla.core org.eclipse.mylyn.myconnector.core
  2. Edit pom.xml, .project and META-INF/MANIFEST to reflect the new bundle id
  3. List the new bundle as a module in the parent pom to include it in the build
  4. Use Import Projects from the popup menu in the Git Repositories view to add the project to the workspace

For plug-ins these additional steps should be considered:

  1. Add bundle to feature
  2. Add source bundle to SDK feature

For features these additional steps should be considered:

  1. Add feature to site


Contributions are a key part of evolving Mylyn. All committers should encourage and prioritize contributions.

Applying Patches

  • Note that each patch should not contain more than 250 lines of code of unique and seprately usable functionality. For larger patches we need to invoke the IP Review process.
  • Contributors frequently write quick patches in order to get something working for them. It is the responsibility of the committer to either encourage the contributor to improve the modularity and test coverage of the patch or to do those themselves if this aligns with the projects' priorities. Failing to do so can reduce the overall quality of the code and failing to get sufficient test coverage reduces our ability to evolve the code.

When applying a patch follow these steps:


  • Enter the name of the contributor as the author of the commit
  • Encourage the contributor to update the patch into state where it can be applied unaltered.
  • If you need to make addtional changes that are non-trivial (e.g., copyright header fixes) commit the unaltered patch first and then make another commit with your changes.
    • If absolutely necessary, a task-branch can be used to group commits and improve traceability otherwise commit messages should be sufficient to associate bugs with commits.
  • All files altered by a contributor must have a note in the copyright header and should have an @author tag if a change was significant.
  • If several authors have worked on a commit consider adding Co-authored-by headers to the commit message for each author.
  • Also see Development_Resources/Handling_Git_Contributions .


  • Flag the the patch attachment as iplog+.
  • Add the contributed keyword to the corresponding bug.

Web Site

  • Create a new CVS location:
  • Check out www/mylyn as a project

You need to be a member of the mylyn group to commit changes to the website.


The Mylyn Incubator is a set of projects and feature contributors use for experimentation. These features are not intended to be used for daily development. Incubator features include experimental connectors and bridges, experimental UI features, and developer tools. To use Incubator tools either check them out of the version control, or install them using the Incubator update site.

Dev tools

  • Introspect Object (action): displays the class and other relevant information (e.g. degree-of-interest, task synchronization state) of any object visible in the workbench. Appears at the end of the context menu for any view that accepts an object contributions.
  • Interest Level Decorator: displays the floating point interest level of elements. Enable via Decorators preference page.
  • Repository Spy: displays the repositories with all their atrtributes in a separate view. Allows the deletion of selected properties.
  • Properties View sources: Shows properties of items selected in the Tasklist View or Task Repositories view in the standard Eclipse Properties View.

Experimental tools

The following experimental views can be opened via the Experimental view category or accessed via the Tasks -> Experimental preference page.

  • Context Search: Automatically finds and displays elements that are structurally related to landmarks in the active . These elements become part of the task context and have a predicted degree-of-interest.
  • Context Hierarchy: Displays the Java hierarchy of all landmark elements.
  • Predicted interested for Java errors: Potentially useful, but tends to overload the Package Explorer. If you find this useful for long-term use condiser commenting on bug 107542.

Tips and Tricks

User support

  • Every time that you find yourself formulating an answer to a bug report, email, or newsgroup post, if the answer is more than a sentence, consider updating the FAQ, User Guide, or Integrator Reference and pointing to the entry.
  • Every time that resolving a bug does not result in a code change that addresses the problem or clarifies the UI, update the FAQ or User Guide to make sure that users can self-diagnose the problem. This is particularly important for bugs marked INVALID or WORKSFORME.


  • For error handling use StatusHandler and pass an IStatus object. Note that some of the other Mylyn code uses the convenience methods on StatusHandler, but we are phasing those out because they do not pass the plug-in ID that the exception originated from.
  • Use WorkbenchJob for running jobs that should only run when the workbench is active. Not doing this can cause errors on workbench shutdown (e.g. bug 178409).
  • When using String.toLowerCase(), use String.toLowerCase(Locale.ENGLISH) to ensure locale safety (see bug 168652).
  • Do not use @Override annotations on implementing methods, only on overriding methods. Doing so violates Java 5 (bug 173171).
  • Use DateFormat with extra caution. It is not thread-safe and should not be saved to fields in classes that can be used from multiple threads (UI, asynchonous execution, or jobs).
  • For the sake of multi-monitor setups, use getMonitor() instead of getDisplay() when you want to position a UI element on a specific coordinate of the screen.
  • To improve the speed of decorators use setUseHashlookup(true) on all structured viewers.


  • Query setup: If you are added to the cc list on a report that is not picked up by your usual queries it may go unnoticed. One trick is to create a query for ALL products except the product you usually work in (and hence have queries for) and set the cc field of the query to your id. Now you will be notified of anybody adding you to the cc of a product you don't usually monitor.


  • Including Platform plug-ins in search: Java search (Ctrl+H > Java Search) will include all plugins in your Plugin-in Dependencies. If you want to search other plugins as well, open the Plug-ins view, right click on the desired plugin(s) and choose 'Add to Java Search'. That plugin will now always be included in your java searches.


  • Task List problems: do not ask users to send or attach their Task List, since it can contain highly sensitive information. If needed ask the user to create a new workspace and try to reproduce the problem there, ensuring that they have not included any user private or company private information, and have them send that.
  • Plug-ins fail to load: verify that plug-in dependencies are met via the Validate Plug-in Set button on the launch configuration Plug-ins tab.
  • Startup failure: If you get an IStartup failure message or a ClassNotFoundException on startup this is often the result of some step in the activation of the plug-in failing.
    • Attempt to find the earliest exception thrown within the in the plug-in's activation process. For example, this could occur in TasksUiPlugin.start() or TasksUiPlugin.<init>.
    • If the cause of the failure is not straightforward, the problem could be due to a class loading race condition. This can sometimes be verified by trying a different VM like IBM's or BEA's and checking if that resolves the problem. If this is the case, please file a bug.
  • Getting a thread dump (when Eclipse hangs):
    • On Windows use the tool found at the adaptj home page:
      • Follow the link and select button "Launch" and run the applet
      • Select menu Process > Thread Dump
      • In the combo box "Process ID" select the Java VM and click OK
    • Or, run Eclipse with the -debug option (or use java.exe instead javaw.exe on windows), then
      • On Windows: Hit a Ctrl-Break few times on the console window during that long synchronization to capture the thread dump
    • Or, on Linux: Use Ctrl-\ on the console or send SIG_QUIT signal: kill -SIGQUIT pid
    • Or, with jconsole (requires 1.5 jdk, works on any OS):
      • Launch eclipse -vmargs
      • Launch the JDK's jconsole tool. You can attach to the Java Process and copy&paste the thread dump.
    • Use jps to find the PIDs of Java processes and jstack to show the stack trace of Java processes: jstack pid
      • Supported starting JDK 5 for UNIX / JDK 6 for Windows
    • See this Weblog on jstack
    • Also see Thread Dump and Concurrency Locks for more details.
  • Startup problems and deadlocks: for a diagnosis of a potential problem see diagnosis on

Back to the top