I'm doing some research on migrating to Maven from our ant project structure, or just adding Ivy. The problem comes that I've never seen a project in Maven such as ours. We have a product for <10 clients, with a potential client base of about 20. Unfortunately, while it uses a base API, each project is highly customized. Currently, our (simplified) project structure looks like this.
/ /client /client/a /client/a/html /client/a/java /client/a/properties /client/a/sql /client/b ... /html /java /properties /sql (Close enough, anyway.) Now, in the build process, information from the base html, java, properties, and sql is used to build the base structure. (Ignore sql for now) We then compile the client java into the same target directory, and overlay the properties and html directories *over* the core files. Yes, this is not the best idea. No, it can't be changed. (Immediately, anyway.) How much pain are we talking about? We're trying to make this more modular, but the UI will initially still be a complete entity. I see how to incorporate the multiple jars in the project, but how do you fit this into the single artifact system? (Do you just have to zip/unzip or use ant tasks?)
