Maven is a great tool but it is not designed to build installation packages.
Would your problem be better solved using one or more installer
generation projects (in Maven) that gather and package the final set of
files that are to be used to deploy the app to the run-time environments?
I use IzPack for this.
It has a Maven plug-in that uses dependency management to grab the right
software from my repos but allows me to specify what I want to deploy to
the various run-time environments.
If you need to support different OS's or different containers, this
might be easier than trying to create a bunch of build projects
controlled with profiles.
Not sure from your description if this is the problem that you are
trying to solve but it is a recurring theme here.
Ron
On 19/10/2015 11:07 AM, Benson Margulies wrote:
Once you've run an archetype, you have a new project. And you're stuck
with it, in the sense that you have to keep it maintained.
An important question is this: what artifacts do you want to make as
part of a release? If you want a portfolio of artifacts, each for one
of your scenarios, then profiles aren't very useful, but the invoker
plugin might be.
On the other hand, if you never make releases, and you just want to
run various build with various results, then profiles can be
convenient.
The invoker is generally used for testing, and I've never tried it as
a solution to DRY-ing up a build that has to produce multiple small
variations.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
