| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | Pavel Raiskup <praiskup(at)redhat(dot)com> |
| Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Wrong link not pointing to the release tarball |
| Date: | 2016-01-22 14:05:38 |
| Message-ID: | CAB=Je-HN_yUA3KOhFSLmdQLHSGVS8VixZtOvrhGM0HYwyw1tOA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Pavel> But with
Pavel>that we are not completely sure that the particular commit ID matches
Pavel>exactly the version you released in pre-built binaries.
Technically speaking, maven creates a git tag (e.g. REL9.4.1207),
then it checks out git tree of that particular commit ID (from github!)
to a clean folder, then it builds the driver, then the results are published.
As long as we use maven, release tag will point to the commit ID
that is used for the release.
Our current *.tar.gz is closer to maven's "bin.tar.gz". In other words,
our tar.gz is for the case when all artifacts like source jar, release jar,
dependencies, etc, are required at once.
Vladimir
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Raiskup | 2016-01-22 14:17:50 | Re: Wrong link not pointing to the release tarball |
| Previous Message | Vitalii Tymchyshyn | 2016-01-22 14:03:50 | Re: Wrong link not pointing to the release tarball |