This looks to me to be a case of a single project with 4 different build profiles. When you look at it that way - it's kind of odd to shove them all into a single build. Is there any reason all 4 builds must happen via one Maven call, rather than calling "mvn package" (or whatever) for each desired package? If you're using a CI server, it'd then be 4 distinct builds - which makes sense, since there are 4 distinct artifacts created.
Eric On 7/25/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi, I have a single POM file of package type "pom". I use it to generate 4 different assemblies, that's it. I have a single resource file in src/main/resources directory. It has some property name placeholders embedded in it for filtering purposes. What I need to do is copy that single resource file 4 different times to four different sub-directories of the target directory. Then each assembly picks up the appropriate file for that assembly. When I do the copy, I need to use a different set of filter values for each file (so that each assembly ends up with a slightly different configuration). I am having trouble making this happen - mostly I cannot figure out a way to use a different filter.properties type file for each copy. Any ideas? Thanks ------------------------------------------------------------------------------ Craig Dickson Software Engineering Manager Behr Process Corporation Santa Ana, California ------------------------------------------------------- The information contained in this e-mail message may be proprietary, privileged, confidential or protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this e-mail message in error, please e-mail the sender.
-- Eric Redmond http://blog.propellors.net