Home » Author Archives: Wayne Beaton (page 2)

Author Archives: Wayne Beaton

Official Eclipse Support for Java(TM) 8

eclipse-logo

Dani Megert, the project lead for the Java development tools (JDT) project made this announcement earlier today: The Eclipse top-level project is very proud to announce official support for Java™ 8. Starting with I20140318-0830 all Luna (4.4) builds contain the Eclipse support for Java™ 8. For Kepler SR2 (4.3.2) a feature patch is available. For future builds visit our downloads ...

Read More »

Playing with Java 8 Lambdas in the JDT

eclipse-logo

I’ve been playing with the language a bit while tinkering with the Java 8 support under development by the Eclipse Java development tools (JDT) project. I’ll admit that I’m a little underwhelmed by lambdas in Java 8. This, of course, comes from an Old Dude Who Knows Smalltalk (and LISP/Scheme). Like any good Smalltalk curmudgeon, when I set about learning ...

Read More »

Building and Running Java 8 Support

eclipse-logo

The Eclipse support for Java 8 is not yet available for download. If you want to play with it, you’ve got to build it. Eclipsepedia’s JDT Core/Java8 page includes instructions for setting up your development environment with the source for the evolving Java 8 support in the Eclipse Java development tools (JDT). There’s a few pieces missing from the instructions; ...

Read More »

PMI Facelift

eclipse-logo

The Project Management Infrastructure (PMI) is still, frankly, a little too ugly for my liking. A proper facelift with the help of a graphics designer and somebody who knows a thing or two about designing websites is still required (and planned). Having said that, we’re taking a small step forward. Over the weekend, I will release an update to the ...

Read More »

Eclipse Project: Releases, Plans, and Reviews

eclipse-logo

For each release, an Eclipse project is required to provide a project plan. The project plan is created at the beginning of a release cycle and may be modified throughout the cycle. The plan tells the community what the main areas of focus are in the project. This lets, for example, contributors know what kinds of contributions are going to ...

Read More »

Two Years of Experience Doesn’t make you “Senior”

software-development-2-logo

Two years of experience doesn’t make you “senior”. Except maybe in high school. I don’t mean this in a negative sort of way. I mean it in a trying-to-help-you-out sort of way. I’ve worked for a relatively small number of companies in my twenty-plus years of professional life. Small by the software industry’s standards, anyway. I’ve been involved in the ...

Read More »

The Eclipse Common Build Infrastructure

eclipse-logo

Creating an Common Build Infrastructure (CBI) at Eclipse has been one of our holy grail pursuits over the years. My main goal in this effort has been to get Eclipse committers out of the build business so that more time and energy can be focused on actually writing software (which is what most software developers would rather spend their time ...

Read More »

Application Lifecycle Management at Eclipse

subversion-logo

The Eclipse Foundation has evolved a pretty impressive application lifecycle management story. Based on what I’ve observed over the years, I believe that it’s completely reasonable to say that our ALM story is one of the best in the world: the envy of hundreds of open source projects and closed source development shops around the world. I believe that our ...

Read More »

Diversity in Open Source Projects

software-development-2-logo

I’ve been talking a lot about diversity lately. There are, of course, different kinds of diversity; but when I talk about diversity, I tend to mean diversity in the organizations contributing to an open source project: multiple organizations from different parts of the industry working together. Doug tweeted recently on the topic: Why do you need diverse projects? So when ...

Read More »

Open Source Rules of Engagement

software-development-2-logo

The Eclipse Development Process (EDP) defines–in its section on principles–three open source rules of engagement: Openness, Transparency, and Meritocracy: Open – Eclipse is open to all; Eclipse provides the same opportunity to all. Everyone participates with the same rules; there are no rules to exclude any potential contributors which include, of course, direct competitors in the marketplace. Transparent – Project ...

Read More »

Want to take your Java skills to the next level?

Grab our programming books for FREE!

Here are some of the eBooks you will get:

  • Advanced Java Guide
  • Java Design Patterns
  • JMeter Tutorial
  • Java 8 Features Tutorial
  • JUnit Tutorial
  • JSF Programming Cookbook
  • Java Concurrency Essentials