Archive for the ‘q4e’ Category
I have been deep into configuring a development ecosystem with my client lately, with a boring session of integration tests for another project going in parallel, so I wanted to try something different for a change.
Eclipse 3.5 is about to come out and I have been playing with the RCs for a while. I’m on a Mac, so one of the things I wanted to see the new support for Cocoa (so far works great, but I have not been able to use Java 6 or 64bits). The other one was updating Eclipse IAM to run on the new Eclipse.
Creating a Lift project
Step one is creating the project from the lift archetype.
After all dependencies are downloaded I was welcome with some build errors on the test cases, which seem to be caused by Lift’s open dependency on Jetty (there were some refactorings in Jetty 7).
Setting an upper bound of 7.0.0 for the jetty dependency fixed those.
<dependency> <groupid>org.mortbay.jetty</groupid> <artifactid>jetty</artifactid> <version>[6.1.6,7.0.0)</version> <scope>test</scope> </dependency>
Clean the project and the errors are gone.
Running the project
Starting with Lift, suggests running the project launching jetty from maven. I wanted to use WTP instead, so I tried to install the Jetty adapter by using the support in WTP for downloadable adaptors. Unfortunately, the installation did not work, so I used the built-in support for Tomcat 5.5 instead.
Before getting into the next chapter of Starting with Lift, I played around with the application I had just built.
- Changes to index.html were shown immediatly
- Same thing when modifying the default.html template
- Modifying the HelloWorld class to return a new value causes the context to be reloaded and the changes can be seen live (no redeployment needed)
- Adding a second method to HelloWorld and using it on the index.html template works as above (as expected)
End of chapter one
There might be some surprises down the road, but the initial impression has been good.
- IAM has “just worked” and stayed out of the way in a non-java project (there is no special support on IAM for Scala or Lift, although esmi is on the works)
- WTP performed well. I expect the issues with the installation of the Jetty adapter to go away soon, since Jetty has joined Eclipse.
- About Lift and Scala… well, I have a lot of things to learn yet.
I am looking forward to keep using these tools together (at least go through the Starting with Lift guide!).
This is meant to be my introduction to the Eclipse blogging community. It is something that I have delayed too much already, but (finally) I got around to writing it.
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.
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).
The Eclipse IAM/q4e team has released a new version.
I would talk about the new features, but there is an extremely nice New and Noteworthy page on the wiki which has saved me some work.
I would point out only a few features that I really like:
- Autocompletion for dependencies in pom.xml. This is nicely done by installing the WTP XML editor if your eclipse doesn’t have it. Suggestions come from the new artifact search framework.
- Using maven mojos in the workspace for your builds. This new feature will be really useful for maven plug-in developers… we want your feedback!
- An upgraded embedder which allows the use of Maven 2.0.9 features (and plug-ins using those feaures).
Hope you enjoy using q4e as much as we enjoyed making this release!
Q for Eclipse, or q4e for short, is an open-source and open-development eclipse plug-in for bridging the gap between Eclipse and Maven. It is available from its google code home.
Since we believe that every eclipse user should be able to enjoy the benefits of using maven, we’ve proposed IAM (Integration for Apache Maven) as a new Eclipse project. Of course we offered q4e as an initial code contribution for the project. The proposal is discussed on its eclipse newsgroup (you’ll need to get a password from eclipse).
We’ve been working towards becoming a good candidate for an Eclipse project. The number of committers and the overall project activity has been growing, we’ve provided WTP integration, allowed sophisticated dependency analiysis… and much more.
Now, we’re gearing towards the final step for donating q4e source to the IAM proposal… getting IAM into the eclipse incubator.
For this, we needed two eclipse mentors.
Well, we’ve got three
- Ed Merks, IBM: Eclipse EMF
- Thomas Watson, IBM, Equinox
- Brett Porter, Exist Global: Maven PMC, Apache member,…
Being an official Eclipse project can only bring good things to q4e. Since we will have more eyes on the project, more enhancements will be requested and more hands will join in.
If you use q4e, feel free to write some quotes on the IAM group. We always like to know who’s using q4e and where!
Exciting times are ahead!