The Git distributed versioning system is being increasingly adopted by the developer community. Using Git for version control makes Gerrit the natural choice for code reviews. Besides source code, requirements and build artifacts lay an important role in the development cycle which are often managed in Hudson and Bugzilla. While these tools enable exciting development process improvements, adapting to new workflows and learning how to push, pull and fetch can be daunting. Furthermore, switching between command line, web-browser and Eclipse-based tool interfaces breaks the flow.
For tasks, Mylyn already streamlines workflow by providing first-class integration with the IDE. The recent Mylyn project restructuring now enables 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 requirement. On task activation, the EGit Mylyn integration automatically branches managing the change in the workspace. Once a commit is pushed Gerrit stages the change, creates a code review and a Hudson build is triggered to execute tests. Meanwhile, the Mylyn Reviews project enables a team member to complete a code review and provide feedback to the developer, all without leaving the IDE. We will show how the tools available in the Mylyn project work together to seamlessly integrate development artifacts in Eclipse and provide traceability all the way from the requirement to the final merge into the production branch.

REST is a technique for providing light weight Web Services and in Java EE the Java API for RESTful Services (JAX-RS) provides the service framework. The Java Persistence API (JPA) provides the data access and Java Architecture for XML Binding (JAXB) handles marshalling the persistent entities into and out of XML. Sound great! There are a number of issues developers have to deal with when using them together. In this session we'll look at how to build RESTful services with Eclipse WTP using these standard technologies, their integration points and where the pain points are, and how to avoid them using EclipseLink's advanced REST/JAXB/JPA integrations features.

M2Eclipse provides a robust and mature solution for integrating Maven with the Eclipse IDE. M2Eclipse continues on the path to be the de-facto standard Eclipse integration for Maven users and Maven integrators alike. Features unique to M2Eclipse, such as the POM editor and support for the Nexus repository indexes, dramatically reduce the Maven learning curve and give full access to numerous Maven and p2 repositories around the world.

An open Project Configuration Framework unifies the IDE with automated, headless environments by synchronizing Eclipse settings for technologies like JDT, AJDT and WTP with their Maven counterparts. A viable solution for the ever present tension between build automation and development.

This presentation will review and demonstrate the features that currently exist in M2Eclipse. We will also discuss extensions build on top of the open API, such as expanded vision of project materialization encompassing much more than just source and binary dependencies and including issues and documentation to provide a unique developer "on-boarding" solution that will decrease downtime and increasing developer mobility. Finally we'll talk about project roadmap and the future plans.