On 7/25/06, Max Cooper <[EMAIL PROTECTED]> wrote:
Some production environments have similar issues. For example, some webapps are deployed expanded. And the new version is simply dumped in over the old version. Requesting to have files deleted during a deployment in these schemes is overhead, and error-prone. I think that is a lousy way to setup a production deployment, but I have had to live with this kind of thing on more than one occasion in my professional career. I am sure I'm not the only one.
Bingo. In theory the idea of jars with version names in them is great, and when you have 100% control of the application not a problem. This would work out great if only the rest of the java community followed suit! However, in the real world end-users of maven are faced with potentially very complex J2EE applications that have conventions or restrictions that don't fit this notion of versions in jar names. Best practices aside, sometimes we're stuck with the pile built by someone else. I will investigate some of the suggestions you kind folks have made in this thread, thanks for that. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
