What about having a maven project for each platform using the same
parent pom, rather than architecting the solution on profiles?
/Johan
6 jun 2008 kl. 09.47 "Timothy Reilly" <[EMAIL PROTECTED]> skrev:
I wanted to see if others have addressed this requirement before and
what approaches they have taken:
We have certain artifacts which need to be built for multiple
platforms.
For example, we may have j2ee artifacts that get deployed to
Websphere 6
and Websphere 6.1. We use profiles to setup the right build properties
for each and the resulting artifact has a qualifer like MyTime-1.0-
WAS60
or MyTime-1.0-WAS61. The next thing we want to start doing is
automating
the build process for these multi platform builds.
I think we have a few options for this,
1) maven is executed currently by a provisioning tool which currently
pulls from our scm(1), kicks off maven and installs the artifacts to
the
appropriate application server(s). The tool has some workflow
capabilities so we could just build a workflow around the build
request
process and let this tool run maven the required number of times.
2) I think it would be a lot better if we declaratively provided this
information to maven in a pom file. To do this we could create a new
project aggregator pom. This new project's purpose would be to run
multiple invocations of the build using perhaps maven invoker plugin.
This seems pretty straight forward but the only problem is that we
would
need to incorporate this new project into the build process and
perhaps
make sure every project (a hundred plus) has one of these so called
"here's what and how many times to build" projects.
3) Finally, what I think is the best but harder to implement is to
somehow use the existing project's parent pom and configure it to run
the required number of builds with the various profiles activated.
This
would probably be some sort of plugin, plus custom lifecycle and
extension. Has anyone done this?
What other ways are people address something like this? Is there a
"maven way" to handle it?
Any feedback appreciated.
(1) Our scm has no maven scm provider so we need the other tools help
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
