Please test the 'current' jdk 1.5 patchset

[Jung-uk Kim]

On Tuesday 05 June 2007 02:25 am, Greg Lewis wrote:
> All,
>
> If you're not afraid to build the JDK from scratch without using
> the jdk15 port, please try the "current" JDK 1.5 patchset (see
> http://www.eyesbeyond.com/freebsddom/java/jdk15.html).  This is
> based on the 1.5.0 Update 11 JRL source rather than the 1.5.0 SCSL
> source.
>
> Unless I get some showstopper reports I plan to release this as
> patchset 5 within the next few days.  Note that I don't believe
> this will fix the problems on -CURRENT/i386 some are seeing and the
> raw patchset itself will have problems if you don't have the
> /usr/X11R6 symlink (this shouldn't be the case for the updated
> jdk15 port though).
>
> I haven't yet completed the update for the jdk15 port, which is why
> you'll have to build it from scratch ;).  I am working on an update
> though, so one will be available before the release of the
> patchset.
>
> I realise that Update 12 was just released, but I think its worth
> getting the newer patchset out now and switch to Update 12
> afterwards rather than stopping the release cycle at this point.
>
> If the build is successful you should see something like this:
> > /usr/local/jdk1.5.0/bin/java -version
>
> java version "1.5.0_11-p5"
> Java(TM) 2 Runtime Environment, Standard Edition (build
> 1.5.0_11-p5-glewis_03_jun_2007_19_01) Java HotSpot(TM) 64-Bit
> Server VM (build 1.5.0_11-p5-glewis_03_jun_2007_19_01, mixed mode)
>
> (Server VM being the default on amd64)

I have successfully built it and it seems working fine:

%java -version
java version "1.5.0_11-p5"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-p5-jkim_05_jun_2007_13_06)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_11-p5-jkim_05_jun_2007_13_06, mixed mode)
%sysctl kern.osreldate
kern.osreldate: 700043

I know -CURRENT is unsupported, so I used my patches from
ports/java/jdk15/files.  I also had to disable plugin support but
then I decided to make patches to pacify the errors instead.
Keep in mind that plugin does/will *not* work on amd64, so please
don't bother. ;-)

Thanks!

Jung-uk Kim