Benjamin Bentmann wrote:
Paul Gier wrote:
I'd like to recommend that we start doing the same thing for mojo
releases
+1
but I'm not sure the best way to encourage/enforce it.
Make it as automatic as possible, e.g. by providing an appropriate
profile in the mojo-parent and activate that via the Release Plugin's
releaseProfiles parameter.
What's the best way to make it automatic but still overridable? Since a lot of
projects might have one or two files/directories that don't match the default
setup? If we create an assembly plugin config in the parent, could that be
overridden by an assembly config that uses the same execution id?
IMO it's enough to just include the .zip file, and make other formats
(tar.gz, bz2, etc) optional.
Sounds fine to a Windows user, let's see how many *nix users scream ;-)
Zip/unzip come standard with all the major linux distros, AFAIK. But if it's an
issue for anyone, I'm fine with including tar.gz as well.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
