[jpaulsmith1]

There seems to be a subtle, but ongoing mismatch between eclipse project structures, and
J2EE structures (so subtle I can’t quite pin it down….)

Can anybody recommend a good tutorial (myeclipse or elsewhere) on the subject of
project/directory structures outside eclipse/myeclipse.

i.e. split directory structures(src,build), importing & exporting. etc. maybe a CVS tutorial on this.

Thanks.

[Scott Anderson]

The issue that you’re running into is that there is no such thing as a “standard J2EE project structure”, and there never has been. It’s simply not any any specification, anywhere.

As a result, there are many project styles in use in various areas. From a practicality standpoint, I simply use whatever structure is most expiedient with the tool / process I’m using at the moment as this allows me to focus on “development”, not on “set up”. Interestingly, this is why Ruby on Rails is so popular; it simply dictates how everything works and people just do it that way. Very efficient. In Java, people seem to like to worry about such minor issues and want things “just so” before they can get to work. Rather odd, really.

MyEclipse conforms to a “defacto standard” of simply setting up projects like their unarchived deployment targets (ie. WAR, EJB jar, EAR), which is common in many tools and deployers. For more information on how projects work in MyEclipse, please see the Documentation section. The Working with Web Projects quickstart is a good starting point.

Hope that helps.

[jpaulsmith1]

Thanks, that helps, What I’m getting towards is the most efficient/intuitive structures for team development, where individual developers can see their work in relation to the whole. (on multiple EAR projects). I’ll experiment (and maybe check out ‘Ruby on Rails’ as well).

[Author]

Posts