Hi
everybody.
Recently I had a
heated discussion with some people in my team about our development directory
structure. We are developing a set of loosely connected modules to be used in
one big web application (the project is large!). I created separate development
structure and created the necessary Ant scripts. But they argued that it is very
hard to work on JSP pages and config files when you need to rebuild all the
time. They prefer to just hit the refresh button of the browser or restart
button of the server and rock&roll.
I tried to explain
that using the same structure for developing and deployment is not
flexible - it is hard to include other frameworks, to create easily
customizable deployment scripts, to construct config files and resources from
smaller chunks, etc.
I pointed the
recommendations from the mailing lists, from Tomcat's documentation, but without
success ... :-( Finally they won and changed the development
tree.
They prefer the easy
way, they want to use their IDE's (JBuilder, JRun Studio) and don't want to use
console scripts.
Please, help !
Give me some convincing real life examples why should we use separate
structures.
Best
regards,
Danail
Grigorov
P.S. One of the
commented applications was Ted Husted's WXXI-GAVEL. They claim that it
uses single development and deployment structure and there is nothing wrong with
that. Can anybody give me some clues ?
