Revision as of 12:37, 23 July 2007

Integrators: if your tool builds on or integrates Mylyn please add it by editing this page. Order is alphabetical.

Connectors bundled with Mylyn can be found on the Download Page.

Bundlings

CodeGear JBuilder 2007

JBuilder 2007 bundles Mylyn and includes a task repository connector for XPlanner. For more information see the video documentation.

License: Commercial

Connectors

CodeBeamer Mylyn Connector

CodeBeamer from Intland Software, GmbH is a highly scalable collaborative software development platform used by sites such as JavaForge.com. The CodeBeamer connector for Mylyn gives you an access to bug/issue trackers in a project hosted at JavaForge.com (or any other hosting site powered by CodeBeamer). You can create bugs/issues in Eclipse, you can associate Mylyn task context with the issues, you can query or search all trackers in your CodeBeamer managed project.

License: tbd (free)

Update sites:

• Eclipse 3.2 and 3.3: cbconnector.javaforge.com/update/2.0

Issue Tracker (IssueZilla) Mylyn Connector

Issue Tracker is spin off project from bugzilla and is part of the CollabNet Enterprise Edition tool suite. This connector allows users to access and manipulate Issue Tracker issues through Eclipse Mylyn.

License: CollabNet Desktop Software End User License Agreement

Update sites:

• Eclipse 3.3: downloads.open.collab.net/eclipse/update-site/e3.3/
• Eclipse 3.2: downloads.open.collab.net/eclipse/update-site/e3.2/

Mantis Mylyn Connector

This project is an Eclipse Mylyn Repository plug-in for the Mantis Bug Tracking application using the Mantis Connect SOAP interface. This Repository Connector is alpha quality. Patches to improve the functionality would be appreciated -- see contributing on the connector home page to get started.

The latest version adds support for the majority of the mylyn features, and close to the feature set of the trac plugin.

License: EPL

Update sites:

• Eclipse 3.3: mylyn-mantis.sourceforge.net/eclipse/update

Project Tracker Mylyn Connector

Project Tracker a flexible tracking system that is part of the CollabNet Enterprise Edition tool suite. Project Tracker's primary focus is on software artifacts such as defects and enhancements, but is suitable for handling many other record oriented artifacts. Project Tracker is fully integrated with version control tools. This connector allows users to access and manipulate Project Tracker artifacts through Eclipse Mylyn.

License: CollabNet Desktop Software End User License Agreement

Update sites:

• Eclipse 3.3: downloads.open.collab.net/eclipse/update-site/e3.3/
• Eclipse 3.2: downloads.open.collab.net/eclipse/update-site/e3.2/

Track+ Mylyn Connector

Track+ is a web based professional project management and issue tracking system. It has a highly configurable access control system, supports workflows and project accounting. Here you can obtain the Track+ Mylyn connector to use Track+ from within Eclipse.

License: GPL

Update sites: www.trackplus.com/files/update-site/e3.2/trackplus-mylar

Bridges

Dynamic Languages via Eclipse DLTK

The Eclipse DLTK project provides structure bridges that support Mylyn's context model for languages such as Tcl, Ruby, Python and JavaScript. For more information see the Xored video documentation.

License: EPL

Update site: to come

Pydev

The Pydev project provides a structure bridge that supports the Pydev Package Explorer and Python elements in the Project Explorer. It currently works at the resource-level.

License: EPL

Update site: http://pydev.sourceforge.net/updates/

Spring IDE

The Spring IDE Mylyn Integration provides:

• A Structure and UI Bridge for Spring elements that works on Spring-element level (<bean />, <property /> or <constructor-arg /> elements)
• Automatic code folding in XML editor based on current interest context (Code Folding for Structured Text Editors needs to be enabled)
• Content assist proposal resorting based current interest context in the XML editor
• Interest-level filtering in the Spring specific views, like Spring Explorer and Beans Cross References View

The Mylyn Integration is currently under development, but can be installed to preview from Spring IDE's nightly updatesite.

License: EPL

Update site: http://springide.org/updatesite_nightly

Version Control

Subclipse Integration

Subclipse is a Subversion client for Eclipse. Supported features: automatic Change Set management (see Mylyn FAQ Team Support), automatic commit messages, Open Corresponding Task action to open Mylyn's task editor from the Change Set in Synchronize view and from entries in History view.

License: EPL

Update site: subclipse.tigris.org/update_1.2.x

Subversive Integration

Subversive is a Subversion client for Eclipse. See Polarion's Mylyn Integration Quick Start

License: EPL

Update site: www.polarion.org/projects/subversive/download/1.1/update-site/

Duplicate Detectors

Mylyn provides an extension point that allows contributors to create duplicate detectors. Each duplicate detector can use its own algorithm to determine if any similar bugs exist in the bug repository.

org.eclipse.mylyn.internal.bugzilla.ide.StackTraceDuplicateDetector can be used as a reference implementation.

When you create a duplicate detector, you need to specify the extension in the plugin.xml file. Below is the entry from the org.eclipse.mylyn.internal.bugzilla.ide plugin.xml file, as an example.

   <extension point="org.eclipse.mylyn.tasks.ui.duplicateDetectors">
       <detector class="org.eclipse.mylyn.internal.bugzilla.ide.StackTraceDuplicateDetector"
                 name="Stack Trace">
       </detector>       
   </extension>

The class attribute of the detector extension is required and must be a subclass of org.eclipse.mylyn.tasks.ui.AbstractDuplicateDetector. The name is also required and must be a string. The name attribute will be displayed on the New Repository Task editor, so make sure it is short but descriptive. There is also an optional kind attribute - this attribute allows you to specify what kind of repository your duplicate detector works with. If you leave the kind attribute blank, your duplicate detector may be displayed in the duplicate detector list for every repository (i.e., users could choose to use your detector regardless of the type of repository that they are using)

The default behaviour is for every editor that inherits from org.eclipse.mylyn.tasks.ui.editors.AbstractNewRepositoryTaskEditor to display all of the duplicate detectors that are available. If you want to modify the list of duplicate detectors that are shown, you should override AbstractNewRepositoryTaskEditor's getDuplicateSearchCollectorsList() method and return only the List of AbstractDuplicateDetectors that you want to be displayed. This is where the kind attribute could be useful - for example, the org.eclipse.mylyn.internal.bugzilla.ui.editor.NewBugzillaTaskEditor could override getDuplicateSearchCollectorList() and return a list that contains only the duplicate detectors where the kind was specific as Bugzilla.

To create a duplicate detector you should:

• Create your duplicate detector class that subclasses org.eclipse.mylyn.tasks.ui.AbstractDuplicateDetector
• Create a subclass SearchHitCollector to query the repository for duplicates
• Within your duplicate detector class, override the public SearchHitCollector getSearchHitCollector(TaskRepository repository, RepositoryTaskData taskData) method to use your new SearchHitCollector
• Specify the extension (as shown above) in the plugin.xml file in the same plugin as your duplicate detector class and your subclass of SearchHitCollector.