Pete Muir

Bio

Pete Muir

I am leading the CDI 1.1 specification, and work on JBoss Developer Framework, a
set of tutorials and examples for all JBoss users. Previously, I've worked on
Infinispan and I led the Seam and Weld projects, and am a founder of the
Arquillian project. I've worked on a number of specifications including JSF 2.0,
AtInject and Java EE 7. I am a regular speaker at JUGs and conferences such as
JavaOne, Devoxx, JAX, JavaBlend, JSFDays, JBoss World, Red Hat Developer Day and
JUDCon.
I am currently employed by Red Hat Inc. working on JBoss open source projects.
Before working for Red Hat, I used and contributed to Seam whilst working at a
UK based staffing agency as IT Development Manager.

Weld Extensions is set of portable services and utility classes for CDI which make up a good base layer for extension and application development. You can read more about the sort of portable extensions we are planning in this interview I gave.

Recently, we've been working hard on a solution to improve the testability of Java EE, and particularly JBoss AS. I'm pleased to say that a critical piece of puzzle, Arqullian, is now available. Congratulations to Aslak and the Arquillian team for releasing the first alpha of Arquillian! You can read more about Arquillian's mission, and our plans for Java EE testing below; alternatively, there are some quick links at the bottom if you want to dive right in.

I want to spend a moment introducing you to a team restructuring we're undertaking for the Seam and Weld projects. We have decided to consolidate the community-focused roles that various people have held in the past to a single person. Whilst I (as project lead) am often focused on architecture, making sure releases happen on time, and coordinating the various contributors, the community liaison is more focused on making sure the project is both easy to consume by the community and easy to contribute ideas and code into.

James and Cheyenne (from the JBoss.org design team) have been hard at work creating a logo. We've worked through a few designs, and picked a few that we want to share with the community and get feedback on.

I've alluded to our plans for the CDI TCK, but I wanted to expand upon them. We're pretty proud of the fact that the CDI TCK is open source (something we share in common with Bean Validation and JSR-330 in the Java EE space), and we intend to treat the TCK like any other open source project (as far as possible within the constraints set by the JCP).