> > > You may either use the local file directly for a hot > > deployment on your developer machine or you can use > > additional plugins to process the file further. > > To give Kent an example: > > Consider a pom for building a WAR. > If you set > > <finalName>mycontextpath</finalName> > > and use e.g. the jetty plugin to start your webserver in 1 go: > > $> mvn package jetty:run > > Then your finalName is being used for 'deployment' and you may access your > webapp via > > http://localhost:8080/mycontextpath/
Well, this is all very nice... but not so practical for creating a proper context for a production environment? Also, to make things more annoying, tomcat has a tendency to ignore symlink names and picking the actual filename (pointed to by the symlink) as context ANYWAY!?! It is possible to work around this, but it seems it gets quite messy... so our best solution so far is to make sure that the actual filename matches the desired context name...
