Bringing Mylyn to NetBeans and OSGi, Bridging Their Worlds

Mylyn has been re-used in NetBeans IDE since version 6.9. The fact that we adopted OSGi helps us to run Mylyn in its natural environment. It helps that Mylyn code is usually split into two parts - UI independent and the SWT UI - and we can reuse just the UI independent part (sure, NetBeans is Swing based platform). Still, we are reusing Mylyn in a way that was never tried before and we are running into some issues.

We'll have David Green from Tasktop to ensure we deliver our story from all points of view. Stop by to learn how co-operation between NetBeans and Tasktop guys makes Mylyn more flexible and NetBeans IDE better!

Software Modularity: Paradoxes, Principles, and Architectures

I am about to publish new book about Paradoxes of API Design (not a chapter as was in TheAPIBook, but a complete book with twenty chapters revealing sort of paradoxial observations about API design) and I'd like to promote it a bit during JavaOne2012. Andrzej Olszak agreed to help me. His deep theoretical knowledge of design principles useful for producing viable architectures will be confronted with my paradoxes. Stop by to win a discount for the Paradoxes book.

I really enjoyed Andrzej's part. He talked about so many interesting things. For example he mentioned that there are multiple reasons to modularize your application and each of them leads to completely different architecture.

Patterns for Modularity: What Modules Don’t Want You to Know

This is a third sequel of our patterns for modularity talk. I will join Toni Epple and Zoran Ševarac describing techniques to discover what your modular system tries to hide from your sight. The advices and life demonstrations performed will provide the best tips and tricks to get an amoeba-like beast - e.g. your modular application developed by tens or hundreds of distributed programmers under control.

Hack into Your Compiler!

In this hands-on-lab we plan to learn more about JSR-269 and how we can use it to simplify our code, avoid boiler plate code and make our systems more scalable. The hands-on-lab will take two hours and its content is going to be similar to my talk at GeekOut 2012.