Skip to content

NIFI-9552 Fix the same NoClassDefFound error in case of nifi-registry…#5663

Closed
taz1988 wants to merge 1 commit intoapache:mainfrom
taz1988:NIFI-9552-registry
Closed

NIFI-9552 Fix the same NoClassDefFound error in case of nifi-registry…#5663
taz1988 wants to merge 1 commit intoapache:mainfrom
taz1988:NIFI-9552-registry

Conversation

@taz1988
Copy link
Contributor

@taz1988 taz1988 commented Jan 17, 2022

… ranger plugin

Without define the jcl runtime dependency, the assembly plugin will not copy the jcl jar to the ranger lib directory,
which cause NoClassDefFoundError in some cases

Thank you for submitting a contribution to Apache NiFi.

Please provide a short description of the PR here:

Description of PR

Fixes bug NIFI-9552

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

  • Is there a JIRA ticket associated with this PR? Is it referenced
    in the commit message?

  • Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

  • Has your PR been rebased against the latest commit within the target branch (typically main)?

  • Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

  • Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
  • Have you written or updated unit tests to verify your changes?
  • Have you verified that the full build is successful on JDK 8?
  • Have you verified that the full build is successful on JDK 11?
  • If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
  • If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
  • If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
  • If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

  • Have you ensured that format looks appropriate for the output in which it is rendered?

Note:

Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

… ranger plugin

Without define the jcl runtime dependency, the assembly plugin will not copy the jcl jar to the ranger lib directory,
which cause NoClassDefFoundError in some cases
@pvillard31
Copy link
Contributor

@exceptionfactory @bbende - you may want to have a look at this one?

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 the improvement @taz1988! Verified that jcl-over-slf4j is present in the nifi-registry-ranger-assembly as expected. +1 Merging.

krisztina-zsihovszki pushed a commit to krisztina-zsihovszki/nifi that referenced this pull request Jun 28, 2022
…ssembly

Without define the jcl-over-slf4j runtime dependency, the assembly plugin will not copy the jcl jar to the ranger lib directory,
which cause NoClassDefFoundError in some cases

This closes apache#5663

Signed-off-by: David Handermann <exceptionfactory@apache.org>
Lehel44 pushed a commit to Lehel44/nifi that referenced this pull request Jul 1, 2022
…ssembly

Without define the jcl-over-slf4j runtime dependency, the assembly plugin will not copy the jcl jar to the ranger lib directory,
which cause NoClassDefFoundError in some cases

This closes apache#5663

Signed-off-by: David Handermann <exceptionfactory@apache.org>
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.

3 participants