Aleksey Didik <didik <at> magenta-technology.ru> writes: > Using separate module for EAR is the most useful solution. > This module is description of "what must be in the ear". > Use <packaging>ear</packaging>, <modules> section in the <configuration> > and, attention, don't forget add dependency to project-web artifact to > <dependencies> section.
Thanks Aleksey. Can I directly combine this with a parent POM? From another thread I got a parent POM is helpful in general for centralizing dependency management. I already have multiple projects for the JARs of the webapp. (I overtook the application, but only the source code, not the build files.) So can I use the parent POM for also specifying the content of the EAR as you described above? Joerg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
