0.9 test suite fails when built with jdk1.5 (was: checkout of 0.9 branch won't package)

["Heck, Gus (Patrick)" <Gu...@aspentech.com>]

It is set to a jdk... note the fact that it starts with c:\jdk... Just for fun however I did the following:

bash-4.1$ mvn -version
Apache Maven 3.0.2 (r1056850; 2011-01-08 19:58:10-0500)
Java version: 1.5.0_12, vendor: Sun Microsystems Inc.
Java home: C:\jdk1.5.0_12\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"
Picked up _JAVA_OPTIONS: -Xmx512m

bash-4.1$ export JAVA_HOME='/cygdrive/c/jdk1.6.0_18/'

bash-4.1$ mvn -version
Apache Maven 3.0.2 (r1056850; 2011-01-08 19:58:10-0500)
Java version: 1.6.0_18, vendor: Sun Microsystems Inc.
Java home: C:\jdk1.6.0_18\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"
Picked up _JAVA_OPTIONS: -Xmx512m

The \jre is just how maven reports it. However to my amazement with JDK 1.6 the package target passes. reverting to the 1.5jdk causes it to fail, so this is a JDK version compatability issue. This is great for me because I don't mind using 1.6, but might still constitute a bug?

-Gus

-----Original Message-----
From: Benson Margulies [mailto:bimargulies@gmail.com] 
Sent: Wednesday, April 20, 2011 1:03 PM
To: user@tika.apache.org
Subject: Re: checkout of 0.9 branch won't package


 C:\jdk1.5.0_12\jre

Set your JAVA_HOME to a JDK?

On Wed, Apr 20, 2011 at 10:42 AM, Heck, Gus (Patrick)
<Gu...@aspentech.com> wrote:
> Hi Folks,
>
> I didn't find anything when I searched the site/lists for
> "ForkedParserTest" wanted to check if anyone can spot something silly
> before I file a bug.
>

(snip)



This e-mail and any attachments are intended only for use by the
addressee(s) named herein and may contain legally privileged and/or
confidential information. If you are not the intended recipient of
this e-mail, you are hereby notified any dissemination,
distribution or copying of this email, and any attachments thereto,
is strictly prohibited. If you receive this email in error please
immediately notify the sender and permanently delete the original
copy and any copy of any e-mail, and any printout thereof.