-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Trygve, hi everybody,
I started to get into unix-maven-plugin. So far I like the general configuration of common package meta-data and your excellent documentation how this is mapped down according to the actual format. However currently the site has various dead links: http://mojo.codehaus.org/unix/unix-maven-plugin/usage.html http://mojo.codehaus.org/unix/unix-handbook/handbook http://mojo.codehaus.org/unix/unix-maven-plugin/unix-maven-plugin/plugin-info.html http://mojo.codehaus.org/unix/unix-maven-plugin/developers/ For the meta-data I would like to work on adding dependencies. Here I am NOT talking about maven deps but about dependencies of the generated package. Further what I want to understand is, why you added all this <copyArtifact> and <extractArtifact> in <assembly>? We already had the "re-invent-the-wheel" discussion about things like this when talking about the philosophy of solaris-maven-plugin. I mean there is maven-dependency-plugin, maven-resource-plugin and filtering and all what maven already offers. Why not just let the user build the package content with all features of maven to build.outputDirectory and then build a package from that. Sure you will still need support for symlinks and permissions. What was your motivation to go a different way? Or am I just missing something? Did you have a look at pkg-maven-plugin. It is just raw minimum but it should just show how simple you can make maven to build packages with all your custom needs. Should I also add an example project or is it self-explanatory. Regards Jörg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpBPKwACgkQmPuec2Dcv/9j1QCeOr6Babvmg5DyuKogf+hdQ3oK CsMAn2OFdvz+WI9n8fRJ7C5fSaadZEMY =G524 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
