I'd try this last approach, using the "dir" format for the first pass to
sort of stage out the assembly to a directory structure. From there, you can
work on the assembly directory using a custom plugin, then take a second
pass of the assembly plugin to simply archive the staged directory into a
zi
Or, bind the assembly plugin to two different phases with different assembly
descriptors.
On 10/2/07, Kalle Korhonen <[EMAIL PROTECTED]> wrote:
>
> I doubt so. Use some other plugin (like the dependency plugin) to copy the
> resources, modify as you like with other plugins, then use filesets to
>
I doubt so. Use some other plugin (like the dependency plugin) to copy the
resources, modify as you like with other plugins, then use filesets to
assembly the modified files together.
Kalle
On 10/2/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> is there a way to modify the assembly
Hi
In theory, being maven2 plugin a program written in java or ant script you
can do whatever you want with it.
Here's a reference that I believe it might be useful to write and build
plugins:
http://www.devzuz.com/web/guest/products/resources#BBWM
bye
On 10/2/07, [EMAIL PROTECTED] <[EMAIL P
Hi,
is there a way to modify the assembly (e.g. with a custom plugin) after it
created the assembly directory structure and before it creates the
tar/jar/zip file? My plugin would for example modify some files within the
assembly folder before the archive is created.
Thanks for any help,
Armin
