maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Matic Langford" <>
Subject RE: RE : "In-Place" Web Development
Date Fri, 01 Aug 2003 10:13:43 GMT
what if you're not using ejb?

The information contained in this e-mail is intended only for the person
entity to which it is addressed and may contain confidential and/or
privileged material. If You are not the intended recipient of this
the use of this information or any disclosure, copying or distribution
Prohibited and may be unlawful. If you received this in error, please
contact the sender and delete the material from any computer. The views
expressed in this e-mail may not necessarily be the views of The PCMS
plc and should not be taken as authority to carry out any instruction

> -----Original Message-----
> From: BRUNOT Sébastien [] 
> Sent: 01 August 2003 09:53
> To: 'Maven Users List'
> Subject: RE : "In-Place" Web Development
> 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 [] 
> Envoyé : vendredi 1 août 2003 01:17
> À : 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
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message