During software maintenance, developers are confronted with large amounts of code and little insight about the originial design decisions and intentions.
Most of the time is spent reading and understanding the code and determining the implication of code changes.
Projects utilizing the Context feature of Mylyn (or a traceability solution) offer a major advantage to maintenance developers.
Such tools enable the developers to be more efficient by support him at:
* localizing the defect cause
* localizing the correct location of the fix/change request
Collaborative software development is the key to drive innovation in today's software industry and to realize increased efficiency. Today's teams are often geographically or organizationally distributed, adding the complications of different time zones, corporate policies, and languages to the process. All these factors require development teams to communicate and monitor progress throughout the development lifecycle and to work together to find solutions that deliver effective software shipped on time and on budget.
State of the art application development tool stacks often include a variety of ALM systems that are disconnected from each other and lack integration with tools typically used by developers. For tasks, Eclipse Mylyn streamlines workflow by providing first-class integration with the IDE. New Mylyn connectors now enable the same integrated workflows for code reviews, builds and version control systems like Git. For example, a developer can use the Mylyn Task List to track a Bugzilla requirement.
The heterogeneous ALM stacks commonly found in enterprises challenge users with a lack of integration. Data in systems deployed across the organization gets out sync causing a disconnect between stakeholders and developers. Mylyn's broad ecosystem of extensions bridges that gap with the popular IDE tooling that providing visibility into projects. These tools are based on the frameworks of the Mylyn sub-projects that cover key ALM concerns. In this talk we will examine how the APIs for tasks, versions, builds, reviews and contexts can be orchestrated and extended to link ALM systems.
Open Services for Lifecycle Collaboration (OSLC) challenges the conventional thinking of API-based product integrations. OSLC provides a way to integrate applications just like the web integrates content, documents, and data. Linked data is the foundation of OSLC, which is driving the vision of Web 3.0 - Data on the web. Eclipse Lyo is a toolkit to help make this transition from traditional API based approach to integration to a more Linked Data style integration model.
Continuous Integration should be the cornerstone of your development project. But have you embraced it yet? Whether you are working on an Eclipse project, in an enterprise development team, behind a firewall or in the cloud or just interested in the buzz around CI then this tutorial is for you.
Using a mix of short overviews and hands-on exercises developers will gain first hand experience from Hudson experts on setting up Hudson for managed and non-managed Master-slave configuration and preparing Hudson for a cloud environment using Active slaves.
Hudson CI server is often used merely as an automated build system and to run tests. But is it at the heart of your development process? Is it providing the fast, self-testing, automated feedback to your development team that increases their ownership of the code and decreases the time it takes for bugs to be discovered and new features to be available to the whole team? Are you overwhelmed by the range and diversity of the plugins available and which will be most effective for your project? Is security an issue for you?