Bug 69157 - [PATCH] textproc/saxon-devel: fix javavm issue
Summary: [PATCH] textproc/saxon-devel: fix javavm issue
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-16 16:50 UTC by Hervé Quiroz
Modified: 2004-07-17 09:20 UTC (History)
1 user (show)

See Also:


Attachments
saxon-devel-8.0_1.patch (1.44 KB, patch)
2004-07-16 16:50 UTC, Hervé Quiroz
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Hervé Quiroz 2004-07-16 16:50:23 UTC
When a JDK that is not suitable for Saxon 8.0 (version <1.4) has been installed
prior to JDK 1.4+, its entry in ${PREFIX}/etc/javavms is prior to the one of
JDK 1.4+. This means saxon will eventually get run with this JDK and thus won't
work as it requires Java 1.4+.

This patch hardcodes the choice of the Java VM by setting the JAVAVM variable
prior to running javavm.

A more flexible system is underway with the improvements of the
java/javavmwrapper that have been discussed in a couple of PRs lately.

While I'm at it, I've applied a small cosmetic change so that portlint no
longer report false warnings.

I also bumped PORTREVISION as this is a fix.

Greg Lewis is cc'ed as he suggested the fix.

Generated with FreeBSD Port Tools 0.50
Comment 1 Greg Lewis freebsd_committer freebsd_triage 2004-07-17 09:19:58 UTC
State Changed
From-To: open->closed

Committed, thanks!