Re: Migration to Maven

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Steven Schlansker <stevenschlansker(at)gmail(dot)com>
Cc: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, Stephen Nelson <stephen(at)eccostudio(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Migration to Maven
Date: 2015-12-01 12:13:04
Message-ID: CADK3HHLG9nF4T2Zm7HYbmot_pNkLYcqf8XgBEbqHyY6MOsbRMg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On 30 November 2015 at 16:26, Steven Schlansker <stevenschlansker(at)gmail(dot)com>
wrote:

>
> 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 :)
>
>
> Well I'm pretty sure I'll script this.

So where are we on this? Do you feel we are ready to commit this ?

Dave Cramer

davec(at)postgresintl(dot)com
www.postgresintl.com

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Stephen Nelson 2015-12-01 12:54:54 Re: Migration to Maven
Previous Message Steven Schlansker 2015-11-30 21:26:17 Re: Migration to Maven