-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Aug 23, 2005, at 11:41, Jamie Bisotti wrote:
Thanks for your response. Sorry, I didn't ask my question clearly
enough. I understand what it is doing and that it is doing things per
the documentation. I guess my real question is why does
'maven.war.final.name' not default to
${pom.artifactId}-${pom.version}.war? This seems to go against "the
Maven way".
As I'm typing this, it seems like maybe this came up on the list
recently; however, a quick search didn't find it. If so, and this has
already been addressed, a pointer to the thread would be greatly
appreciated.
I don't remember this coming up recently, but I'm pretty sure it's come
up before. I know the answer to this, which means that I got the answer
from someone smarter than me. :-)
Some servlet containers (like Tomcat 5, maybe?) deploy a webapp to a
URL that's a function of the warfile name. (For instance, "myapp.war"
might be deployed to "http://www.example.com/myapp";.) If the warfile
name changes, the URL changes -- and that's probably undesired
behavior.
- --
Craig S. Cottingham
[EMAIL PROTECTED]
OpenPGP key available from:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7977F79C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFDC1YrEJLQ3Hl395wRAkRdAJ4x9zlR3SNHO8x9g4UqB3lccWJFGwCeP+bQ
YfwMjiJsOmZY8Gi1/esj268=
=MYc6
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
