I know this could be a huge topic, but I have to start somewhere and I suspect that this issue is common for maven users.
We've successfully migrated a project from Ant to Maven. In the process we've broken a large application into 5 components. Currently we deploy and install the entire thing as one entity using InstallShield. All the jar files go under one application directory. Upgrading to the next release means creating another application directory and adjusting a symbolic link to point to it. In the past if we needed to make a patch we'd create (by hand) a patch.jar that had the changes and placed it at the front of the classpath. I'd like to get away from this. Instead I'd like to just release a new version of the changed component. The question is how should my production environment be setup to make this easy/possible? Thanks, Christopher The information contained in this e-mail is confidential. This e-mail is intended only for the stated addressee. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. if you have received this e-mail in error, please inform us immediately and delete it and all copies from your system. EBS Dealing Resources International Limited. Registered address: 10 Paternoster Square, London EC4M 7DY, United Kingdom. Registered number 2669861. EBS Dealing Resources, Inc, registered in Delaware. Address: 535 Madison Avenue, 24th Floor, New York, NY 10022, USA, and One upper Pond road, Building F - Floor 3, Parsippany, NJ 07054, USA. EBS Dealing Resources Japan Limited, a Japanese Corporation. Address: Asteer Kayabacho Bldg, 6th Floor, 1-6-1, Shinkawa, Chuo-Ku, Tokyo 104-0033, Japan.
