On Wed, 22 May 2002 [EMAIL PROTECTED] wrote:

> 
> Not a bad idea.
> 
> I'm +1 on making war/ear names fall into line with jar naming conventions,
> but -1 on having this in the project descriptor - no other deliverables are
> at this point, and I'd rather be consistent.

Well, I can accept defaulting the name of the webapp to the name of the 
project - that's pretty logical.  

However, you can't include a version number in the resulting war file
name.  Most webapp containers rely on the war file name being the correct
default name of the application.  Do you really want to stick a version
number in there? :)

I'd like to leave the ability to specify what the name of the webapp is 
based on the maven.j2ee.webapp.name (or whatever it is) property, and the 
current directory structure.  Anything else makes it difficult to create 
multiple webapps out of a single code base.

Glenn McAllister
SOMA Networks, Inc.



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to