; > basic checks to prevent common install failures.
> > >
> > > From: David Handermann
> > > Sent: Wednesday, April 6, 2022 8:11 AM
> > > To: dev@nifi.apache.org
> > > Subject: Re: Missing maven dependencies when buil
ava 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: dev@nifi.apache.org
> >
2 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
@nifi.apache.org
Subject: Re: Missing maven dependencies when building nifi
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
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
> coul
he.org
> Subject: Re: Missing maven dependencies when building nifi
>
> 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 seco
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
Good point there James. Phil definitely give that a look. Those commands
need to be run on the repository at the right time as well so it doesn't
import with the wrong line endings.
>From our github automated builds we have at:
Possibly not your problem, but did you follow the instructions for building
on Windows here:
https://nifi.apache.org/quickstart.html
On Tue, 5 Apr 2022, 12:42 Phil H, wrote:
> Okay, I started over with a completely new local repo. This is the exact
> sequence of commands I ran:
>
> $ git
Okay, I started over with a completely new local repo. This is the exact
sequence of commands I ran:
$ git clone https://github.com/apache/nifi.git
$ cd nifi
$ git remote add upstream https://github.com/apache/nifi.git
$ git clean -fxd
$ mvn clean package verify
Thanks Joe!
On Tue, 5 Apr 2022 at 00:53, Joe Witt wrote:
> Phil
>
> I think you need to run 'git clean -fxd' from the nifi source root.
>
> Then try the build again. And allow the entire thing to run.
>
> Too many builds in different levels are leaving things around.
>
> Thanks
>
> On Mon, Apr
Phil
I think you need to run 'git clean -fxd' from the nifi source root.
Then try the build again. And allow the entire thing to run.
Too many builds in different levels are leaving things around.
Thanks
On Mon, Apr 4, 2022 at 7:46 AM Phil H wrote:
> So, about that error that flashed
So, about that error that flashed past...
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 22:21 min (Wall Clock)
[INFO] Finished at:
Thanks Joe, it seems to be about half way through now - much further than
previously. I thought I saw some red text flash past, but nothing
stopped. Does one of those switches you suggested pile all the bad news up
to deliver at the end, or can maven have "red errors" that aren't terminal?
TIA,
Thanks Mike - that certainly moved the pieces along the board. Your
patience for my ignorance is greatly appreciated ;-)
Sidenote: I always thought mvn "install" was to do with packaging up
binaries, and occurred after the "test" phase had completed?
So, got a new new problem:
[INFO] Running
Phil
Here is a command I commonly run to ensure I have nothing other than
what the source tree intends.
mvn -T C1 clean package verify -Pcontrib-check,include-grpc
This will do everything - build it all, run contrib check, and use all the
cores.
Thanks
On Mon, Apr 4, 2022 at 6:38 AM Mike
Did you run "mvn install" from the root of the project before
attempting to run a full test of the code base?
On Mon, Apr 4, 2022 at 9:36 AM Phil H wrote:
>
> Hi there,
>
> So I got past this issue by running "mvn test" from the root of the nifi
> tree. After much compiling and testing, I am
Hi there,
So I got past this issue by running "mvn test" from the root of the nifi
tree. After much compiling and testing, I am now getting the attached
error. I think I am following the contributor guide in having my local
branch track origin/main (currently "4a90334728: NIFI-9846 Implement
Hi there,
Trying to build the nifi git repo for the first time and I'm getting the
message below
I'm used to working in offline development environments, so I'm a bit lost
with this online dependency stuff. I note that
https://repository.apache.org/snapshots/org/apache/nifi/ doesn't contain
any
21 matches
Mail list logo
