Thread: Re: [pgjdbc] chore: migrate the build to Maven (#322)

Actually I would even like to add <classifier/> in case the build provides different editions of JARs.

Sad to read that there is another false decision of the past that we have to keep forever. :-(

The idea to prevent too much change might become major drawback some day, we should have in mind that argument, too. It might encourage people to fork some day.

-Markus

Yes, IMO changing the coords is a non-starter this would affect many
automated builds, and tools. As Stephen pointed out we already did it once
(somewhat at our peril)

I am thinking of pushing a branch we can use or we can just use Stephen's
branch for now.

PS. just got back from pgcon.... the lack of sleep and hangover(s) is
abating



Dave Cramer

On 20 June 2015 at 09:09, Stephen Nelson <notifications@github.com> wrote:

> There's a few more changes to do before it's ready to merge. I've been a
> bit busy to complete this week. If you want to create a PR against my
> branch I'll accept them so it can be finished quicker.
>
> Briefly in answer to your points:
>
> 1. The coordinates are already published on OSS so need to match. We
> already changed once a while back so it wouldn't be wise to do it again.
> 2. Agree
> 3. Agree
> 4. Build properties are within pom.xml so additional files not really
> needed now.
> 5. Agree
> 6. Agree
> 7. It needs to be confirmed as working but @davecramer
> <https://github.com/davecramer> already has a process for existing
> build.
>
> I wanted to ensure contents of jar files are exactly the same too. Also
> should we use the maven release plugin?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/pgjdbc/pgjdbc/pull/322#issuecomment-113764796>.
>

—
Reply to this email directly or view it on GitHub.