From: | Mark Rotteveel <mark(at)lawinegevaar(dot)nl> |
---|---|
To: | <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Pre-processing during build |
Date: | 2015-06-16 07:08:48 |
Message-ID: | 45e4ecb7fe5cfb9bc3c61480284b810c@imap.procolix.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Morgan | 2015-06-16 13:11:47 | Re: Pre-processing during build |
Previous Message | Mark Rotteveel | 2015-06-16 06:59:04 | Re: Pre-processing during build |