First impressions on Eclipse 3.5 RC4, IAM, Scala IDE and Lift

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.

These notes can be seen as a total noob’s comments on Scala and Lift.


Everything installed nicely on Eclipse 3.5 (JEE package for Mac OS X Cocoa). I have used the nighty release of IAM.

Creating a Lift project

Step one is creating the project from the lift archetype.

Creating a new lift project with the new maven project wizard

Creating a new lift project with the new maven project wizard

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).

Compile errors after creating the project

Compile errors after creating the project

Setting an upper bound of 7.0.0 for the jetty dependency fixed those.







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.

The LIft webapp is up and running

The LIft webapp is up and running

Playing around

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!).


  1. Hey Abel,

    If you have generic Scala questions, the #scala IRC channel is usually helpful. There are also some people familiar with Lift there, but not as many.


  • My profile

    View Abel Muño's profile on LinkedIn

    amuino on Twitter

  • My projects

    The cloud market:
    Find the virtual image you need on the cloud.
  • Top Posts

  • Archives

  • Categories

%d bloggers like this: