2010/12/7 fhomasp <[email protected]>: > That does make sense. So I'd create a release module that has a client > application as dependency, that's what you mean?
Exactly. > So one release module for > one application. Kind of like an ear packaging a war, in a broad analogy > then? Very broad, since EAR has its own package type. > In the super pom bundling the modules I then add these modules to the > modulelist? Or only in a seperate profile meant for the release? Add new modules to the module list. This approach proved to be the best in the long term, especially if you have a very complicated list of dependencies to include in the assembly. Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
