On Tue, Jun 22, 2010 at 12:00 PM, D D <[email protected]> wrote: > I'm converting projects from M1 to M2. Due to restrictions imposed from > "above" - I'm not allowed to change anything - including names of artifacts. > In M1 implementation the artifacts did not contain versions in their names. > > At this point I have over 100 artifacts that will be ftp-ed to an > application server where those will be picked up and deployed. Actual > deployment process is out of my hands - changing names of artifacts could in > theory break something on a server side.
What are you calling 'deployment' here? The term is unfortunately overloaded when discussing Maven builds. It sounds like the requirement is only that the filenames be preserved when the files land on the application server. How does the FTP happen now (in M1)? Is it part of the build for each artifact or do you gather up several things and FTP them in a group? How about... deploy 'as usual' to the Maven repo, then have a second process that does the FTP (renaming them at that time.) Again one or more of the goals in the Dependency plugin might be useful to collect the things that need to be FTP'd over. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
