[
http://jira.codehaus.org/browse/MOJO-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125589
]
deckrider commented on MOJO-1049:
---------------------------------
Hi,
We use pkg-get from blastwave, continuum, archiva, and the maven release
plugin. So the main issue addressed by gzipping the package is to conserve
space within archiva (and most solaris packages I see available on the net are
gzipped).
We have applied the last patch and are using this patched version of your
plugin internally (it gives no choice but to gzip).
Thus, our build gzips and uploads to archiva. Then, we have several versions
of URLs given to /opt/csw/etc/pkg-get.conf (developoment, test, user
acceptance, production). A small script is run to stage an archiva package to
any of these environments (just a 'ln -s' to the original in archiva,
conformant to the name pkg-get wants, followed by a corresponding update to the
catalog).
Our builds have no makefiles, only pom.xml. And I'm not a blastwave
maintainer, we are just using their system (I see none better out there to work
with Solaris 10).
Thanks.
> option for solaris maven plugin to generate *.pkg.gz
> -----------------------------------------------------
>
> Key: MOJO-1049
> URL: http://jira.codehaus.org/browse/MOJO-1049
> Project: Mojo
> Issue Type: New Feature
> Components: solaris
> Environment: solaris
> Reporter: deckrider
> Attachments: jira-1047-1048-1049-v2.txt, jira-1047-1048-1049-v3.txt,
> jira-1047-1048-1049.txt
>
>
> I would like to request that the solaris maven plugin can have an option to
> gzip the resulting pkg.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
