Arlo,
Agree with the sentiment that requiring everyone to come up with their
own pom.xml's to do overrides is not optimal, that Maven can be slow in
larger projects, that it isn't as straightforward as Ant when it comes
to customized/non-standard build tasks and scripting.
But the following is incorrect: "There's no way to run special ant
commands or executables."
See: http://maven.apache.org/guides/mini/guide-using-ant.html
You can use Ant from Maven 2 to call Ant tasks, etc. so you could have
Maven use an Ant task to only copy the files that you want it to update.
Many would suggest against making file changes to an exploded war,
though. If you don't mind rebuilding the entire artifact (and possibly
redeploying via wagon or called ant task, etc.) and you want simplified,
consistent build definitions that promote dependency management, it
works well. If you do make changes to the exploded war and only want
certain files copied over into the exploded war directory, then maybe
some combination of source control and rsync, filer, Ant (scp, etc.),
Maven calling Ant, and/or maybe even a push CMS (shudder!) might help.
HTH,
Gary
On 6/30/10 1:33 PM, Arlo White wrote:
There's no way to run special ant
commands or executables.
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
