title: How should I get Maven to deploy artifacts for all supported architectures at the same time?
body: <p>I have a question that's probably pretty similar to <a href="https://stackoverflow.com/questions/5162009/building-artifacts-for-multiple-java-architectures-using-maven-anything-better-t">this</a>.  I need to solve what I have to imagine to be a pretty common problem -- how to configure Maven to produce multiple variations on the same artifact -- but I have yet to find a good solution.</p>
  
  <p>I have a multi-module project, that eventually results in the <code>assembly</code> plugin generating an artifact.  However, part of the assembly includes libraries that have changed substantially in the recent past, with the result that some consumers of the project need library version N, while others need version N+1.  Ideally, we'd just automatically generate multiple artifacts, e.g. <code>theproject-1.2.3.thelib-1.0.tar.gz</code>, <code>theproject-1.2.3.thelib-1.1.tar.gz</code>, etc. (where that's release 1.2.3 of our project, running against either library version 1.0 or 1.1).</p>
  
  <p>Right now, I have a bunch of default properties, which build against the latest version of the library in question, plus a profile to build against the older version.  I can deploy one or the other this way, but cannot deploy both in one build.  Here's the key wrinkle that differs from the above question: I can't automate build-one-clean-build-the-other <em>inside</em> of the <code>release</code> plugin.</p>
  
  <p>Normally, we'd <code>mvn release:prepare release:perform</code> from the root of the multi-module project to take care of deploying everything to our internal Nexus.  However, in that case, we have to pick one -- either run the old-library profile, or run without and get the new one.  I need the release plugin to deploy <em>both</em>.  Is this just impossible?  I have to imagine we're not the first people who want to have our automated builds generate support for different platforms....</p>