Hello List Members, Whether to layout a project within version control as a WAR based layout (images/ pages/ tiles/ WEB-INF/ WEB-INF/src) or as a sun J2SE blueprint layout (build/ conf/ src/ lib/ webapp/ docs/ test/ etc. http://java.sun.com/blueprints/code/projectconventions.html) is an issue that has long plagued me as a developer and more so as a manager who oversees java developers as well as jsp/dhtml client side personnel.
I've only ever found one or two good threads on the subject, and most (but not all) Java developers I've worked with have favored the J2SE approach. The _HUGE_ downside of this approach is that for a client side jsp or html coder to work, they have to use at minimum Ant and often times have a full IDE installed, so they can WAR the application, deploy it, reload the app server, just to see if changing some column size gives them the output they were hoping for. Assume a standard web application, and the display tier technologies are html / jsp / css (not xslt and xml - as that could be a solution - but not for rich client side web functionality IMO) Has anyone experienced a development process or project layout that can accommodate the J2SE best practices and keep client-side developers away from the drudgery of compile_jar_war_deploy_reload just to see a simple js, css, or html change? I can think of a hybrid approach as well the idea of creating multiple vcs projects for the different team members, but neither of those ideas excite me. Thanks, Eric -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
