Archive for the ‘wtp’ Category
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!
Developing web applications with maven and q4e is really, really easy… try this:
- Update your q4e version from the development update site
- Create a New project
- Select the Maven 2 project creation wizard
- Give it a name… like webtest
- Select a web archetype… let’s say wicket-archetype-quickstart (the last in the wizard’s list)
- Finish and wait while the dependencies are downloaded
- Right click on the project, Run as… > Run on Server and select a Tomcat server.
But, wait… this is the same process used for creating any q4e project, right?
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?