From users-return-7482-apmail-maven-users-archive=maven.apache.org@maven.apache.org Fri Aug 01 10:11:44 2003 Return-Path: Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 32805 invoked by uid 500); 1 Aug 2003 10:11:44 -0000 Mailing-List: contact users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Maven Users List" Reply-To: "Maven Users List" Delivered-To: mailing list users@maven.apache.org Received: (qmail 53970 invoked from network); 1 Aug 2003 08:54:09 -0000 Message-ID: <6FAE40314DD0D4119AF200508BDE743203A6E43F@hydrus-exch.fr.eu.corp.vizzavi.net> From: =?iso-8859-1?Q?BRUNOT_S=E9bastien?= To: "'Maven Users List'" Subject: RE : "In-Place" Web Development Date: Fri, 1 Aug 2003 10:53:27 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I used to agree with that... I've been coding J2EE app for two years = now, always using this way of working, and considering two distinct = processes : 1) Code Authoring, done by the developper, using this "in-place" structuration ; 2) Module Assembling, done by the architect, using ant... But what about testing : can you set an efficient unit testing = environment with "in-place" structuration ? Wich steps are necessary to run cactus = tests for example ? Do you think your developpers will go through this steps = each time they modify code ? With maven, this is a single command operation = that build, run tests, deploy... Another point is That "in-place" structuration is impossible for your = ejb modules. Sebastien BRUNOT -----Message d'origine----- De : Dave Ford [mailto:dford@smart-soft.com]=20 Envoy=E9 : vendredi 1 ao=FBt 2003 01:17 =C0 : Maven Users Objet : "In-Place" Web Development How do people do "in-place" web development with Maven? I have been developing web apps "in-place" now for quite some time (pre-maven). By in-place, I mean the following: - My development servlet container (Resin) runs an un-jared web app - My development webapp and the executable webapp are one in the same - Jikes/IntelliJ places class files directly in WEB-INF/classes - My servlet container is setup so that it doesn't cache pages or class files so i never have to restart anything or reload the web app This is super convenient and fast. I can make changes to jsp pages and = .java files, press ctrl-F9 in IntelliJ, Alt-Tab to the browser and F5 to see = my changed web app. The time between making a change and viewing the = change is 1/4 second. I'm used to this. So now, I've set up my web app to work with Maven's war plugin and I = have lost the in-place development luxury because I have to run the = war:webapp goal every time I want to run my JSP. So, I'm considering ditching what appears to be the standard way of doing webapps with Maven. Q1: Do people actually work this way? That is, copy the entire webapp = folder every time they want to test out a small change in a jsp or class? Q2: If not, how do they organize the webapp to do in-place web = development but also. Thanks Dave Ford Smart Soft - The Developer Training Company http://www.smart-soft.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org For additional commands, e-mail: users-help@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org For additional commands, e-mail: users-help@maven.apache.org