Eclipse, SAP and Project Pave

Eclipse, SAP and Project Pave

A new project proposal came through my inbox this morning.

The Pave project is a proposed open source project under the Eclipse Web Tools Platform Project.

The Pave project provides a framework for composing sequences of frequently executed operations. These sequences are called patterns and are meant to provide error proof path for users in the execution of routine tasks. You are invited to comment on and/or join the project. Please send all feedback to the newsgroup.

While I’m still blurry on what exactly will be done in the project (maybe someone from the project can shed some light), it’s interesting to note that this project comes from a fairly large company known as SAP.

SAP Logo

SAP’s involvement in Eclipse has grown significantly over the last couple of years. I believe it first started with the excellent Eclipse Memory Analyzer (MAT) project. Now it looks like SAP is involved in:


I think it’s a good sign when a large company starts investing into the technology they are basing their current and future product lines on. From a personal point of view, I would be curious to see the culture shift inside of SAP when it comes to open source. I’m fascinated with how companies change internally to work with open source communities. At my time with another large company, there was a certain set of people who understood open source and those who didn’t. I remember one time there were people that suggested working on a project internally and than just dumping the code over the “open source fence” every release would be good enough. Oh how far have we come 😉

In the end, I hope to hear more good things about SAP getting involved in Eclipse and open source.

  • Ralph Mueller
    Posted at 06:26, 2009-05-17

    If you want to ask them:

    Meet them at the Walldorf Demo Camp:


  • Kaloyan Raev
    Posted at 10:21, 2009-05-20

    I think the SAP story of contributing to Eclipse started back in 2006 when Java EE 5 was in the highlights. That time we realized that it is better to step in the Eclipse WTP open source project and make the changes we need there instead of developing strange workarounds in our commercial product.

    Since that time the shift is going on – slowly, but steadily. Bigger stones have bigger intertia. It’s just the matter of hitting the right direction.