Q4E has WTP support, from today!

Abel has been rushing to get WTP support working just in time for my talk at EclipseCON. Nice job!

Check the screencast. You will need the development verson of Q4E 0.6.0 until it is released (using the update site at http://q4e.googlecode.com/svn/trunk/updatesite-dev/)

The talk went well, not much to do it 10 min though. Will be posting the slides soon.

Letters from EclipseCON

Yesterday’s Maven, Eclipse and OSGi working together tutorial went fairly well, I thought I would have plenty of time but had to rush through the end. The room (small one) was packed, with aournd 50 people, and the feedback collected by the Eclipse Foundation was 17 positive, 0 negative, so not bad, considering that the tutorial was pretty hardcore stuff and some people were definitely not expecting it (next time I need to make that more clear). I’ll post the material online soon.

Tomorrow I’ll be giving a short talk about Q4E, more user oriented, at 16:50, room 209/210.

Monday ended with the usual suspects (and recently joined ones) like Lynn Gayowski (Eclipse Foundation) and Adrian Mos (Inria), having some beers (free of course), and deciding to make a t-shirt for foreigners (US foreigners) with sentences like "Smart people thinks in Celsius" or "Smart people use colored bank notes" 😀

Seems that today is going to end the same way as yesterday, having some beers during the receptions. Come around and say hi 😉

Update: fixed links

Q for Eclipse 0.5.0 released

A new release of Q4E is out, 0.5.0. Thanks to all the people involved for making such a quick turn around and keep a constant release cycle.

Besides many bug fixes and small improvements, the main changes are:

  • Ability to import pom projects
  • Maven execution can now be canceled.
  • New dependency analysis view! It is now possible to
    display the project dependencies and analyze them to assess where the
    actual dependencies and versions come from.
  • Improved handling of resources:
    • If filtering is configured for resources, it is honored.
    • Inclusion/Exclusion patterns for resources are honored. Now
      it is possible to share a folder for java sources and resources.
    • Note that resources are no longer added to the build path as source folders.
  • The dependency graph is no longer a pop up window. It has its own Eclipse view.
  • Allow maven goals to use artifacts in the workspace when launched
    from q4e, even if they are not installed on the repository

An example of the new Dependency analysis view

Maven at EclipseCON

I’ll be next March 17th-20th at EclipseCON in Santa Clara, California, giving two talks. if you are going to be attending and you want some specific topic to be covered please leave a comment and I’ll try to make your time worthwhile.

Q4E, Maven integration for Eclipse short talk

"Q for Eclipse" (Q4E) is a new Open Source project that integrates
Apache Maven and the Eclipse IDE for faster, more agile, and more
productive development.
The plugin allows you to run Maven from the IDE, import existing Maven
projects without intermediate steps, create new projects using Maven
archetypes, synchronize dependency management, search artifact
repositories for dependencies that are automatically downloaded, view a
graph of dependencies and more!
If you are a Maven and Eclipse user join us to discover how to take
advantage of all these features, as well as how they can help you to
improve your development process. 

Maven, Eclipse and OSGi working together tutorial

With the growing popularity of Apache Maven, Eclipse, and OSGi, the
most frequently-asked questions are: "Can they work together?" and, "Do
they fight for the same space?"
This tutorial will cover the strengths and weaknesses of each, explains
where they overlap, and how they complement each other so you can get
maximum productivity. It pays special attention to the build process,
dependency management, collaboration, repository management, and
available tools, as well as the future direction of the technologies.
The solutions proposed will be based on the work done in the Apache
Maven and Apache Felix projects, along with several Eclipse Foundation
projects like Eclipse PDE
and Eclipse Buckminster.

Q for Eclipse 0.4.0 released

A new release of Q4E, the Eclipse plugin for Maven, is out. I’m going to quote Abel announcement, only adding something that he forgot, the new 0.5.0 release we are working on has initial support for importing parent projects (pom projects).

After some delay (you can blame it on Christmas we committers need to have some fun far away from the computer), there is a new version of q4e waiting for you.

This version is 0.4.0 and has some interesting new features. Probably the best one is that it is much faster.

On the fancier side of things, the dependency viewer has been cleaned a bit and now more cleanly draws the dependencies. Judge for yourself:

q4e dependency viewer

For 0.5.0, we have a new contributor, Jake Pezaro who is working on integrating his dependency analysis tool into q4e.

Also, we are introducing a new and noteworthy page for q4e, and you can follow the current status from the wiki (whats pending, whats done and previous releases changelog). You can use the list of pending tasks to take a look at what were trying to get into 0.5.0 but also to help us! We always welcome helping hands (remember that you can look for easy tasks to get started).

If you like living on the edge, the development update site already has a preview of the upcoming 0.5.0 version. Come and try it!

Eclipse jars now in Maven repository

After some time trying to figure out what the best conversion from Eclipse plugins / OSGi bundles naming conventions to Maven naming I had finally put many Eclipse plugins in the central Maven repository (see only the Eclipse plugins that got copied in this batch). It’s sometimes a bit tricky, but the main goal was a bidirectional automated translation from Bundle-SymbolicName and Bundle-Version to groupId, artifactId and version in Maven.

Basically you take the BundleId and use the dots to split it. The last section is the artifactId, the rest is the groupId. For the versions they are pretty much the same, only changing dashes and underscores. There’s a maven-osgi library very light that you can use to do these conversions, used by the Maven Eclipse and Felix bundle plugins.

This improves the support for building Eclipse plugins from Maven, although you can do some things already, or using Eclipse libraries from Maven projects. We’ll see more activity in these two fields soon.

Some people complained that you get weird jar names like net-1.0.0-I20070531.jar. Something I’d like to point out is that the repository is just an interface, the way artifacts are stored internally shouldn’t matter to the clients (Maven, Ivy,…). Plugins that generate a flat directory with jars (like assembly, war,…) should take care of renaming the jars to groupId.artifactId, to avoid clashes in the namespace, and so you get a meaningful name out of a hierarchical directory structure.

So you want Maven integration in Eclipse?

You are lucky, the Eclipse integration for Apache Maven (Eclipse IAM) proposal has been approved, and is the first step to have a project at the Eclipse Foundation.

The proposal is based on the work done at Q4E and we hope that by taking it into the next level at the Eclipse Foundation more people will be interested and will collaborate to make it completely successful and hopefully part of the Eclipse IDE distribution.

Please join us at the eclipse.technology.iam newsgroup at news.eclipse.org (web interface) for suggestions, discussions and information on the project.

OSSummit Asia

If you happen to be close by Hong Kong ( who isn’t? 😉 ), check out OSSummit, 26-30 November, the first joined conference between The Apache Software Foundation and Eclipse Foundation. I’ll be giving a talk Maven, Eclipse and OSGi working together.

We also hope to have a Birds-of-a-feather (BOF) session during the conference for those interested in Maven.

The Apache Software Foundation and Eclipse Foundation are joining together for the first time at OSSummit ASIA 2007 – November 26 through 30 at the Cyberport in Hong Kong

OSSummit combines 2 days of in-depth hands on trainings followed by a 3 day conference featuring over 60 presentations, Birds of a Feather gatherings to interact throughout each day, interactive keynote panel, and Li Gong Chairman and CEO of Mozilla Online Ltd presenting the featured keynote.

OS Summit Asia