Re: WAR file versioning (Maven RC4)

[Brill Pappin]

Yes I know, but it would be a disaster in our particular case. We use 
the tomcat foo.xml for development, but deploy the war remotely via the 
manager interface. not only that but it means another point of failure 
for us with two files to maintain.

Anyway, someone mentioned using the properties file, which is the best 
solution I think and solves the problem from both ends.

- Brill
Martijn Dashorst wrote:
Brill Pappin wrote:
I don't know how others are deploying, but I definitely *do not* want 
the version appended to the war file.
The reason for this is that most containers name the context after 
the name of the war file and having a version on the end would mean 
that the context changed every time a new version was deployed.

Several webapplication containers *do* support supplying additional 
information regarding the context in which the application is deployed.
* Tomcat: supply a foo.xml for your foo-1.0.war in which you define 
the Context with as base the war file name
* JBoss: supply next to the web.xml a jboss-web.xml file with the 
context name.

These also allow for automatic configuration of the server.xml (or 
whatever configuration mechanism your server uses).

With regards,
Martijn Dashorst
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

--
"Any sufficiently advanced magic is indistinguishable from technology."
                                                 - Arthur C Anticlarke
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]