Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jtWxp-0002yn-7E for pljava-dev@arkaria.postgresql.org; Thu, 09 Jul 2020 13:51:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jtWxn-0006XF-Th for pljava-dev@arkaria.postgresql.org; Thu, 09 Jul 2020 13:51:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jtWxn-0006X8-Mh for pljava-dev@lists.postgresql.org; Thu, 09 Jul 2020 13:51:47 +0000 Received: from mail-ej1-x629.google.com ([2a00:1450:4864:20::629]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jtWxl-0003SZ-6y for pljava-dev@lists.postgresql.org; Thu, 09 Jul 2020 13:51:46 +0000 Received: by mail-ej1-x629.google.com with SMTP id a1so2306968ejg.12 for ; Thu, 09 Jul 2020 06:51:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=izxhc4Z5uR+T6B9/KSLb6uVF/dLXBVFRkCa52T5L4vs=; b=oOpLyrDDLWMnX0R4IDJAp/mwOOCxlpQ7zzlSV+W6s8DK/S36hkrN569d8hJpoFZsyi fgJvXnS1nYvtj3kPK/tMrWZpCXNxqaOV4PuRHBSdqStFTbjoiG0frtdsIM7xOKsQ5Cwy nty78LTedDc+t0tb4zcfP+uTOn9V+Jeq9vgsAFgSL/bSryp/9vu3llrfdc58VPQUmXmC WP+H4McBxrofbMiOkPxyOV0Ymi+ux06Tl+SbFrBMthst6vUCYN4M+VLJAfPcTYf5fHXg SKN7mokmp2hsHVD+YUIEydvg0a5142Cg4dsc8CGYGJ5CsTF4XjR7aqG8wWetoAGdX9Lr KT7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=izxhc4Z5uR+T6B9/KSLb6uVF/dLXBVFRkCa52T5L4vs=; b=Aj5VebcEeWZy/scX7VYM1MpPYyG8rxgwAFUQswUN2Jjo2K8R6IyYC7Bs0FQbWo0Oau KzUUkIASzSTloauinQtUvU9lI+pgrXnL/IIsJVY7AGQWsGK64b0VD9EWiTIQGtvtjdnI /3F4NZNVC6ARW6ueILvynuYX1d7mVct/yaNOuX0CSUbuehqrBmERCuMpunvM8O1UyWBy w5n7N4unyK6qzd8wgpMPeg1Rsg4Fi9JwDGbPR5INhtcA55YkCwDAZZLILKKrqFN3R1BY hWTGaj6Vt2mVrFHbE8pgDu8NRbA4gfpb+zl7zeK7ruEc3Hp3PaIRLXIoJj3NgwraHkeL gO5w== X-Gm-Message-State: AOAM532ge13n040RznGLZ9px7yEPMuWJcY/Db5tYHAp+JxJ2NMpWEEoY 6+TbnHkh20NFk9avzPq+g+XvvC7/le032xggMR0a6IAs X-Google-Smtp-Source: ABdhPJzXg4tRP2dlG/rI4TZTioHcUY7hgC175iJC2bI+l7xI7WXxUWq6qN+480QmOmNA8Uvz/Lxn5GcGw4OkxV2oYzE= X-Received: by 2002:a17:906:594c:: with SMTP id g12mr56176915ejr.255.1594302702615; Thu, 09 Jul 2020 06:51:42 -0700 (PDT) MIME-Version: 1.0 References: <5EFE0A4D.8060402@anastigmatix.net> <5F0125BC.5000609@anastigmatix.net> <5F0172D7.3000708@anastigmatix.net> <5F02122C.7040905@anastigmatix.net> <5F021785.905@anastigmatix.net> <5F021A20.1050903@anastigmatix.net> <5F02340C.7030002@anastigmatix.net> <5F04FA65.5000600@anastigmatix.net> <5F071CFC.9090306@anastigmatix.net> In-Reply-To: <5F071CFC.9090306@anastigmatix.net> From: Kartik Ohri Date: Thu, 9 Jul 2020 19:21:31 +0530 Message-ID: Subject: Re: PL/Java new build plugin To: Chapman Flack Cc: pljava-dev@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000041007e05aa02868b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --00000000000041007e05aa02868b Content-Type: text/plain; charset="UTF-8" > > Odd ... were these two builds started with different command lines? > > The first one looks like it builds all subprojects: > > [INFO] Reactor Build Order: > [INFO] > [INFO] PostgreSQL PL/Java > [INFO] PL/Java API > [INFO] PL/Java backend Java code > [INFO] PL/Java backend native code > [INFO] PL/Java Ant tasks > [INFO] PL/Java examples > [INFO] PL/Java packaging > > The second one seems to skip right to pljava-so: > > [INFO] Reactor Build Order: > [INFO] > [INFO] PL/Java backend native code > [INFO] PL/Java Ant tasks > [INFO] PL/Java examples > [INFO] PL/Java packaging > Yes, when the second build failed. I ran mvn install -rf :pljava-so -X -e. In nar-maven-plugin 3.2.3, the line with the null pointer exception > seems to be this one: > > > https://github.com/maven-nar/nar-maven-plugin/blob/nar-maven-plugin-3.2.3/src/main/java/com/github/maven_nar/Compiler.java#L499 > > which makes me think that some entry of 'defines' is a null. > Any suggestions what could be the problem? As far as I see in the build.xml, I can only think of MSVC.RINT but it should not be probably the cause. > If you're running the build with Java 14 or later, you may be able > to squeeze a little more information out of a NullPointerException > by putting the right -XX:... option in the MAVEN_OPTS environment > variable (see [1]). In this case it might only say something like > "cannot call method split() because receiver is null" (I don't see > a lot of other possibilities on that line) but in general it might > be helpful. > Yes, I understand that but as you say it isn't beneficial in this case. --00000000000041007e05aa02868b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Odd ... were these two builds started with different com= mand lines?

The first one looks like it builds all subprojects:

[INFO] Reactor Build Order:
[INFO]
[INFO] PostgreSQL PL/Java
[INFO] PL/Java API
[INFO] PL/Java backend Java code
[INFO] PL/Java backend native code
[INFO] PL/Java Ant tasks
[INFO] PL/Java examples
[INFO] PL/Java packaging

The second one seems to skip right to pljava-so:

[INFO] Reactor Build Order:
[INFO]
[INFO] PL/Java backend native code
[INFO] PL/Java Ant tasks
[INFO] PL/Java examples
[INFO] PL/Java packaging
=C2=A0
Yes, when th= e second build failed. I ran mvn install -rf :pljava-so -X -e.
In nar-maven-plugin 3.2.3, the line with the null pointer exception
seems to be this one:

https://github.com/maven-nar/nar-maven-plugin/bl= ob/nar-maven-plugin-3.2.3/src/main/java/com/github/maven_nar/Compiler.java#= L499

which makes me think that some entry of 'defines' is a null.

Any suggestions what could be the=C2=A0proble= m? As far as I see in the build.xml, I can only think of MSVC.RINT=C2=A0but= it should not be probably the cause.
=C2=A0
If you're running the build with Java 14 or later, you may be able
to squeeze a little more information out of a NullPointerException
by putting the right -XX:... option in the MAVEN_OPTS environment
variable (see [1]). In this case it might only say something like
"cannot call method split() because receiver is null" (I don'= t see
a lot of other possibilities on that line) but in general it might
be helpful.
=C2=A0
Yes, I understand that bu= t as you say it isn't beneficial in this case.
--00000000000041007e05aa02868b--