exceptionfactory closed pull request #8708: NIFI-13108 Update a variety of
dependencies
URL: https://github.com/apache/nifi/pull/8708
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
joewitt commented on PR #8708:
URL: https://github.com/apache/nifi/pull/8708#issuecomment-2091897995
@pvillard31 For the 1.x line i put together
https://issues.apache.org/jira/browse/NIFI-13131. This *should be* safe. Full
clean build and a basic runs suggests so.
--
This is an
joewitt commented on PR #8708:
URL: https://github.com/apache/nifi/pull/8708#issuecomment-2091273371
The change-set for the main branch is ready to go and looks good.
In general I do not plan to make hygiene updates on the 1.x line at this
point. The dependency management there is
pvillard31 commented on PR #8708:
URL: https://github.com/apache/nifi/pull/8708#issuecomment-2090234009
@joewitt - it feels like some of the dep upgrades included in that PR could
also apply to NiFi 1.26 - are you planning for a PR that would apply to 1.x and
should I wait for this before
joewitt commented on PR #8708:
URL: https://github.com/apache/nifi/pull/8708#issuecomment-2081686592
grrr. Need to clean these up...
❯ find . -type f | grep \\.jar | grep logback
joewitt commented on PR #8708:
URL: https://github.com/apache/nifi/pull/8708#issuecomment-2081686050
@exceptionfactory This changeset should do it. Hilariously reducing the
number of log impls changes the behavior of aws-processors test. I had to
change that in NIFI-12998 but now that it
joewitt commented on PR #8708:
URL: https://github.com/apache/nifi/pull/8708#issuecomment-2081352893
Adjusted nifi-bom to remove logback-classic and logback-core from the
dependency list even as provided as it means test runs have both slf4j-simple
and logback-classic/core. The nifi-bom
joewitt commented on PR #8708:
URL: https://github.com/apache/nifi/pull/8708#issuecomment-2081346192
the wild log output is found in at least nifi-framework-core integration
tests. And it is due to
SLF4J(W): Class path contains multiple SLF4J providers.
SLF4J(W): Found provider
joewitt commented on PR #8708:
URL: https://github.com/apache/nifi/pull/8708#issuecomment-2081340799
have noticed a good bit of failures on the windows build as well with
something related to the otel stuff.
--
This is an automated message from the Apache Git Service.
To respond to the
joewitt commented on PR #8708:
URL: https://github.com/apache/nifi/pull/8708#issuecomment-2081340390
@exceptionfactory Yeah that is an ultra bummer because i run the same
integration tests locally and they work fine. I'll run them again though and
see if the same log info comes out. I
joewitt opened a new pull request, #8708:
URL: https://github.com/apache/nifi/pull/8708
# Summary
[NIFI-0](https://issues.apache.org/jira/browse/NIFI-0)
# Tracking
Please complete the following tracking steps
11 matches
Mail list logo
