It's just an arbitrary limitation in that plugin, that does at least cover some of the usage cases.Hello Maven Friends, So, I am in quite a quandary... It seems like Maven and other apps (like XDoclet) do not support (without a bit of hacking) multiple war files. I am very curious as to why this is. Should I only have 1 war file per project? That doesn't seem right, so why are multiple war files per project not better supported? When should I use multiple war files and when shouldn't I?
Thanks for you input.
Persoanlly, I have a number of projects that produce multiple war files (for example, a small web-app that is used to kick-start startup services in a j2ee app, alongside with something like the main web site and/or an admin site.
As others have suggested, you can have a separate project for each war file, but given that each war is coming from the same sources, this is not necessarilly too optimal in terms of a fast and easy code/build/debug cycle. You have to switch among projects or start using the reactor.
btw, if you use xdoclet raw, as opposed to the plugin, you should be able to handle multiple WARs I think. I haven't done it with wars, but certainly have with EJBs, where the same limitation exists with using the xdoclet plugin, but not xdoclet itself...
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
