TM Developer Resources

CVS Repository TM development is managed in the RSE and Core Repositories. To populate an Eclipse workspace with our code, best use our Team Project Sets. A CVS Changelog is available, and you can subscribe to commit notifications on tm-cvs-commit.
Bug Process
View all open issues | Submit new bugs | Request an enhancement
Eclipse API Scanner
Describe the API of a component and scan plug-ins for API violations (from the WebTools project).
Check Unused Properties Tool
Scan property files for unused messages (from the WebTools project).
Core Tools
Useful utilities from the Platform team. Consider adding their update site to your configuration.
Building RSE
Instructions how to perform unattended builds of TM / RSE.
Release Engineering
See the instructions, FAQs and help from the Platform-Releng team.
Eclipse Committer Tools
Information on infrastructure status, file path information, FAQs, etc. [login required]

Committer HOWTO
Simple cookbook instructions for performing basic tasks properly. Committers need to follow check-in conventions and IP Due Diligence as outlined here.
API Guidelines
Look here for general Eclipse API rules of engagement. We strive to achieve Eclipse Quality, as outlined in the draft of Eclipse Quality APIs.
Development Conventions and Guidelines
Coding standards, naming conventions, and other guidelines used by the Platform. TM will use these conventions until such time as deviation is required.
Architectural Overview
A high level summary of the components and their architecture.
Project Requirements
Look here for a list of the project use cases and their priorities.
Charter
As a Tools subproject, the TM project abides by the Tools Project charter and the Eclipse Standard Charter.
Contributors and Committers
List of TM Project contributors and committers.