From: | Steven Schlansker <stevenschlansker(at)gmail(dot)com> |
---|---|
To: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
Cc: | Stephen Nelson <stephen(at)eccostudio(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Migration to Maven |
Date: | 2015-11-30 21:26:17 |
Message-ID: | B1D1BEFA-BD8F-4A6C-ACC3-FA58931DA51E@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Nov 30, 2015, at 1:18 PM, Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> wrote:
>
> maven-toolchains-plugin allows to specify per-module JDK version, so
> you just mvn and it uses the proper JDK.
> I did not figure proper travis configuration yet, however I think it
> should not be hard.
>
Here is an example of how we did it in another project, in case that is helpful:
https://github.com/jdbi/jdbi/pull/169/files
> It boils down the release procedure to:
> Release for jre8
> 1) mvn release:clean release:prepare, enter, enter, enter
> 2) mvn release:perform
>
> Release for jre7
> 3) cd core-jre7; mvn release:clean release:prepare, enter, type <next
> version>; enter, enter
> 4) mvn release:perform
>
> Release for jre6
> 3) cd core-jre6; mvn release:clean release:prepare, enter, type <next
> version>; enter, enter
> 4) mvn release:perform
It would be nice for this to be one step, if possible... just wait until someone
does a typo on one of the versions :)
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2015-12-01 12:13:04 | Re: Migration to Maven |
Previous Message | Vladimir Sitnikov | 2015-11-30 21:18:27 | Re: Migration to Maven |