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.
We do version our wars however... we added the version to the web.xml in the description element so that we can see what version of a webapp we have deployed. I've been thinking about using the old ant "Filter" task to update it automatically fro the maven version, but haven't added the preGoal yet.
- Brill Pappin
[EMAIL PROTECTED] wrote:
Hi,
I just used the war plugin, it seems that it does not attach a version to the generated war file. I am using Maven RC4.
I'd expect that a testapp-1.0.war would be generated in the target directory, I only get a testapp.war
I reproduced it quite easily:
1) generate a new application with maven genapp 2) invoke "maven war"
You get an unversioned war file.
Anyone else seen this ?
br, /Sverre
--------------------------------------------------------------------- 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]
