From owner-freebsd-java@freebsd.org Tue May 21 21:33:06 2019 Return-Path: Delivered-To: freebsd-java@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3AF72159056E for ; Tue, 21 May 2019 21:33:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C2EB1824E2 for ; Tue, 21 May 2019 21:33:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 81C4E159056B; Tue, 21 May 2019 21:33:05 +0000 (UTC) Delivered-To: java@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F824159056A for ; Tue, 21 May 2019 21:33:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F3874824DC for ; Tue, 21 May 2019 21:33:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 470BF146EB for ; Tue, 21 May 2019 21:33:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x4LLX4ks041687 for ; Tue, 21 May 2019 21:33:04 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4LLX41B041686 for java@FreeBSD.org; Tue, 21 May 2019 21:33:04 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: java@FreeBSD.org Subject: [Bug 237054] java/openjdk11: Needs to be integrated into bsd.java.mk Date: Tue, 21 May 2019 21:33:03 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: needs-patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: tommyhp2@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: java@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 May 2019 21:33:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237054 --- Comment #6 from Tommy P --- (In reply to Greg Lewis from comment #5) Hi Greg, Without the patch, specifying any of the below would cause errors during building of various ports using Java: JAVA_VERSION=3D12 JAVA_VERSION=3D12.0 The patch conforms to previous JAVA_VERSION usage: 1.6 1.7 1.8 11.0 12.0 Using JAVA_VERSION=3D12.0 and JAVA_VENDOR=3Dopenjdk allow my systems to hav= e only 1 JDK. I haven't tried using only 12.0+ yet but the regex pattern should mat= ch and also allow future versions 11.1 or 12.1 with minor changes. Any existi= ng ports specifying JAVA_VERSION=3D1.8+ would build such as sysutils/facter (f= or sysutils/puppet6) with additional patches: *) BR 237991 - java/openjdk12 is missing java wrapper for RUN_DEPENDS in Makefile which provides various java commands in /usr/local/bin.=20 java/openjdk11 is also missing the wrapper. If JDK12 is the only java tool available, any app searching for java commands in the path would fail to execute and ports would also failed to build. Of the 3 OpenJDKs 8, 11, 12, only 8 provides the wrapper. *) BR 237990 - sysutils/facter specifies '-soucre 1.6' but JDK12 requires '-source 7' I've done some spot tests with Tomcat 9.0.20 various (Servlet, JSP, and WebSocket) examples without any issue. This is the server information repo= rted by Tomcat's manager: Tomcat Version JVM Version JVM Vendor OS Name OS Version OS Architecture Hostname IP Address Apache Tomcat/9.0.20 12+12-2 Oracle Corporation FreeBSD 11.2-RELEASE-p10 amd64 freebsd.test.domain 10.x.x.x Snippets from /usr/local/etc/rc.d/puppet* : ${puppetdb_java_home=3D"/usr/local/openjdk12"} : ${puppetserver_java_home=3D"/usr/local/openjdk12"} And puppetserver does run with default config as seen from log: 2019-05-21T13:58:53.400-07:00 INFO [async-dispatch-2] [o.e.j.s.AbstractConnector] Started ServerConnector@e3c57e4{SSL,[ssl, http/1.1]}{0.0.0.0:8140} 2019-05-21T13:58:53.401-07:00 INFO [async-dispatch-2] [o.e.j.s.Server] Sta= rted @56880ms 2019-05-21T13:58:53.415-07:00 INFO [async-dispatch-2] [p.t.s.s.status-core] Starting background monitoring of cpu usage metrics 2019-05-21T13:58:53.440-07:00 INFO [async-dispatch-2] [p.t.s.s.status-serv= ice] Registering status callback function for service 'status-service', version 1.1.0 2019-05-21T13:58:53.445-07:00 INFO [async-dispatch-2] [p.t.s.s.status-serv= ice] Registering status service HTTP API at /status 2019-05-21T13:58:53.478-07:00 INFO [async-dispatch-2] [o.e.j.s.h.ContextHandler] Started o.e.j.s.h.ContextHandler@1e55980e{/status,null,AVAILABLE} 2019-05-21T13:58:53.546-07:00 INFO [async-dispatch-2] [p.s.m.master-servic= e] Puppet Server has successfully started and is now ready to handle requests 2019-05-21T13:58:53.549-07:00 INFO [async-dispatch-2] [p.s.l.legacy-routes-service] The legacy routing service has successfully started and is now ready to handle requests 2019-05-21T13:58:53.556-07:00 INFO [async-dispatch-2] [p.s.a.analytics-service] Puppet Server Update Service has successfully sta= rted and will run in the background I'm aware of only one major issue with puppet is that I think the major cha= nges FreeBSD 12 in how the OS handles filesystem hooks breaking jruby. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233766 Because of that, I'm holding back on upgrade to 12.0 :( --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=