Bug 69157
| Summary: | [PATCH] textproc/saxon-devel: fix javavm issue | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Hervé Quiroz <herve.quiroz> | ||||
| Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | CC: | glewis | ||||
| Priority: | Normal | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
State Changed From-To: open->closed Committed, thanks! |
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