So Kepler is finally going through the creation review this Wednesday and hopefully in a matter of a couple of weeks it will be setup as a proper Eclipse project with source control, issue tracking and all those goodies that will allow us to commit our code and show the world what we’ve been working on.
And some more pictures…
Grand Canyon panorama
Brett has posted the interview where we talked about the projects I’ve been working with lately, including Kepler and Q4E, so he saved me from writing a new blog entry 😉
And finally found some time to upload more pictures from my trip to China.
Oriental Pearl Tower
Dragon in Yuyuan Garden
China World Trade Center
Starbucks in Beijing
Drum and Bell towers
Tian’an Men Square
Tian’an Men Square
After a week in Cebu and Manila preparing the launch of a new project (more details to come…) and having more fun than ever thanks to the team there and the Exist people, a 24 trip to Frankfurt via Kuala-Lumpur, and driving as-fast-as-you-can in the Autobahn, I’m finally at the Eclipse Summit Europe 2007 in Ludwisburg with Brett Porter. BTW I added to the right a Dopplr banner so you can see my future trips in case we coincide, for instance I surprisingly met Ben Alex from Acegi security (Spring-security) in Manila who I knew for 3+ years by collaborating in Acegi but never met in person, even when he traveled to Spain or the USA.
Back to Eclipse Summit, this morning was dedicated to Equinox provisioning and afternoon to Server Side Equinox, learning what’s going on in the other projects and talking about Kepler. For those interested I have posted in the Kepler wiki as example on how Kepler and P2 metadata of an Eclipse plugin look like
There are some things in the P2 Instalable Unit model that are not yet in Kepler but could easily be implemented by adding a new facet (extension points)
There’s a new release of the Eclipse plugin for Maven Q4E, with some bugfixes and minor improvements. One of the main problems we are trying to solve is the performance and memory consumption.
The Q4E team is proud to announce the release of version 0.2.2
Changes in this version includes :
- Ability to attach sources to classpath if Download Sources preferences is turned on.
- Fixed Issue 74 – q4e doesn’t release handle on pom.xml when deleting project
- Fixed Issue 75 – Add a refresh cache action to cleanup cache and free up memory
- Fixed Issue 80 – URL pattern matching for "archetype list source URL" is too rigid
- Fixed Issue 81 – http://people.apache.org/repo/m2-incubating-repository is claimed to be an invalid remote repository URL
- Fixed Issue 85 – NLS missing message: MavenEventView_FilterDialog_eventTypes
- Some stability fix
Update from the update site or read the installation instructions.
I’m in Ottawa, at the Equinox Summit 2007, deep dive into Eclipse Equinox, the Eclipse Foundation OSGi framework.
Most interesting bits are about p2 (formerly Equinox provisioning), which basically is a way to populate a OSGi runtime from a repository (similar to a Maven repository), so after talking to Pascal Rapicault I think it’d be great if the default format of the repository were a Maven repo, that would allow using a repository manager like Maestro (or Apache Archiva).
p2 is going to use a new metadata format called Installable Units (IU) that will define the dependencies and other info about the project. It’s interesting to see how this approach aligns with Maven’s, both in the usage of a repository and externalizing the metadata out of the binary artifact (vs. OSGi usage of the manifest.mf). The reason is that the metadata needs to be gathered before the binaries to show information to the user, perform the resolution,…
An interesting point is the role that Kepler can play. Kepler is an Eclipse Foundation proposal created by DevZuz to handle collaboration metadata about projects. I’ll talk in more detail about Kepler in the future as we prepare the creation process, but you can take a look at the wiki. Kepler defines an extensible model with some core information and extensions for things like licensing, participants, build information (Maven, Ant,…), any kind of internal company info,… There’s already a Maven adaptor that will extract the information from a Maven pom, so it’d definitely make sense to have support for Equinox UIs and consider the generation of UIs from poms and viceversa through Kepler.
Another topic was Spring-OSGi by Adrian Colyer (Interface21 CTO), now called Spring Dynamic Modules for the OSGi TM platform (you gotta love trademarks), explaining how Spring easily supports exposing beans as OSGi services and consuming services using proxies to hide the OSGi dynamic nature and alleviate as possible. Right now you can take advantage using the latest 2.1 milestone (upcoming 2.5) of spring-core and spring-osgi jars. They will be increasing their OSGi support to the rest of the spring modules in the next months.
Other topics covered at the summit were tooling, how PDE is going to support these IUs, improvement of headless builds, logging,…
I’d like to introduce the Q for Eclipse (Q4E) project, an Eclipse plugin for Maven.
- running Maven goals from the IDE
- dependency managing using the Maven POM, with automatic download of dependencies
- dependency graphing
- direct import of Maven 2 projects
- wizard for creation of new projects using the archetype mechanism
- modular approach to improve reusability by other Eclipse projects
… and more to come
What can this Eclipse plugin do?
It will allow you to run
Maven goals from the Eclipse IDE, create new Maven projects using
archetypes, import Maven projects without any intermediate steps, view
the dependencies of your project in a graph,… we will keep adding
features with the time
How do I install it?
Refer to Installation
What are the differences between this plugin and m2eclipse (aka Tycho)?
The objective of this plugin is to be part of the Eclipse Foundation, for that reason the license is EPL and we are going to follow the foundation procedures. Thanks to the sponsorship of DevZuz, an Eclipse Strategic Developer Member we are in a good position to achieve this goal.
the objective, there are technical differences. While m2eclipse shows
Maven output in a console, Q is based in events and will show them in
an organized way that allows filtering by severity, search,…
Functionality like the dependency graph, direct import of projects or
creation of new projects using the archetype mechanism are only present
Why the name Q?
Q, named after the special agent Q in the James Bond books and movies. No double meaning or anything like that, we are just James Bond fans 😉
The project is licensed under the EPL and collaborations are welcome, please join the user mailing list to be informed of updates, or the developers list if you want to help with the development or extend the plugin.
You can also take a look at the list of known issues.