We're developing a large scale Struts app along with a subcontractor. While the subcontractor produces a lot of "library code" in the form of common components, they are also developing some web modules. As the developer here with the best Ant background, it's falling into my lap to unite the modules into a single application.
All of the modules must share a single login, and in some cases must share the same session for communication between them. Currently they exist in separate CVS modules, with separate Ant scripts, DB config, and other config files. I believe in the end they must deploy to the same .WAR file, and I suspect it's not going to be trivial in the least to merge them into a single application. Has anyone out there dealt with a similar scenario and could give me some advice? This might be more of an Ant question, but is relevant here as well. I'm mainly looking for high level advice, or suggestions in general, but here's a few of the questions I have off the top of my head: 1. Each company currently has their own web.xml - how to merge these in hopefully in an automated manner 2. Is there a limit to the number of struts modules an application can have? Any repurcusions for having many (dozens?) of struts modules? 3. Best practices for structuring both the individual projects and the final product 4. How to integrate? Let Ant sort it out? Try to convince them to merge into a single repository and directory structure? Build a common structure for each build and then build that with Ant? Thanks in advance for advice, hopefully someone out there has had to endure this before and can at least give me some mistakes not to make =) Chip Paul Sr Software Engineer ComFrame Software Corporation Listen.Understand.Innovate www.comframe.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
