So I just compiled and executed the simplest HTTP program I could find
import java.io.IOException;
import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;
public class ReadWebPage {
public static void main(String[] args)
No issue running the openssl command. I’m just on my personal laptop
connecting via my hotspotted phone - I’ve never had any sort of network type
issues like this before. That’s why I wondered whether it was somehow
maven/java related.
Makes no sense to me!
> On 7 Apr 2022, at 11:40 am,
Phil,
Thanks for the additional details, Maven 3.8.1 is recent, so it should work.
The stack trace include the following specific problem:
- java.net.SocketException: Network is unreachable (connect failed)
This indicates a low-level network connectivity problem. Although you
provided the curl
Sure thing David,
phil@Phils-MacBook-Pro nifi % mvn -X -T C2.0 clean install -Pinclude-grpc
Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
Maven home: /usr/local/Cellar/maven/3.8.1/libexec
Java version: 11.0.12, vendor: Oracle Corporation,
Phil,
Can you provide the version of Maven you are using? Running Maven with the
-X argument for debug will generate a lot of logging information, but it
might point to the POM resolution problem.
Regards,
David Handermann
On Wed, Apr 6, 2022 at 8:13 PM Phil H wrote:
> I reverted back to AZUL
I reverted back to AZUL JDK 11, and then in turn to Oracle JDK 11, and all had
the same issue.
So I’m assuming it’s either a OSX thing, or some sort of weird maven issue?
> On 7 Apr 2022, at 10:02 am, Mike Thomsen wrote:
>
>> However it’s not a network issue because…
>
> Could be something
Related. You said you're used to building in offline environments. You
were also using a really old build Java 8 early on in the previous
thread. If you're building on a commercial or government network, you
might want to throw the JDK and Maven on a personal laptop and do a
build there.
> However it’s not a network issue because…
Could be something funky with how Java 17's TLS APIs are working on your setup.
Java 8 and Java 11 are your best bets for now anyway. Java 17 support
is still in the early stages and isn't a preferred JDK/JRE.
On Wed, Apr 6, 2022 at 7:00 PM Phil H
So I upgraded to the Azul JDK 17. New repo, following the same instructions as
before.
phil@Phils-MacBook-Pro nifi % mvn -T C2.0 clean install -Pinclude-grpc
[INFO] Scanning for projects...
Downloading from central:
Phil,
You're welcome. I have also updated the NiFi Contributor Guide to mention
minimum supported versions:
https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide
The latest version of Java 8 is currently update 322. The automated builds
on GitHub run on Azul Zulu and Eclipse
Much appreciated. If I am upgrading the JDK on this VM (which I will only
use for NiFi contributions) should I be moving to a more modern version,
and if so, what is recommended?
On Wed, 6 Apr 2022 at 22:32, David Handermann
wrote:
> Updating the minimum Java version in the build configuration
Severity: moderate
Description:
When creating or updating credentials for single-user access, NiFi
wrote a copy of the Login Identity Providers configuration to the
operating system temporary directory. On most platforms, the operating
system temporary directory has global read permissions. NiFi
Updating the minimum Java version in the build configuration would be
helpful, I will look into submitting a pull request to include this check.
Regards,
David Handermann
On Wed, Apr 6, 2022 at 7:23 AM Chakravarty, G wrote:
> Just wondering if Nifi runs through any pre-install checks like
Just wondering if Nifi runs through any pre-install checks like minimum java
version, OS etc. like many other software. Will be nice if it does basic checks
to prevent common install failures.
From: David Handermann
Sent: Wednesday, April 6, 2022 8:11 AM
To:
Phil,
Recent versions of NiFi require Java 8 Update 251 or newer in order to
support modern signing algorithms. Java 8 Update 171 and newer include the
unrestricted Java Cryptography Extension Policy. Upgrading to the latest
Java 8 version should resolve the illegal key size issue shown in the
Australia. Never had any other issues with OpenSSL stuff, etc
On Wed, 6 Apr 2022 at 21:11, Otto Fowler wrote:
> What country are you in? Are you under export controls?
>
> From: Phil H
> Reply: dev@nifi.apache.org
> Date: April 6, 2022 at 07:08:45
> To: dev@nifi.apache.org
> Subject:
What country are you in? Are you under export controls?
From: Phil H
Reply: dev@nifi.apache.org
Date: April 6, 2022 at 07:08:45
To: dev@nifi.apache.org
Subject: Re: Missing maven dependencies when building nifi
So, I restarted the whole process inside a CentOS VM. The only way I could
So, I restarted the whole process inside a CentOS VM. The only way I could
get the build to complete was by using -DskipTests in the maven command.
Trying to run the built nifi fails after maybe 15 seconds (see below):
[phil@localhost nifi-1.17.0-SNAPSHOT]$ bin/nifi.sh run
Java home:
Hi guys,
Yep - I made sure the global git settings held before the clone.
I tried running with the options from the .yml file and got a bunch of
errors.
So I started the contributor guide again (from a new clone) and this time
compiled with:
mvn clean package verify.
It ran for a while before
19 matches
Mail list logo
