All of my development is on Catalina and IntelliJ and I haven’t had any trouble
with the build.
Thanks
Shawn
Sent from my iPhone
> On Jan 17, 2020, at 6:25 PM, Marc Parisi wrote:
>
> Mike my osx builds are also Catalina based. I usually add -T2C but don't
> recall if I added that to the
-1 binding.
https://issues.apache.org/jira/browse/NIFI-7044
On Fri, Jan 17, 2020 at 12:41 PM Marc Parisi wrote:
> +1 Binding to release
>
>Followed the release helper guide -- didn't see any license issues, all
> looks good.
>I built and ran with some custom NARs on a sizable Apache
Mike my osx builds are also Catalina based. I usually add -T2C but don't
recall if I added that to the release vote build. The output was
successful, though.
If it only sporadically occurs I can retry a few more times or run in a
loop tomorrow.
On Fri, Jan 17, 2020, 7:10 PM Joe Witt wrote:
>
Command I use to build:
mvn -T 1C clean install -Pinclude-grpc -Ddir-only
JAVA 8 on Catalina
……
[INFO] nifi-system-test-extensions-nar SUCCESS [ 0.832
s]
[INFO] nifi-system-test-extensions2-bundle SUCCESS [ 0.044
s]
[INFO]
ill build on catalina now and let you know what i see
thanks
On Fri, Jan 17, 2020 at 6:15 PM Mike Thomsen wrote:
> That makes me strongly suspect that the problems I've had with a few unit
> tests are an OS issue.
>
> On Fri, Jan 17, 2020 at 2:26 PM Joe Witt wrote:
>
> > I did it on macOS
That makes me strongly suspect that the problems I've had with a few unit
tests are an OS issue.
On Fri, Jan 17, 2020 at 2:26 PM Joe Witt wrote:
> I did it on macOS Mojave and Fedora 31.
>
> Thanks
>
> On Fri, Jan 17, 2020 at 2:18 PM Mike Thomsen
> wrote:
>
> > My company recently updated my
I did it on macOS Mojave and Fedora 31.
Thanks
On Fri, Jan 17, 2020 at 2:18 PM Mike Thomsen wrote:
> My company recently updated my MBP to Catalina. Is anyone else doing the
> release vote on that version of macOS?
>
> Thanks,
>
> Mike
>
My company recently updated my MBP to Catalina. Is anyone else doing the
release vote on that version of macOS?
Thanks,
Mike
Peter,
I dont think there has been any further discussion on evolving standard
libraries as a thing which can be shared across components. It was and is
a good idea. Needs folks to push it along is all.
That though is a different issue than release size. The release size is
issue has to do
+1 Binding to release
Followed the release helper guide -- didn't see any license issues, all
looks good.
I built and ran with some custom NARs on a sizable Apache NiFi Cluster
running a high throughput workload that I used to validate 1.10 -- no
issues encountered or performance
I know the NiFi 1.11 release process is already going on, but I thought the
community decided back in September to split most of the libraries out into the
new `NiFi Standard Libraries` Git repo/project because NiFi as a binary release
to Apache Maven was getting too big?
Was there further
+1
Hashes and signature are fine.
Build and tests work after setting JAVA_HOME.
NiFi works with a simple flow.
On Fri, 17 Jan 2020 at 16:55, Arpad Boda wrote:
>
> +1
>
> Verified signature and hashes
> Built and tests passed
> NiFi started, created a simple flow
> Transferred flowfiles using raw
+1
Verified signature and hashes
Build and all tests passed
Checked readme and license files
Nifi Started without any issue
On Fri, Jan 17, 2020 at 4:55 PM Arpad Boda
wrote:
> +1
>
> Verified signature and hashes
> Built and tests passed
> NiFi started, created a simple flow
> Transferred
+1
Verified signature and hashes
Built and tests passed
NiFi started, created a simple flow
Transferred flowfiles using raw S2S
All worked perfectly
On Fri, Jan 17, 2020 at 2:58 PM Shawn Weeks
wrote:
> +1 Build runs fine and hashes match.
>
> On 1/16/20, 4:54 PM, "Joe Witt" wrote:
>
>
+1 Build runs fine and hashes match.
On 1/16/20, 4:54 PM, "Joe Witt" wrote:
Hello,
I am pleased to be calling this vote for the source release of Apache NiFi
nifi-1.11.0.
The source zip, including signatures, digests, etc. can be found at:
15 matches
Mail list logo
