On 04/12/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Well, it would be like other archives. By default, it would pull them from the various added sources straight into the archive - src/main/ webapp, target/generated-package-resources, for example. However, it would be sensible for the war plugin to have an option that copied all of these into target/webapp-name (in the same way as war:webapp), and then using that as the single war resource directory to package.
Yes, it'd be hard to see how war overlaying could easily work without building the exploded war first.
That's off the top of my head, not sure if it makes sense but seems consistent with how we do things elsewhere.
My only problem would be that depending on the phase process-package-resources doesn't necessarily mean the exploded archive has been built. This may be the case for the war plugin, if it's been configured that way, but as you say other packagings pull items in dynamically. I'm not sure whether this still leaves a requirement for a pre-package phase to produce the full exploded archive? Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
