Eclipse Mylyn becomes a top-level project

http://www.infoq.com/cn/news/2010/09/eclipse-mylyn/as the Lifecycle management tool for applications, eclipse The Mylyn project has been promoted to a top-level eclipse project (but still retains Mylyn as its abbreviation). Its project charter illustrates its purpose in the ecosystem.

This is no different for the average Eclipse Mylyn user (direct). Mylyn will continue to be developed by the original project performer and provide the same type of experience as the current use: Focus on the developer. Becoming Eclipse's top-level project also means that the current project structure is obsolete, and the organization of Eclipse's current project has two levels of execution structure, one for eclipse projects like JDT and Pde, and one for tool projects like CDT and PDT.

In order to find the location of the project, Mylyn spent a lot of time, it has been through the incubator, through the technical project phase, and then the tool project phase, until eventually become the top-level project. The subject of the project is no longer a technical or tool project, and the choice of its nature is arbitrary, and in many cases is not visible to the user and the project performer. Sharding is primarily based on CVS or the SVN root, which leads to a discussion of whether the project is migrating to git or getting rid of the constraints of the execution library structure (enforced repository structure).

As part of the re-organization effort, Mylyn is creating some level two projects of its own. This is actually just a re-chunking of the existing Mylyn module, where the Egit and CVS connectors become part of the MYLYN/SCM project, and Bugzilla and TRAC connectors are part of the Mylyn/tasks project and the Mylyn/context project. This forms the basis of the active UI filtering mechanism, which makes the Mylyn popular again.

However, Mylyn has not remained stable for many years and is becoming more diversified. Mylyn's wikitext component was originally designed to be a friendly way of writing bug reports, and now it has become a separate Mylyn/docs project as a byproduct, with the addition of rich text-based editing capabilities. Similarly, Mylyn has been extended and integrated with Hudson, which includes the ability to read console output and can be embedded in failed tests on the server as easily as it does with local test failures.

Finally, Mylyn set a goal for itself, which is to provide an interface to a code-based censorship system, initially to provide a simple task-based Mylyn review system and embed it in an existing code review system.

For more information, please check out the interview with Mik Kersten and the project Charter.

Eclipse Mylyn becomes a top-level project