-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi there,
in "Re: [mojo-dev] No interest in RPM, Deb, Sys-V, Yum?"
we have talked about the common tasks for creating deployment packages
independent from the actual type of the packaging.
After thinking about it, I still have the oppinion that an
AbstractDeploymentPackageMojo would make sense:
It could offer a method like:
public FileInfo getFileInfo(String rootPath, boolean directory)
where FileInfo (or however the object could be named) contains
the user (String), group (String), file-/directory-permissions (structured or
bit-mask as int).
So getFileInfo("/usr/local", true) could return a FileInfo
representing "root:stuff drwxrwsr-x" or whatever.
The AbstractDeploymentPackageMojo would handle all the logic to
configure the user, group, file-/directory-permissions
via simple defaults and maybe adanced rules using regexp patterns.
As a first try, I could write such an AbstractDeploymentPackageMojo
within solaris-maven-plugin and derive the actual Mojo there from it.
Others could review this and consider wether we should extract
the AbstractDeploymentPackageMojo into a seperate module and derive
other packaging plugins from it.
This would make it easier to switch the package-format or even to create
packages in differnet formats from the same module. Further the
logic to configure the ACL stuff would only need to be written once and
all derived plugins could easily take advantage from improvements.
Comments and concerns are very welcome.
Regards
Jörg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGI9RKmPuec2Dcv/8RAmPkAJ4oCK5TyFqbX5LjYdyFBTMhgCL1uACdFUUD
YxxBhDw9gB7NBmSgCEvrE1M=
=TFn9
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
