I have a project where there are 5 levels of projects (maven modules each) in a pom hierarchy:
CommonLibrary.jar -> CommonMvc.jar -> ProductAndService.war -> ProjectCore.war -> ProjectSpecific_1.war The idea is that the later war file configuration files currently replace the earlier ones where they conflict. The result of all of this is one war with all of the files unbundled and re-bundled in order along the chain. Right now I am using the AppFuse's warpath plugin to accomplish this, but there are problems. Netbeans handles it best, but it fails to recognize compilation paths at times. It sometimes fails to recognize Java file changes, but in somewhat of a predictable manner. There is a big chance this build method may breakdown with 3.0 Maven even worse. What I am asking is, what do you suggest? How do people handle such complex web project compiles where there are commonly replaced configuration files and web oriented files? What do you consider to be a best method if this will not work? What way do you suggest will work with Netbeans effectively? Looking for suggestions. I am willing to make changes to the project structure to make it work, but hoping to be able to keep the modules separate as I am seeking as much reuse between the tiers as possible. For instance I compile one final build with different features for USA vs another for China. Thank you for any help. The more detail the better. JohnE ----- John Eichelsdorfer http://jobbank.com/ jobbank.com -- View this message in context: http://old.nabble.com/Multi-war-complex-build-recommendation-request-tp26347866p26347866.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
