Skip to content

NIFI-13913 Declared provided dependency on slf4-api in nifi-registry-…#9431

Merged
exceptionfactory merged 1 commit intoapache:mainfrom
bbende:NIFI-13913
Oct 21, 2024
Merged

NIFI-13913 Declared provided dependency on slf4-api in nifi-registry-…#9431
exceptionfactory merged 1 commit intoapache:mainfrom
bbende:NIFI-13913

Conversation

@bbende
Copy link
Contributor

@bbende bbende commented Oct 21, 2024

…web-api to prevent pacakging it in the WAR and instead obtain it from lib

Summary

NIFI-13913

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

Pull Request Tracking

  • Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
  • Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

  • Pull Request based on current revision of the main branch
  • Pull Request refers to a feature branch with one commit containing changes

Verification

Please indicate the verification steps performed prior to pull request creation.

Build

  • Build completed using mvn clean install -P contrib-check
    • JDK 21

Licensing

  • New dependencies are compatible with the Apache License 2.0 according to the License Policy
  • New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

  • Documentation formatting appears as expected in rendered files

…web-api to prevent pacakging it in the WAR and instead obtain it from lib
Copy link
Contributor

@exceptionfactory exceptionfactory left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for correcting this dependency on slf4j-api @bbende. Planning to merge pending successful builds.

@exceptionfactory exceptionfactory merged commit ab28464 into apache:main Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants