-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > [cut] > I do NOT use assembly, because I did NOT find it suiteable for my needs but > maybe I was missing something. > But I did not reinvent the wheel, too. I use the resources plugin and the > dependency plugin to build the complete structure of the package into > target/package/ROOT/ all with existing maven stuff. > So in src/main/resources/ROOT/usr/foo/... you dump everything you want to have > included as is. Then (in my case) there is src/main/templates/ROOT/usr/foo/... > for all filtered resources and via the dependency plugin you can copy all > reuqired jars to target/package/ROOT/usr/foo/lib/ or extract a war file to > target/package/ROOT/usr/foo/webapps/ > > But this is exactly the thing to clarify. How does this work with the assembly > plugin instead? I have evaluated the assembly plugin and now I see the point. This gives you another level of flexibility how to determine what goes into the package. I will consider this when I update the solaris plugin... > > Something that all these plugins should share in the end is a common part of > the > documentation describing how to produce the stuff into the "target" folder > and some good examples. This is still very much true.
Regards Jörg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGXz4SmPuec2Dcv/8RAgrkAKCUCiIYfks9/1vgW0oH9dxy3xTiPACdE9Ll VX5xkHoRVSDtdX4hRq7UJhY= =EamF -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
