Re: Pre-processing during build

Well, we actually opened this discussion because we WANT particularly Maven and we DO NOT want the flexibility of ANT but follow CoC, hence make PGJDBC at-most a simple, "standard" project with as less as possible customizations... The less flexibility you have the more standards you follow the easier new programmer's can get at speed with the project. More flexiblity = more complexity = more customization = longer time to get about = less new programmers will join. That's the idea behind this thread, actually.

-----Original Message-----
From: pgsql-jdbc-owner(at)postgresql(dot)org [mailto:pgsql-jdbc-owner(at)postgresql(dot)org] On Behalf Of Mark Rotteveel
Sent: Dienstag, 16. Juni 2015 09:09
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [JDBC] Pre-processing during build

On Mon, 15 Jun 2015 18:42:13 -0400, Sehrope Sarkuni <sehrope(at)jackdb(dot)com>
wrote:
> I think a purely Maven based build with separate targets should be
possible
> via a generated-sources plugin. Off the top of my head I'm not sure
which
> plugins it would use though. It's been a while since I wrote anything
like
> that though I do remember it being a bit of a pain to get right. On the
> plus side we only have to figure it out once right? :)

My experience is that Ant gives you a lot more flexibility. For Jaybird I
considered moving to a Maven based build, but I finally decided against it
because it was too much hassle. The difference with the PostgreSQL JDBC is
that Jaybird uses JDBC version specific sources-folders with common classes
(and abstract classes for common implementation).

> I'm a big fan of Mavenizing the build process. A lot of the value of it
> will come from how it will simplify things like adding tests. It
eliminates
> a lot of the double and sometimes triple entry (i.e. add the test class,
> add it to a suite, add the suite to build.xml).

You don't need Maven to achieve that. For one you don't need testsuites,
with JUnit 3 it is a bit harder, but you could use a consistent naming
convention and filter tests in the Ant plugin, with JUnit 4 you could use
(class or instance) rules, or filtering based on annotations.

Mark

--
Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc