On Tue, 28 Mar 2006, Kris Jurka wrote:

>
>
> On Mon, 27 Mar 2006, Tom Lane wrote:
>
>> BTW, one Red Hatter had this to say:
>>
>>> Yeah, AFAIAC this is a bug in ant. Really, the build file should be using
>>> ${java.version} instead of ${ant.java.version} to avoid this problem,
>>> IMHO.
>>> I ran into a similar issue with the Eclipse SDK.
>>
>
> The difference is that java.version will return things like 1.4.2_08 instead
> of just 1.4, so they are not equivalent. ant doesn't offer a lot of tools to
> parse such a string, the best you could do would be a global substring match.
> Trying to find 1.4 would match 1.1.4 as well as 1.4.2 though. Since we don't
> support 1.1 builds we could do this, but it seems a little fragile with
> perhaps other vendors using different format strings. The best solution for
> older ant users might be to duplicate the checks ant makes for
> ant.java.version in our own build file. That way we can put in the latest
> updates and not require an upgrade.

How about java.specification.version? AFAIK, it should do just what we
need.

- Heikki

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

On Thu, 30 Mar 2006, Heikki Linnakangas wrote:

> How about java.specification.version? AFAIK, it should do just what we
> need.
>

Indeed it does, I've put this into our build.xml along with an explicit
failure message when someone tries a JDK1.6 compile.

Kris Jurka

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

I am also really excited about GCJ/Classpath support, since this would
allow users to use postgres from java applications without relying on
proprietary software.

Just because of interrest, has anybody successfully used the jdbc
driver with gnu-classpath based JVMs?

Thanks, lg Clemens

2006/4/29, Kris Jurka <books@ejurka.com>:
>
>
> On Thu, 30 Mar 2006, Heikki Linnakangas wrote:
>
> > How about java.specification.version? AFAIK, it should do just what we
> > need.
> >
>
> Indeed it does, I've put this into our build.xml along with an explicit
> failure message when someone tries a JDK1.6 compile.
>
> Kris Jurka
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly