[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: J2EE JSP/Servlet Project Source Repository Layout

From: Jim Van Fleet <jim_at_jimvanfleet.com>
Date: 2005-02-07 22:20:24 CET

Eric Martin wrote:
> <repos name>
> applications
> <j2ee-web-project-name>
> branches
> tags
> trunk
> <best-practice-j2ee-web-project-layout-goes-here>
> commons
> external (vendor)

This looks big? I've got a good idea what external is for, but what
about commons? Is that in-house utility code?

> Any suggestions for <best-practice-j2ee-web-project-layout-goes-here>?
> Perhaps:
> trunk
> build
> src
> webapps
> Any thoughts?

Get comfortable enough with Ant and you can get away with anything.

I've got this:


I have some libraries dropping some stuff directly under trunk (e.g. hbm
and webwork-template directories), but those could just have easily gone

It's my belief that any elements directly derivable with minimal effort
from a working copy should not be stored *within* the repository. This
would mean keeping build and dist directories out of the repository
space completely. (Mine are trunk/../build and trunk/../dist).

By seperating out JSP, you can more easily process zips or tarballs from
your graphics people, if you have them.

Just my 2 cents.



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 7 22:22:42 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.