A more "maveny" way IMHO would have a project for each thing you are trying to build. That would include the base, each client and each assembly.To buld an assembly you go to its project folder and type:
mvn assembly:assembly This goes against our built-in lazyness where we want to have as few folders full of stuff as possible. But it works well and organizes things well. -- Lee On 11/17/06, flyboy <[EMAIL PROTECTED]> wrote:
Here is a question about maven assembly. Maybe it is a best practice question. Say there is a Base project that provides common services. Then there are multiple projects (Client-1, Client-2,...) which use the common service. Say I want to build assemblies which include the Base and various different permutations of Clients. Example: Assembly-1 contains Base, Client-1, Client-3. Assembly-2 contains Base, Client-3, Client-4. Assembly-3 contains Base, Client-1, Client-2, Client-4. and on and on.... All clients depend on Base. Each assemlbly would contain 1 or more clients. I think I will create an seperate project, AssemblyProy. The pom would describe all clients as dependencies. The pom would parameterize the assembly descriptor and the assembly name. Each descriptor would represent a diffeferent combintation of Clients. To build an assembly, would run: mvn -Passembly=Assembly-1 assemble Is this THE WAY in maven? If not, what is? If there currently isn't a WAY, is the above reasonable? Are there alternatives? Thanks, John -- View this message in context: http://www.nabble.com/assembly-permutations-tf2655047s177.html#a7406601 Sent from the Maven - Users mailing list archive at Nabble.com.
-- -- Lee Meador Sent from gmail. My real email address is lee AT leemeador.com
