The OSGi console is a great help in such cases. The `diag` command can tell you what’s wrong. Usually it is a dependency that is missing.

Start by launching eclipse from the command line with the -console command line option.

Now, just diag your.bundle.id, and you’ll see eclipse telling you what’s wrong.

• Joakim Erdfelt, who has started by enhancing wtp integration to reach beyond web projects.
• Ismael Teijeiro, author of the Buckminster integration and maven actor.

More news soon!

It was a great experience (my first time with the eclipse community). The event was incredibly well organized! Congratulations!

It was not perfect, though. Both IAM and M2E had new&noteworthy talks, but finally M2E was cancelled… I was hoping to meet Jason on that talk, so I was a bit disappointed.

I couldn’t meet with Ed Merks (which is one of the IAM mentors)… he is a busy guy!

Another problem… too many great talks! I was tempted for a moment to skip my IAM New & Noteworthy talk so I could attend the parallel sessions (specially Equinox P2: Provisioning your world by Jeff McAffer).

On the good side, I was able to meet with some of the Eclipse community in Spain, which seems to be focused on modeling. There are the folks from the European Software Institute, which had a poster on the first day and then some more from the MOSKitt team (who are hosting an Eclipse Day next week).

I attended the Buckminster talks (IAM added Buckminster support a while back, with some more waiting on bugzilla) and found it very interesting for several tasks, specially creating target platforms.

Finally. the two main things that I got back from ESE2008 regarding IAM are:

• People do care about maven integration, but not only as users. Questions about integration of P2 and Maven was raised several times, so it is good to know that we have that on IAM’s project plan.
• Users still wonder why there are 2 integration plug-ins for maven. Well, I so do I! Let’s see if we can change this in the future.

A great experience! Hope I can repeat soon!

I’ll be arriving at Ludwigsburg this tuesday evening, so if anyone feels like having a late refreshment, let me know.

On Wednesday I’ll be assisting to some of the talks (still have not decided) and I expect to have some time to talk with other attendees.

Thursday is the day for my IAM New and Noteworthy talk. If you are interested in Maven integration in Eclipse, you should come!

Ismael Teijeiro will also be coming. He has contributed the integration of IAM with Buckminster. This a bridge between the two projects which works in both directions… IAM can use Buckminster and Buckminster can use IAM. It is an extremely interesting work, so you might want to learn more from him.

After the summit, I’ll spend a few days on Stuttgart, so you have one more chance to learn more about IAM .

My name is Abel Muiño (but just write Muino if you have a non-spanish keyboard),  and I am the project lead for Eclipse IAM, which stands for Integration for Apache Maven.

Eclipse IAM is a technology project focused in integrating maven into the eclipse IDE. It comes with a year-long history as Q4E.

I’m thrilled by joining this community of exceptional developers, and looking forward to meet some of you at Eclipse Summit Europe in a few days (by the way, be sure to attend the “IAM New & Noteworthy” talk… I’ve heard the speaker is extremely handsome).

When providing a SelectionListener for doing a something when a SWT button is pressed, you’ll need to implement two methods:

Button b = new Button(container, SWT.PUSH);
b.addSelectionListener( new SelectionListener()
{
  public void widgetSelected( SelectionEvent e )
  {
    // TODO Auto-generated method stub
  }

  public void widgetDefaultSelected( SelectionEvent e )
  {
    // TODO Auto-generated method stub
  }
} );

However, only one of those methods will be called: widgetSelected

So you can save a couple of lines (which is always nice, specially when inlining the handlers like in these examples) by using SelectionAdapter, an implementation of SelectionListener with default implementation of both methods (which is to do nothing).

The final, shorter, core looks like this:

Button b = new Button(container, SWT.PUSH);
b.addSelectionListener( new SelectionAdapter()
{
  public void widgetSelected( SelectionEvent e )
  {
    doSomething();
  }
} );

You can visit EPIC, rate Q for Eclipse and leave your comments.

It should also be much easier for new users to get to know Q for Eclipse.

In Adapting, the last post of the series, he shows some code to check if an object is or adapts to a given interface. This code has the problem that it needs to be repeated for every interface you need to check against.

The process is:

1. Check if the object already implements the interface.
2. If it doesn’t, check if it implements IAdaptable and can adapt to the interface.
3. If it doesn’t, check if an adapter can be found through the Platform.getAdapterManager().loadAdapter(…)

My solution to avoid repeating code and leverage Java5 generics is this:

private <T> T adaptAs( Class<T> clazz, Object object )
{
    if ( object == null )
    {
        return null;
    }
    if ( clazz.isAssignableFrom( object.getClass() ) )
    {
        return (T) object;
    }
    if ( object instanceof IAdaptable )
    {
        return (T) ( (IAdaptable) object ).getAdapter( clazz );
    }
    else
    {
        return (T) Platform.getAdapterManager().getAdapter( object, clazz );
    }
}

More solutions, all of them Java 1.4 compatible, are listed in the eclipse bug 118560.

1. Update your q4e version from the development update site
2. Create a New project
3. Select the Maven 2 project creation wizard
4. Give it a name… like webtest
5. Select a web archetype… let’s say wicket-archetype-quickstart (the last in the wizard’s list)
6. Finish and wait while the dependencies are downloaded
7. Right click on the project, Run as… > Run on Server and select a Tomcat server.

Did it work? Sure it did… see it in action! (thank to Joakim Erdfelt for hosting it)

But, wait… this is the same process used for creating any q4e project, right?

Exactly!

Don’t you love when things are so simple?

And you can do hot deployment, edit your classes, save and see changes… edit resources… everything is updated in a few seconds.

This is bleeding edge, so we’re really interesting in receiving your feedback. Drop us a line on the q4e groups.

Support for WTP is only an example of what’s possible with q4e, a proof of concept of its extensibility. If you’re interested in developing support for your plug-in, let us know on the developers list. We can help!

My goal for 0.6.0 will be to abstract q4e from the JDT and make it a little smarter along the way. Smart enough to know what kind of project you are creating/importing and set up your workspace accordingly.

This includes many fronts quite probably I won’t be able to cover them all in one release, but at least the way will be paved for 3rd party plug-ins that can add support for other languages (like scala) and other plug-ins (like springide and wtp).

So… yes I’ll try to move closer to supporting wtp. I know many of you are just waiting for this… and we’re listening.

What other things would you include in your wishlist for 0.6.0?