How to create generic projects in Eclipse

For use with Netbeans, Ant, Tomcat etc.

Author: Ivar Abrahamsen

New document location: click here

This document is not finished yet.

A quick howto document to describe setting up projects in Eclipse.

These projects will be generic so that they are compatible with Netbeans, generic Ant scripts etc.


This need came about with my own need to have a slightly different project set up than the default Eclipse WTP one.

I like the integration of Tomcat in Eclipse, But I could not get the grips with which folders was published and which not. Coming from a Netbeans background, where the Ant integration seemed better, I grew frustrated quickly.

Even as Eclipse is very configurable and flexible, in certain areas it was not intuative to my needs. So this is a quick way to get Eclipse to follow you Ant scripts on which folder goes where etc.

Pre-requiresite is a working Eclipse Web Tools set up. Follow my How to install Eclipse in Ubuntu if needed. I will assume the setup is as in my install, so take care if not.


First we need to create a project or use an existing project.

This is my project structure, however the need for this doc is the ability to have any project structure, so you dont have to copy it. This is just so you can see where I am comming from. It is similar to the Jakarta project blueprint.

Whether you are creating a proper project from scratch or importing eclipse over one, you have to tell eclipse its a new project.

Select File/new/project, Select web/dynamic web project.

		dont add project to tomcat 
		add path to properties
		modify server.xml, 
			add jdni resource
			modify localhost to enable deployXML to use context.xml
		deploy once as war to use context.xml for jndi purposes
		download subclipse
		create new builder 
		choose ant
		set auto build to dev-deploy
		lib web classes 
		ant subversion, dev test live 
		deploy context.xml jndi