To clarify, my particular use case involves "finger printing" the files included in the war (via a hash), and creating a manifest (that I also want to include in the war).
On Fri, Apr 1, 2016 at 11:14 AM Ryan Dunckel <[email protected]> wrote: > There are "advanced" use cases in which a user of the war plugin wants to > perform some processing between the point in which the war content is > packaged, but before it is s archived into a .war file. In looking at the > war plugin source code, I noticed that the parts of the war building > lifecycle have been abstracted into "tasks" (e.g. a WarPackagingTask and a > WarPostPackagingTask). > > I'm wondering if it would make sense to allow plugin extensions to tap in > and provide additional tasks in order to accomplish use cases as I > mentioned above. I'm envisioning something like allowing a consumer to > provide plugin dependencies in a pom's war plugin config, for which these > plugins could implement these war tasks. > > Are there other alternative solutions? Thoughts? >
