You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by Michal Tomaszewski <Mi...@cca.pl> on 2022/01/19 10:24:36 UTC

Nifi 1.15.2 and 1.15.3 compilation errors

Hi,
We are trying to compile nifi from sources.
There is no problem with 1.15.1 compilation but in case of 1.15.2 and 1.15.3 there are compilation errors.

Can you suggest how to solve this problem?

mvn dependency:tree has no errors:


$ tail log1.txt
[INFO] nifi-toolkit-flowfile-repo ......................... SUCCESS [  0.005 s]
[INFO] nifi-toolkit-flowanalyzer .......................... SUCCESS [  0.008 s]
[INFO] nifi-toolkit-assembly .............................. SUCCESS [  0.463 s]
[INFO] nifi-toolkit-api ................................... SUCCESS [  0.023 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  02:41 min
[INFO] Finished at: 2022-01-19T08:51:46+01:00


Compilation of branch rel/nifi-1.15.3:

[DEBUG] Adding ERROR message due to exception
org.apache.maven.enforcer.rule.api.EnforcerRuleException: Found Banned Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
    at org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute (AbstractBanDependencies.java:113)
    at org.apache.maven.plugins.enforcer.EnforceMojo.execute (EnforceMojo.java:200)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:196)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:186)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)
    at java.lang.Thread.run (Thread.java:748)
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
Found Banned Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
[INFO]

….

[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce (enforce-banned-dependencies) on project nifi-kite-processors: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce (enforce-banned-dependencies) on project nifi-kite-processors: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:196)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:186)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)
    at java.lang.Thread.run (Thread.java:748)
Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
    at org.apache.maven.plugins.enforcer.EnforceMojo.execute (EnforceMojo.java:255)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:196)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:186)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)
    at java.lang.Thread.run (Thread.java:748)
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :nifi-kite-processors

Regards,
Mike

Re: Nifi for Windows stops before Web UI shows up

Posted by Chris Sampson <ch...@naimuri.com>.
Nifi does not currently work with java 17. It is primarily targeted at java
8, although recent changes have enabled it to build and run with java 11.

You will need to change the java runtime you're using.


Cheers,

Chris Sampson

On Sat, 22 Jan 2022, 01:31 Hao Wang, <ha...@live.com> wrote:

> Dear NiFi developers :
>
> I ran NiFi on Windows command line, but it stopped before Web UI showed
> up. How do I fix this problem ?
>
> Below was the command line output :
>
> C:\Users\user\Desktop\nifi-1.14.0\bin>run-nifi.bat
> Failed to determine if Process 17988 is running; assuming that it is not
> 2022-01-22 09:27:11,056 INFO [main] org.apache.nifi.bootstrap.Command
> Starting Apache NiFi...
> 2022-01-22 09:27:11,056 INFO [main] org.apache.nifi.bootstrap.Command
> Working Directory: C:\Users\user\Desktop\NIFI-1~1.0
> 2022-01-22 09:27:11,056 INFO [main] org.apache.nifi.bootstrap.Command
> Command: C:\Program Files\Java\jdk-17.0.1\bin\java.exe -classpath
> C:\Users\user\Desktop\NIFI-1~1.0\.\conf;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\javax.servlet-api-3.1.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\jcl-over-slf4j-1.7.30.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\jetty-schemas-3.1.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\jul-to-slf4j-1.7.30.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\log4j-over-slf4j-1.7.30.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\logback-classic-1.2.3.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\logback-core-1.2.3.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\nifi-api-1.14.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\nifi-framework-api-1.14.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\nifi-nar-utils-1.14.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\nifi-properties-1.14.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\nifi-property-utils-1.14.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\nifi-runtime-1.14.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\nifi-server-api-1.14.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\nifi-stateless-api-1.14.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\nifi-stateless-bootstrap-1.14.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\slf4j-api-1.7.30.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\java11\javax.activation-api-1.2.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\java11\javax.annotation-api-1.3.2.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\java11\jaxb-api-2.3.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\java11\jaxb-core-2.3.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\java11\jaxb-impl-2.3.0.jar
> -Dorg.apache.jasper.compiler.disablejsr199=true -Xmx512m -Xms512m
> -Dcurator-log-only-first-connection-issue-as-error-level=true
> -Djavax.security.auth.useSubjectCredsOnly=true
> -Djava.security.egd=file:/dev/urandom -Dzookeeper.admin.enableServer=false
> -Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true
> -Djava.awt.headless=true -Djava.protocol.handler.pkgs=sun.net.www.protocol
> -Dnifi.properties.file.path=C:\Users\user\Desktop\NIFI-1~1.0\.\conf\nifi.properties
> -Dnifi.bootstrap.listen.port=9606 -Dapp=NiFi
> -Dorg.apache.nifi.bootstrap.config.log.dir=C:\Users\user\Desktop\NIFI-1~1.0\bin\..\\logs
> org.apache.nifi.NiFi
> 2022-01-22 09:27:11,072 WARN [main] org.apache.nifi.bootstrap.Command
> Failed to set permissions so that only the owner can read pid file
> C:\Users\user\Desktop\NIFI-1~1.0\bin\..\run\nifi.pid; this may allows
> others to have access to the key needed to communicate with NiFi.
> Permissions should be changed so that only the owner can read this file
> 2022-01-22 09:27:11,079 WARN [main] org.apache.nifi.bootstrap.Command
> Failed to set permissions so that only the owner can read status file
> C:\Users\user\Desktop\NIFI-1~1.0\bin\..\run\nifi.status; this may allows
> others to have access to the key needed to communicate with NiFi.
> Permissions should be changed so that only the owner can read this file
> 2022-01-22 09:27:11,079 INFO [main] org.apache.nifi.bootstrap.Command
> Launched Apache NiFi with Process ID 20908
>
> C:\Users\user\Desktop\nifi-1.14.0\bin>
>

Nifi for Windows stops before Web UI shows up

Posted by Hao Wang <ha...@live.com>.
Dear NiFi developers :

I ran NiFi on Windows command line, but it stopped before Web UI showed up. How do I fix this problem ?

Below was the command line output :

C:\Users\user\Desktop\nifi-1.14.0\bin>run-nifi.bat
Failed to determine if Process 17988 is running; assuming that it is not
2022-01-22 09:27:11,056 INFO [main] org.apache.nifi.bootstrap.Command Starting Apache NiFi...
2022-01-22 09:27:11,056 INFO [main] org.apache.nifi.bootstrap.Command Working Directory: C:\Users\user\Desktop\NIFI-1~1.0
2022-01-22 09:27:11,056 INFO [main] org.apache.nifi.bootstrap.Command Command: C:\Program Files\Java\jdk-17.0.1\bin\java.exe -classpath C:\Users\user\Desktop\NIFI-1~1.0\.\conf;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\javax.servlet-api-3.1.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\jcl-over-slf4j-1.7.30.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\jetty-schemas-3.1.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\jul-to-slf4j-1.7.30.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\log4j-over-slf4j-1.7.30.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\logback-classic-1.2.3.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\logback-core-1.2.3.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\nifi-api-1.14.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\nifi-framework-api-1.14.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\nifi-nar-utils-1.14.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\nifi-properties-1.14.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\nifi-property-utils-1.14.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\nifi-runtime-1.14.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\nifi-server-api-1.14.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\nifi-stateless-api-1.14.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\nifi-stateless-bootstrap-1.14.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\slf4j-api-1.7.30.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\java11\javax.activation-api-1.2.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\java11\javax.annotation-api-1.3.2.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\java11\jaxb-api-2.3.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\java11\jaxb-core-2.3.0.jar;C:\Users\user\Desktop\NIFI-1~1.0\.\lib\java11\jaxb-impl-2.3.0.jar -Dorg.apache.jasper.compiler.disablejsr199=true -Xmx512m -Xms512m -Dcurator-log-only-first-connection-issue-as-error-level=true -Djavax.security.auth.useSubjectCredsOnly=true -Djava.security.egd=file:/dev/urandom -Dzookeeper.admin.enableServer=false -Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true -Djava.awt.headless=true -Djava.protocol.handler.pkgs=sun.net.www.protocol -Dnifi.properties.file.path=C:\Users\user\Desktop\NIFI-1~1.0\.\conf\nifi.properties -Dnifi.bootstrap.listen.port=9606 -Dapp=NiFi -Dorg.apache.nifi.bootstrap.config.log.dir=C:\Users\user\Desktop\NIFI-1~1.0\bin\..\\logs org.apache.nifi.NiFi
2022-01-22 09:27:11,072 WARN [main] org.apache.nifi.bootstrap.Command Failed to set permissions so that only the owner can read pid file C:\Users\user\Desktop\NIFI-1~1.0\bin\..\run\nifi.pid; this may allows others to have access to the key needed to communicate with NiFi. Permissions should be changed so that only the owner can read this file
2022-01-22 09:27:11,079 WARN [main] org.apache.nifi.bootstrap.Command Failed to set permissions so that only the owner can read status file C:\Users\user\Desktop\NIFI-1~1.0\bin\..\run\nifi.status; this may allows others to have access to the key needed to communicate with NiFi. Permissions should be changed so that only the owner can read this file
2022-01-22 09:27:11,079 INFO [main] org.apache.nifi.bootstrap.Command Launched Apache NiFi with Process ID 20908

C:\Users\user\Desktop\nifi-1.14.0\bin>

Re: Nifi 1.15.2 and 1.15.3 compilation errors

Posted by David Handermann <ex...@apache.org>.
Mike,

You're welcome! The nifi-kite-bundle has been removed from the main branch
of Apache NiFi as of the following commit, so this shouldn't be a problem
for future builds.

https://github.com/apache/nifi/commit/8edb5faac9ff469e4c810891c30892962ed83b29

Regards,
David Handermann

On Wed, Jan 19, 2022 at 10:56 AM Michal Tomaszewski <
Michal.Tomaszewski@cca.pl> wrote:

> David,
>
> Thank you for your help.
>
> We made a change and compilation was successful.
>
>
>
> Regards,
>
> Mike
>
>
>
> *From:* David Handermann <ex...@apache.org>
> *Sent:* środa, 19 stycznia 2022 15:47
> *To:* users@nifi.apache.org
> *Subject:* Re: Nifi 1.15.2 and 1.15.3 compilation errors
>
>
>
> Mike,
>
>
>
> Thanks for the additional details. According to the original output, the
> problem appears to be in the nifi-kite-processors module.  The
> nifi-kite-processors module includes a dependency on hive-hcatalog-core,
> the version of which is based on the hive.version property.  We should be
> able to add an exclusion for log4j-core within that dependency definition,
> which will allow it to compile with Hive 3.1.2.  For the moment, if you
> don't need the Kite processors, you could skip building nifi-kite-nar, or
> you could manually add the following exclusion:
>
> <exclusion>
>
>   <groupId>org.apache.logging.log4j</groupId>
>
>   <artifactId>log4j-core</artifactId>
>
> <exclusion>
>
> Regards,
>
> David Handermann
>
>
>
> On Wed, Jan 19, 2022 at 8:27 AM Michal Tomaszewski <
> Michal.Tomaszewski@cca.pl> wrote:
>
> Compilation with -Dhive.version=3.1.0 makes the problem.
> mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0
> is not successful.
> We also tested -Dhive.version=3.1.2, that is most recent on Apache Hive
> site. Also without success.
>
> Please note that without this parameter probably hive2 version is compiled
> into nifi and HiveStreaming is not working then.
> And hive 3 is most popular novadays.
>
> Regards,
> Mike
>
> -----Original Message-----
> From: Bryan Bende <bb...@gmail.com>
> Sent: Wednesday, January 19, 2022 3:03 PM
> To: users@nifi.apache.org
> Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>
> We did ban all use of log4j-core in favor of log4j-to-slf4j...
>
> https://issues.apache.org/jira/browse/NIFI-9483
>
> With your build specifying the -D versions, it created a different
> classpath during your build than what existed during the normal build of
> the release.
>
> We should try to fix any issues like this though, so if you can figure out
> which dependency path is the issue, the fix is to add some exclusions and
> then to ensure that log4j-to-slf4j dependency is added.
>
> On Wed, Jan 19, 2022 at 8:48 AM Michal Tomaszewski <
> Michal.Tomaszewski@cca.pl> wrote:
> >
> > OK, but there is information that log4j-core:jar:2.17.1 is blocked:
> >
> > [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies
> failed with message:
> >
> > Found Banned Dependency:
> > org.apache.logging.log4j:log4j-core:jar:2.17.1
> >
> > while this version is not impacted by log4j security vulnerability:
> >
> > https://logging.apache.org/log4j/2.x/security.html
> >
> >
> >
> > So for sure it shouldn’t be banned.
> >
> >
> >
> > Regards,
> >
> > Mike
> >
> > From: Pierre Villard <pi...@gmail.com>
> > Sent: Wednesday, January 19, 2022 1:11 PM
> > To: users@nifi.apache.org
> > Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
> >
> >
> >
> > We recently changed the build to fail if it's including problematic
> transitive dependencies for log4j. I think those are coming with the
> specific versions of HBase/Hive you're using. Not a maven expert but I
> guess there is a way to exclude the step "enforce-banned-dependencies" from
> the build.
> >
> >
> >
> > Le mer. 19 janv. 2022 à 12:57, Michal Tomaszewski <
> Michal.Tomaszewski@cca.pl> a écrit :
> >
> > Hi Edward,
> >
> > Full mvn dependency:tree log enclosed.
> >
> > We’re compiling using command:
> >
> > mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0
> > -Dhbase.version=2.0.2
> >
> >
> >
> > Regards,
> >
> > Mike
> >
> >
> >
> > From: Edward Armes <ed...@gmail.com>
> > Sent: Wednesday, January 19, 2022 12:34 PM
> > To: users@nifi.apache.org
> > Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
> >
> >
> >
> > Hi Mike,
> >
> >
> >
> > Can you give the full output you get from mvn dependency:tree as we 15.2
> and 3 was done to remove log4j dependences from Nifi as a safety measure
> due the recent log4shell issues.
> >
> >
> >
> > Thanks
> >
> >
> >
> > Edward
> >
> >
> >
> > On Wed, Jan 19, 2022 at 10:24 AM Michal Tomaszewski <
> Michal.Tomaszewski@cca.pl> wrote:
> >
> > Hi,
> >
> > We are trying to compile nifi from sources.
> >
> > There is no problem with 1.15.1 compilation but in case of 1.15.2 and
> 1.15.3 there are compilation errors.
> >
> >
> >
> > Can you suggest how to solve this problem?
> >
> >
> >
> > mvn dependency:tree has no errors:
> >
> >
> >
> >
> >
> > $ tail log1.txt
> >
> > [INFO] nifi-toolkit-flowfile-repo ......................... SUCCESS [
> > 0.005 s]
> >
> > [INFO] nifi-toolkit-flowanalyzer .......................... SUCCESS [
> > 0.008 s]
> >
> > [INFO] nifi-toolkit-assembly .............................. SUCCESS [
> > 0.463 s]
> >
> > [INFO] nifi-toolkit-api ................................... SUCCESS [
> > 0.023 s]
> >
> > [INFO]
> > ----------------------------------------------------------------------
> > --
> >
> > [INFO] BUILD SUCCESS
> >
> > [INFO]
> > ----------------------------------------------------------------------
> > --
> >
> > [INFO] Total time:  02:41 min
> >
> > [INFO] Finished at: 2022-01-19T08:51:46+01:00
> >
> >
> >
> >
> >
> > Compilation of branch rel/nifi-1.15.3:
> >
> >
> >
> > [DEBUG] Adding ERROR message due to exception
> >
> > org.apache.maven.enforcer.rule.api.EnforcerRuleException: Found Banned
> > Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
> >
> > Use 'mvn dependency:tree' to locate the source of the banned
> dependencies.
> >
> >     at
> > org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute
> > (AbstractBanDependencies.java:113)
> >
> >     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
> > (EnforceMojo.java:200)
> >
> >     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> > (DefaultBuildPluginManager.java:137)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:210)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:156)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:148)
> >
> >     at
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> > t (LifecycleModuleBuilder.java:117)
> >
> >     at
> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> > dBuilder$1.call (MultiThreadedBuilder.java:196)
> >
> >     at
> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> > dBuilder$1.call (MultiThreadedBuilder.java:186)
> >
> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >
> >     at java.util.concurrent.Executors$RunnableAdapter.call
> > (Executors.java:511)
> >
> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >
> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
> > (ThreadPoolExecutor.java:1149)
> >
> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> > (ThreadPoolExecutor.java:624)
> >
> >     at java.lang.Thread.run (Thread.java:748)
> >
> > [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies
> failed with message:
> >
> > Found Banned Dependency:
> > org.apache.logging.log4j:log4j-core:jar:2.17.1
> >
> > Use 'mvn dependency:tree' to locate the source of the banned
> dependencies.
> >
> > [INFO]
> >
> >
> >
> > ….
> >
> >
> >
> > [INFO]
> > ----------------------------------------------------------------------
> > --
> >
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
> > (enforce-banned-dependencies) on project nifi-kite-processors: Some
> > Enforcer rules have failed. Look above for specific messages
> > explaining why the rule failed. -> [Help 1]
> >
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
> (enforce-banned-dependencies) on project nifi-kite-processors: Some
> Enforcer rules have failed. Look above for specific messages explaining why
> the rule failed.
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:215)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:156)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:148)
> >
> >     at
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> > t (LifecycleModuleBuilder.java:117)
> >
> >     at
> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> > dBuilder$1.call (MultiThreadedBuilder.java:196)
> >
> >     at
> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> > dBuilder$1.call (MultiThreadedBuilder.java:186)
> >
> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >
> >     at java.util.concurrent.Executors$RunnableAdapter.call
> > (Executors.java:511)
> >
> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >
> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
> > (ThreadPoolExecutor.java:1149)
> >
> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> > (ThreadPoolExecutor.java:624)
> >
> >     at java.lang.Thread.run (Thread.java:748)
> >
> > Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer
> rules have failed. Look above for specific messages explaining why the rule
> failed.
> >
> >     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
> > (EnforceMojo.java:255)
> >
> >     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> > (DefaultBuildPluginManager.java:137)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:210)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:156)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:148)
> >
> >     at
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> > t (LifecycleModuleBuilder.java:117)
> >
> >     at
> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> > dBuilder$1.call (MultiThreadedBuilder.java:196)
> >
> >     at
> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> > dBuilder$1.call (MultiThreadedBuilder.java:186)
> >
> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >
> >     at java.util.concurrent.Executors$RunnableAdapter.call
> > (Executors.java:511)
> >
> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >
> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
> > (ThreadPoolExecutor.java:1149)
> >
> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> > (ThreadPoolExecutor.java:624)
> >
> >     at java.lang.Thread.run (Thread.java:748)
> >
> > [ERROR]
> >
> > [ERROR]
> >
> > [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> >
> > [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionExceptio
> > n
> >
> > [ERROR]
> >
> > [ERROR] After correcting the problems, you can resume the build with
> > the command
> >
> > [ERROR]   mvn <args> -rf :nifi-kite-processors
> >
> >
> >
> > Regards,
> >
> > Mike
>
>

RE: Nifi 1.15.2 and 1.15.3 compilation errors

Posted by Michal Tomaszewski <Mi...@cca.pl>.
David,
Thank you for your help.
We made a change and compilation was successful.

Regards,
Mike

From: David Handermann <ex...@apache.org>
Sent: środa, 19 stycznia 2022 15:47
To: users@nifi.apache.org
Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors

Mike,

Thanks for the additional details. According to the original output, the problem appears to be in the nifi-kite-processors module.  The nifi-kite-processors module includes a dependency on hive-hcatalog-core, the version of which is based on the hive.version property.  We should be able to add an exclusion for log4j-core within that dependency definition, which will allow it to compile with Hive 3.1.2.  For the moment, if you don't need the Kite processors, you could skip building nifi-kite-nar, or you could manually add the following exclusion:
<exclusion>
  <groupId>org.apache.logging.log4j</groupId>
  <artifactId>log4j-core</artifactId>
<exclusion>
Regards,
David Handermann

On Wed, Jan 19, 2022 at 8:27 AM Michal Tomaszewski <Mi...@cca.pl>> wrote:
Compilation with -Dhive.version=3.1.0 makes the problem.
mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0
is not successful.
We also tested -Dhive.version=3.1.2, that is most recent on Apache Hive site. Also without success.

Please note that without this parameter probably hive2 version is compiled into nifi and HiveStreaming is not working then.
And hive 3 is most popular novadays.

Regards,
Mike

-----Original Message-----
From: Bryan Bende <bb...@gmail.com>>
Sent: Wednesday, January 19, 2022 3:03 PM
To: users@nifi.apache.org<ma...@nifi.apache.org>
Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors

We did ban all use of log4j-core in favor of log4j-to-slf4j...

https://issues.apache.org/jira/browse/NIFI-9483

With your build specifying the -D versions, it created a different classpath during your build than what existed during the normal build of the release.

We should try to fix any issues like this though, so if you can figure out which dependency path is the issue, the fix is to add some exclusions and then to ensure that log4j-to-slf4j dependency is added.

On Wed, Jan 19, 2022 at 8:48 AM Michal Tomaszewski <Mi...@cca.pl>> wrote:
>
> OK, but there is information that log4j-core:jar:2.17.1 is blocked:
>
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
>
> Found Banned Dependency:
> org.apache.logging.log4j:log4j-core:jar:2.17.1
>
> while this version is not impacted by log4j security vulnerability:
>
> https://logging.apache.org/log4j/2.x/security.html
>
>
>
> So for sure it shouldn’t be banned.
>
>
>
> Regards,
>
> Mike
>
> From: Pierre Villard <pi...@gmail.com>>
> Sent: Wednesday, January 19, 2022 1:11 PM
> To: users@nifi.apache.org<ma...@nifi.apache.org>
> Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>
>
>
> We recently changed the build to fail if it's including problematic transitive dependencies for log4j. I think those are coming with the specific versions of HBase/Hive you're using. Not a maven expert but I guess there is a way to exclude the step "enforce-banned-dependencies" from the build.
>
>
>
> Le mer. 19 janv. 2022 à 12:57, Michal Tomaszewski <Mi...@cca.pl>> a écrit :
>
> Hi Edward,
>
> Full mvn dependency:tree log enclosed.
>
> We’re compiling using command:
>
> mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0
> -Dhbase.version=2.0.2
>
>
>
> Regards,
>
> Mike
>
>
>
> From: Edward Armes <ed...@gmail.com>>
> Sent: Wednesday, January 19, 2022 12:34 PM
> To: users@nifi.apache.org<ma...@nifi.apache.org>
> Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>
>
>
> Hi Mike,
>
>
>
> Can you give the full output you get from mvn dependency:tree as we 15.2 and 3 was done to remove log4j dependences from Nifi as a safety measure due the recent log4shell issues.
>
>
>
> Thanks
>
>
>
> Edward
>
>
>
> On Wed, Jan 19, 2022 at 10:24 AM Michal Tomaszewski <Mi...@cca.pl>> wrote:
>
> Hi,
>
> We are trying to compile nifi from sources.
>
> There is no problem with 1.15.1 compilation but in case of 1.15.2 and 1.15.3 there are compilation errors.
>
>
>
> Can you suggest how to solve this problem?
>
>
>
> mvn dependency:tree has no errors:
>
>
>
>
>
> $ tail log1.txt
>
> [INFO] nifi-toolkit-flowfile-repo ......................... SUCCESS [
> 0.005 s]
>
> [INFO] nifi-toolkit-flowanalyzer .......................... SUCCESS [
> 0.008 s]
>
> [INFO] nifi-toolkit-assembly .............................. SUCCESS [
> 0.463 s]
>
> [INFO] nifi-toolkit-api ................................... SUCCESS [
> 0.023 s]
>
> [INFO]
> ----------------------------------------------------------------------
> --
>
> [INFO] BUILD SUCCESS
>
> [INFO]
> ----------------------------------------------------------------------
> --
>
> [INFO] Total time:  02:41 min
>
> [INFO] Finished at: 2022-01-19T08:51:46+01:00
>
>
>
>
>
> Compilation of branch rel/nifi-1.15.3:
>
>
>
> [DEBUG] Adding ERROR message due to exception
>
> org.apache.maven.enforcer.rule.api.EnforcerRuleException: Found Banned
> Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
>
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
>
>     at
> org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute
> (AbstractBanDependencies.java:113)
>
>     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
> (EnforceMojo.java:200)
>
>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
>
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> t (LifecycleModuleBuilder.java:117)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> dBuilder$1.call (MultiThreadedBuilder.java:196)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> dBuilder$1.call (MultiThreadedBuilder.java:186)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:511)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1149)
>
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:624)
>
>     at java.lang.Thread.run (Thread.java:748)
>
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
>
> Found Banned Dependency:
> org.apache.logging.log4j:log4j-core:jar:2.17.1
>
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
>
> [INFO]
>
>
>
> ….
>
>
>
> [INFO]
> ----------------------------------------------------------------------
> --
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
> (enforce-banned-dependencies) on project nifi-kite-processors: Some
> Enforcer rules have failed. Look above for specific messages
> explaining why the rule failed. -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce (enforce-banned-dependencies) on project nifi-kite-processors: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
>
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> t (LifecycleModuleBuilder.java:117)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> dBuilder$1.call (MultiThreadedBuilder.java:196)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> dBuilder$1.call (MultiThreadedBuilder.java:186)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:511)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1149)
>
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:624)
>
>     at java.lang.Thread.run (Thread.java:748)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
>
>     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
> (EnforceMojo.java:255)
>
>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
>
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> t (LifecycleModuleBuilder.java:117)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> dBuilder$1.call (MultiThreadedBuilder.java:196)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> dBuilder$1.call (MultiThreadedBuilder.java:186)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:511)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1149)
>
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:624)
>
>     at java.lang.Thread.run (Thread.java:748)
>
> [ERROR]
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
>
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionExceptio
> n
>
> [ERROR]
>
> [ERROR] After correcting the problems, you can resume the build with
> the command
>
> [ERROR]   mvn <args> -rf :nifi-kite-processors
>
>
>
> Regards,
>
> Mike

Re: Nifi 1.15.2 and 1.15.3 compilation errors

Posted by Edward Armes <ed...@gmail.com>.
This should be brought up in a new thread (and will do later) given that
the original decision to not re-publish these processors was down to space
issues. Is it worth of the back of 2.0 to re-think the idea of
re-publishing a new version of a processor every single time a release is
done, given that we are likely to have more processors as time goes this is
somewhat delaying the inevitable in that perspective.

The overheads of doing so are not lost on me in the short term, but longer
term I suspect it might help us. As an aside I've noticed that those
processors are not listed in the docs on the website, which could limit
usage especially for any one looking for an easy to use implementation of
Apache Tika.

Edward

On Thu, Jan 20, 2022 at 7:41 PM Michal Tomaszewski <
Michal.Tomaszewski@cca.pl> wrote:

> Thank you very much for explanation.
>
> Regards,
> Mike
>
> -----Original Message-----
> From: Joe Witt <jo...@gmail.com>
> Sent: czwartek, 20 stycznia 2022 19:36
> To: users@nifi.apache.org
> Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>
> Mike
>
> Yeah a bit more than two years ago we stopped including the nifi-kite-nar
> by default.
> https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance
>
> That means the processors in it are no longer included by default.
> Since that time though we still build and published the nar to maven
> artifact repos.
>
> What we've done now is we've removed the source from our repo and will not
> publish the nar going forward.  That said you'll be able to keep using the
> already published nars to do this as you need.  Until we release a nifi 2.0
> you should be safe from them breaking.
>
> But as Chris Sampsson just replied you almost certainly want to
> discontinue using them anyway and switch to using the record based
> processors.  They are far more efficient, far more powerful, and are
> extremely actively developed and maintained.
>
> Thanks
>
> On Thu, Jan 20, 2022 at 11:32 AM Chris Sampson <ch...@naimuri.com>
> wrote:
> >
> > If the kite nar is refined then that processor would indeed no longer be
> present.
> >
> > A good alternative would be to use a Record based processor such as
> ConvertRecord with a CSVReader and an AvroWriter. Such processors and
> controller services typically offer much more powerful options than the
> older processors such as those in the kite nar.
> >
> >
> > Cheers,
> >
> > Chris Sampson
> >
> > On Thu, 20 Jan 2022, 18:08 Michal Tomaszewski, <
> Michal.Tomaszewski@cca.pl> wrote:
> >>
> >> Joe,
> >>
> >> Does it mean ConvertCSVToAvro will disappear too?
> >>
> >> Or you discontinue only a part of org.apache.nifi.processors.kite
> schema and the rest will be somehow moved to other schemas?
> >>
> >>
> >>
> >> Regards,
> >>
> >> Mike
> >>
> >>
> >>
> >>
> >>
> >> From: Joe Witt <jo...@gmail.com>
> >> Sent: środa, 19 stycznia 2022 15:57
> >> To: users@nifi.apache.org
> >> Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
> >>
> >>
> >>
> >> We should discontinue Kite processors from the build at all in 1.16.0.
> >>
> >>
> >>
> >> Ill file a Jira
> >>
> >>
> >>
> >> Thanks
> >>
> >>
> >>
> >> On Wed, Jan 19, 2022 at 7:47 AM David Handermann <
> exceptionfactory@apache.org> wrote:
> >>
> >> Mike,
> >>
> >>
> >>
> >> Thanks for the additional details. According to the original output,
> the problem appears to be in the nifi-kite-processors module.  The
> nifi-kite-processors module includes a dependency on hive-hcatalog-core,
> the version of which is based on the hive.version property.  We should be
> able to add an exclusion for log4j-core within that dependency definition,
> which will allow it to compile with Hive 3.1.2.  For the moment, if you
> don't need the Kite processors, you could skip building nifi-kite-nar, or
> you could manually add the following exclusion:
> >>
> >> <exclusion>
> >>
> >>   <groupId>org.apache.logging.log4j</groupId>
> >>
> >>   <artifactId>log4j-core</artifactId>
> >>
> >> <exclusion>
> >>
> >> Regards,
> >>
> >> David Handermann
> >>
> >>
> >>
> >> On Wed, Jan 19, 2022 at 8:27 AM Michal Tomaszewski <
> Michal.Tomaszewski@cca.pl> wrote:
> >>
> >> Compilation with -Dhive.version=3.1.0 makes the problem.
> >> mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0 is
> >> not successful.
> >> We also tested -Dhive.version=3.1.2, that is most recent on Apache Hive
> site. Also without success.
> >>
> >> Please note that without this parameter probably hive2 version is
> compiled into nifi and HiveStreaming is not working then.
> >> And hive 3 is most popular novadays.
> >>
> >> Regards,
> >> Mike
> >>
> >> -----Original Message-----
> >> From: Bryan Bende <bb...@gmail.com>
> >> Sent: Wednesday, January 19, 2022 3:03 PM
> >> To: users@nifi.apache.org
> >> Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
> >>
> >> We did ban all use of log4j-core in favor of log4j-to-slf4j...
> >>
> >> https://issues.apache.org/jira/browse/NIFI-9483
> >>
> >> With your build specifying the -D versions, it created a different
> classpath during your build than what existed during the normal build of
> the release.
> >>
> >> We should try to fix any issues like this though, so if you can figure
> out which dependency path is the issue, the fix is to add some exclusions
> and then to ensure that log4j-to-slf4j dependency is added.
> >>
> >> On Wed, Jan 19, 2022 at 8:48 AM Michal Tomaszewski <
> Michal.Tomaszewski@cca.pl> wrote:
> >> >
> >> > OK, but there is information that log4j-core:jar:2.17.1 is blocked:
> >> >
> >> > [WARNING] Rule 0:
> org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
> >> >
> >> > Found Banned Dependency:
> >> > org.apache.logging.log4j:log4j-core:jar:2.17.1
> >> >
> >> > while this version is not impacted by log4j security vulnerability:
> >> >
> >> > https://logging.apache.org/log4j/2.x/security.html
> >> >
> >> >
> >> >
> >> > So for sure it shouldn’t be banned.
> >> >
> >> >
> >> >
> >> > Regards,
> >> >
> >> > Mike
> >> >
> >> > From: Pierre Villard <pi...@gmail.com>
> >> > Sent: Wednesday, January 19, 2022 1:11 PM
> >> > To: users@nifi.apache.org
> >> > Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
> >> >
> >> >
> >> >
> >> > We recently changed the build to fail if it's including problematic
> transitive dependencies for log4j. I think those are coming with the
> specific versions of HBase/Hive you're using. Not a maven expert but I
> guess there is a way to exclude the step "enforce-banned-dependencies" from
> the build.
> >> >
> >> >
> >> >
> >> > Le mer. 19 janv. 2022 à 12:57, Michal Tomaszewski <
> Michal.Tomaszewski@cca.pl> a écrit :
> >> >
> >> > Hi Edward,
> >> >
> >> > Full mvn dependency:tree log enclosed.
> >> >
> >> > We’re compiling using command:
> >> >
> >> > mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0
> >> > -Dhbase.version=2.0.2
> >> >
> >> >
> >> >
> >> > Regards,
> >> >
> >> > Mike
> >> >
> >> >
> >> >
> >> > From: Edward Armes <ed...@gmail.com>
> >> > Sent: Wednesday, January 19, 2022 12:34 PM
> >> > To: users@nifi.apache.org
> >> > Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
> >> >
> >> >
> >> >
> >> > Hi Mike,
> >> >
> >> >
> >> >
> >> > Can you give the full output you get from mvn dependency:tree as we
> 15.2 and 3 was done to remove log4j dependences from Nifi as a safety
> measure due the recent log4shell issues.
> >> >
> >> >
> >> >
> >> > Thanks
> >> >
> >> >
> >> >
> >> > Edward
> >> >
> >> >
> >> >
> >> > On Wed, Jan 19, 2022 at 10:24 AM Michal Tomaszewski <
> Michal.Tomaszewski@cca.pl> wrote:
> >> >
> >> > Hi,
> >> >
> >> > We are trying to compile nifi from sources.
> >> >
> >> > There is no problem with 1.15.1 compilation but in case of 1.15.2 and
> 1.15.3 there are compilation errors.
> >> >
> >> >
> >> >
> >> > Can you suggest how to solve this problem?
> >> >
> >> >
> >> >
> >> > mvn dependency:tree has no errors:
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > $ tail log1.txt
> >> >
> >> > [INFO] nifi-toolkit-flowfile-repo ......................... SUCCESS
> >> > [
> >> > 0.005 s]
> >> >
> >> > [INFO] nifi-toolkit-flowanalyzer .......................... SUCCESS
> >> > [
> >> > 0.008 s]
> >> >
> >> > [INFO] nifi-toolkit-assembly .............................. SUCCESS
> >> > [
> >> > 0.463 s]
> >> >
> >> > [INFO] nifi-toolkit-api ................................... SUCCESS
> >> > [
> >> > 0.023 s]
> >> >
> >> > [INFO]
> >> > -------------------------------------------------------------------
> >> > ---
> >> > --
> >> >
> >> > [INFO] BUILD SUCCESS
> >> >
> >> > [INFO]
> >> > -------------------------------------------------------------------
> >> > ---
> >> > --
> >> >
> >> > [INFO] Total time:  02:41 min
> >> >
> >> > [INFO] Finished at: 2022-01-19T08:51:46+01:00
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > Compilation of branch rel/nifi-1.15.3:
> >> >
> >> >
> >> >
> >> > [DEBUG] Adding ERROR message due to exception
> >> >
> >> > org.apache.maven.enforcer.rule.api.EnforcerRuleException: Found
> >> > Banned
> >> > Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
> >> >
> >> > Use 'mvn dependency:tree' to locate the source of the banned
> dependencies.
> >> >
> >> >     at
> >> > org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute
> >> > (AbstractBanDependencies.java:113)
> >> >
> >> >     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
> >> > (EnforceMojo.java:200)
> >> >
> >> >     at
> >> > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> >> > (DefaultBuildPluginManager.java:137)
> >> >
> >> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> >> > (MojoExecutor.java:210)
> >> >
> >> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> >> > (MojoExecutor.java:156)
> >> >
> >> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> >> > (MojoExecutor.java:148)
> >> >
> >> >     at
> >> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildPro
> >> > jec t (LifecycleModuleBuilder.java:117)
> >> >
> >> >     at
> >> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThre
> >> > ade dBuilder$1.call (MultiThreadedBuilder.java:196)
> >> >
> >> >     at
> >> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThre
> >> > ade dBuilder$1.call (MultiThreadedBuilder.java:186)
> >> >
> >> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >> >
> >> >     at java.util.concurrent.Executors$RunnableAdapter.call
> >> > (Executors.java:511)
> >> >
> >> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >> >
> >> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
> >> > (ThreadPoolExecutor.java:1149)
> >> >
> >> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> >> > (ThreadPoolExecutor.java:624)
> >> >
> >> >     at java.lang.Thread.run (Thread.java:748)
> >> >
> >> > [WARNING] Rule 0:
> org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
> >> >
> >> > Found Banned Dependency:
> >> > org.apache.logging.log4j:log4j-core:jar:2.17.1
> >> >
> >> > Use 'mvn dependency:tree' to locate the source of the banned
> dependencies.
> >> >
> >> > [INFO]
> >> >
> >> >
> >> >
> >> > ….
> >> >
> >> >
> >> >
> >> > [INFO]
> >> > -------------------------------------------------------------------
> >> > ---
> >> > --
> >> >
> >> > [ERROR] Failed to execute goal
> >> > org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
> >> > (enforce-banned-dependencies) on project nifi-kite-processors: Some
> >> > Enforcer rules have failed. Look above for specific messages
> >> > explaining why the rule failed. -> [Help 1]
> >> >
> >> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
> (enforce-banned-dependencies) on project nifi-kite-processors: Some
> Enforcer rules have failed. Look above for specific messages explaining why
> the rule failed.
> >> >
> >> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> >> > (MojoExecutor.java:215)
> >> >
> >> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> >> > (MojoExecutor.java:156)
> >> >
> >> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> >> > (MojoExecutor.java:148)
> >> >
> >> >     at
> >> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildPro
> >> > jec t (LifecycleModuleBuilder.java:117)
> >> >
> >> >     at
> >> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThre
> >> > ade dBuilder$1.call (MultiThreadedBuilder.java:196)
> >> >
> >> >     at
> >> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThre
> >> > ade dBuilder$1.call (MultiThreadedBuilder.java:186)
> >> >
> >> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >> >
> >> >     at java.util.concurrent.Executors$RunnableAdapter.call
> >> > (Executors.java:511)
> >> >
> >> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >> >
> >> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
> >> > (ThreadPoolExecutor.java:1149)
> >> >
> >> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> >> > (ThreadPoolExecutor.java:624)
> >> >
> >> >     at java.lang.Thread.run (Thread.java:748)
> >> >
> >> > Caused by: org.apache.maven.plugin.MojoExecutionException: Some
> Enforcer rules have failed. Look above for specific messages explaining why
> the rule failed.
> >> >
> >> >     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
> >> > (EnforceMojo.java:255)
> >> >
> >> >     at
> >> > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> >> > (DefaultBuildPluginManager.java:137)
> >> >
> >> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> >> > (MojoExecutor.java:210)
> >> >
> >> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> >> > (MojoExecutor.java:156)
> >> >
> >> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> >> > (MojoExecutor.java:148)
> >> >
> >> >     at
> >> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildPro
> >> > jec t (LifecycleModuleBuilder.java:117)
> >> >
> >> >     at
> >> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThre
> >> > ade dBuilder$1.call (MultiThreadedBuilder.java:196)
> >> >
> >> >     at
> >> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThre
> >> > ade dBuilder$1.call (MultiThreadedBuilder.java:186)
> >> >
> >> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >> >
> >> >     at java.util.concurrent.Executors$RunnableAdapter.call
> >> > (Executors.java:511)
> >> >
> >> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >> >
> >> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
> >> > (ThreadPoolExecutor.java:1149)
> >> >
> >> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> >> > (ThreadPoolExecutor.java:624)
> >> >
> >> >     at java.lang.Thread.run (Thread.java:748)
> >> >
> >> > [ERROR]
> >> >
> >> > [ERROR]
> >> >
> >> > [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> >> >
> >> > [ERROR] [Help 1]
> >> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionExcep
> >> > tio
> >> > n
> >> >
> >> > [ERROR]
> >> >
> >> > [ERROR] After correcting the problems, you can resume the build
> >> > with the command
> >> >
> >> > [ERROR]   mvn <args> -rf :nifi-kite-processors
> >> >
> >> >
> >> >
> >> > Regards,
> >> >
> >> > Mike
>

RE: Nifi 1.15.2 and 1.15.3 compilation errors

Posted by Michal Tomaszewski <Mi...@cca.pl>.
Thank you very much for explanation.

Regards,
Mike

-----Original Message-----
From: Joe Witt <jo...@gmail.com> 
Sent: czwartek, 20 stycznia 2022 19:36
To: users@nifi.apache.org
Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors

Mike

Yeah a bit more than two years ago we stopped including the nifi-kite-nar by default.
https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance

That means the processors in it are no longer included by default.
Since that time though we still build and published the nar to maven artifact repos.

What we've done now is we've removed the source from our repo and will not publish the nar going forward.  That said you'll be able to keep using the already published nars to do this as you need.  Until we release a nifi 2.0 you should be safe from them breaking.

But as Chris Sampsson just replied you almost certainly want to discontinue using them anyway and switch to using the record based processors.  They are far more efficient, far more powerful, and are extremely actively developed and maintained.

Thanks

On Thu, Jan 20, 2022 at 11:32 AM Chris Sampson <ch...@naimuri.com> wrote:
>
> If the kite nar is refined then that processor would indeed no longer be present.
>
> A good alternative would be to use a Record based processor such as ConvertRecord with a CSVReader and an AvroWriter. Such processors and controller services typically offer much more powerful options than the older processors such as those in the kite nar.
>
>
> Cheers,
>
> Chris Sampson
>
> On Thu, 20 Jan 2022, 18:08 Michal Tomaszewski, <Mi...@cca.pl> wrote:
>>
>> Joe,
>>
>> Does it mean ConvertCSVToAvro will disappear too?
>>
>> Or you discontinue only a part of org.apache.nifi.processors.kite schema and the rest will be somehow moved to other schemas?
>>
>>
>>
>> Regards,
>>
>> Mike
>>
>>
>>
>>
>>
>> From: Joe Witt <jo...@gmail.com>
>> Sent: środa, 19 stycznia 2022 15:57
>> To: users@nifi.apache.org
>> Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>>
>>
>>
>> We should discontinue Kite processors from the build at all in 1.16.0.
>>
>>
>>
>> Ill file a Jira
>>
>>
>>
>> Thanks
>>
>>
>>
>> On Wed, Jan 19, 2022 at 7:47 AM David Handermann <ex...@apache.org> wrote:
>>
>> Mike,
>>
>>
>>
>> Thanks for the additional details. According to the original output, the problem appears to be in the nifi-kite-processors module.  The nifi-kite-processors module includes a dependency on hive-hcatalog-core, the version of which is based on the hive.version property.  We should be able to add an exclusion for log4j-core within that dependency definition, which will allow it to compile with Hive 3.1.2.  For the moment, if you don't need the Kite processors, you could skip building nifi-kite-nar, or you could manually add the following exclusion:
>>
>> <exclusion>
>>
>>   <groupId>org.apache.logging.log4j</groupId>
>>
>>   <artifactId>log4j-core</artifactId>
>>
>> <exclusion>
>>
>> Regards,
>>
>> David Handermann
>>
>>
>>
>> On Wed, Jan 19, 2022 at 8:27 AM Michal Tomaszewski <Mi...@cca.pl> wrote:
>>
>> Compilation with -Dhive.version=3.1.0 makes the problem.
>> mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0 is 
>> not successful.
>> We also tested -Dhive.version=3.1.2, that is most recent on Apache Hive site. Also without success.
>>
>> Please note that without this parameter probably hive2 version is compiled into nifi and HiveStreaming is not working then.
>> And hive 3 is most popular novadays.
>>
>> Regards,
>> Mike
>>
>> -----Original Message-----
>> From: Bryan Bende <bb...@gmail.com>
>> Sent: Wednesday, January 19, 2022 3:03 PM
>> To: users@nifi.apache.org
>> Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>>
>> We did ban all use of log4j-core in favor of log4j-to-slf4j...
>>
>> https://issues.apache.org/jira/browse/NIFI-9483
>>
>> With your build specifying the -D versions, it created a different classpath during your build than what existed during the normal build of the release.
>>
>> We should try to fix any issues like this though, so if you can figure out which dependency path is the issue, the fix is to add some exclusions and then to ensure that log4j-to-slf4j dependency is added.
>>
>> On Wed, Jan 19, 2022 at 8:48 AM Michal Tomaszewski <Mi...@cca.pl> wrote:
>> >
>> > OK, but there is information that log4j-core:jar:2.17.1 is blocked:
>> >
>> > [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
>> >
>> > Found Banned Dependency:
>> > org.apache.logging.log4j:log4j-core:jar:2.17.1
>> >
>> > while this version is not impacted by log4j security vulnerability:
>> >
>> > https://logging.apache.org/log4j/2.x/security.html
>> >
>> >
>> >
>> > So for sure it shouldn’t be banned.
>> >
>> >
>> >
>> > Regards,
>> >
>> > Mike
>> >
>> > From: Pierre Villard <pi...@gmail.com>
>> > Sent: Wednesday, January 19, 2022 1:11 PM
>> > To: users@nifi.apache.org
>> > Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>> >
>> >
>> >
>> > We recently changed the build to fail if it's including problematic transitive dependencies for log4j. I think those are coming with the specific versions of HBase/Hive you're using. Not a maven expert but I guess there is a way to exclude the step "enforce-banned-dependencies" from the build.
>> >
>> >
>> >
>> > Le mer. 19 janv. 2022 à 12:57, Michal Tomaszewski <Mi...@cca.pl> a écrit :
>> >
>> > Hi Edward,
>> >
>> > Full mvn dependency:tree log enclosed.
>> >
>> > We’re compiling using command:
>> >
>> > mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0
>> > -Dhbase.version=2.0.2
>> >
>> >
>> >
>> > Regards,
>> >
>> > Mike
>> >
>> >
>> >
>> > From: Edward Armes <ed...@gmail.com>
>> > Sent: Wednesday, January 19, 2022 12:34 PM
>> > To: users@nifi.apache.org
>> > Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>> >
>> >
>> >
>> > Hi Mike,
>> >
>> >
>> >
>> > Can you give the full output you get from mvn dependency:tree as we 15.2 and 3 was done to remove log4j dependences from Nifi as a safety measure due the recent log4shell issues.
>> >
>> >
>> >
>> > Thanks
>> >
>> >
>> >
>> > Edward
>> >
>> >
>> >
>> > On Wed, Jan 19, 2022 at 10:24 AM Michal Tomaszewski <Mi...@cca.pl> wrote:
>> >
>> > Hi,
>> >
>> > We are trying to compile nifi from sources.
>> >
>> > There is no problem with 1.15.1 compilation but in case of 1.15.2 and 1.15.3 there are compilation errors.
>> >
>> >
>> >
>> > Can you suggest how to solve this problem?
>> >
>> >
>> >
>> > mvn dependency:tree has no errors:
>> >
>> >
>> >
>> >
>> >
>> > $ tail log1.txt
>> >
>> > [INFO] nifi-toolkit-flowfile-repo ......................... SUCCESS 
>> > [
>> > 0.005 s]
>> >
>> > [INFO] nifi-toolkit-flowanalyzer .......................... SUCCESS 
>> > [
>> > 0.008 s]
>> >
>> > [INFO] nifi-toolkit-assembly .............................. SUCCESS 
>> > [
>> > 0.463 s]
>> >
>> > [INFO] nifi-toolkit-api ................................... SUCCESS 
>> > [
>> > 0.023 s]
>> >
>> > [INFO]
>> > -------------------------------------------------------------------
>> > ---
>> > --
>> >
>> > [INFO] BUILD SUCCESS
>> >
>> > [INFO]
>> > -------------------------------------------------------------------
>> > ---
>> > --
>> >
>> > [INFO] Total time:  02:41 min
>> >
>> > [INFO] Finished at: 2022-01-19T08:51:46+01:00
>> >
>> >
>> >
>> >
>> >
>> > Compilation of branch rel/nifi-1.15.3:
>> >
>> >
>> >
>> > [DEBUG] Adding ERROR message due to exception
>> >
>> > org.apache.maven.enforcer.rule.api.EnforcerRuleException: Found 
>> > Banned
>> > Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
>> >
>> > Use 'mvn dependency:tree' to locate the source of the banned dependencies.
>> >
>> >     at
>> > org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute
>> > (AbstractBanDependencies.java:113)
>> >
>> >     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
>> > (EnforceMojo.java:200)
>> >
>> >     at 
>> > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
>> > (DefaultBuildPluginManager.java:137)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:210)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:156)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:148)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildPro
>> > jec t (LifecycleModuleBuilder.java:117)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThre
>> > ade dBuilder$1.call (MultiThreadedBuilder.java:196)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThre
>> > ade dBuilder$1.call (MultiThreadedBuilder.java:186)
>> >
>> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> >
>> >     at java.util.concurrent.Executors$RunnableAdapter.call
>> > (Executors.java:511)
>> >
>> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> >
>> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
>> > (ThreadPoolExecutor.java:1149)
>> >
>> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
>> > (ThreadPoolExecutor.java:624)
>> >
>> >     at java.lang.Thread.run (Thread.java:748)
>> >
>> > [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
>> >
>> > Found Banned Dependency:
>> > org.apache.logging.log4j:log4j-core:jar:2.17.1
>> >
>> > Use 'mvn dependency:tree' to locate the source of the banned dependencies.
>> >
>> > [INFO]
>> >
>> >
>> >
>> > ….
>> >
>> >
>> >
>> > [INFO]
>> > -------------------------------------------------------------------
>> > ---
>> > --
>> >
>> > [ERROR] Failed to execute goal
>> > org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
>> > (enforce-banned-dependencies) on project nifi-kite-processors: Some 
>> > Enforcer rules have failed. Look above for specific messages 
>> > explaining why the rule failed. -> [Help 1]
>> >
>> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce (enforce-banned-dependencies) on project nifi-kite-processors: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:215)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:156)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:148)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildPro
>> > jec t (LifecycleModuleBuilder.java:117)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThre
>> > ade dBuilder$1.call (MultiThreadedBuilder.java:196)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThre
>> > ade dBuilder$1.call (MultiThreadedBuilder.java:186)
>> >
>> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> >
>> >     at java.util.concurrent.Executors$RunnableAdapter.call
>> > (Executors.java:511)
>> >
>> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> >
>> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
>> > (ThreadPoolExecutor.java:1149)
>> >
>> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
>> > (ThreadPoolExecutor.java:624)
>> >
>> >     at java.lang.Thread.run (Thread.java:748)
>> >
>> > Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
>> >
>> >     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
>> > (EnforceMojo.java:255)
>> >
>> >     at 
>> > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
>> > (DefaultBuildPluginManager.java:137)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:210)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:156)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:148)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildPro
>> > jec t (LifecycleModuleBuilder.java:117)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThre
>> > ade dBuilder$1.call (MultiThreadedBuilder.java:196)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThre
>> > ade dBuilder$1.call (MultiThreadedBuilder.java:186)
>> >
>> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> >
>> >     at java.util.concurrent.Executors$RunnableAdapter.call
>> > (Executors.java:511)
>> >
>> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> >
>> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
>> > (ThreadPoolExecutor.java:1149)
>> >
>> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
>> > (ThreadPoolExecutor.java:624)
>> >
>> >     at java.lang.Thread.run (Thread.java:748)
>> >
>> > [ERROR]
>> >
>> > [ERROR]
>> >
>> > [ERROR] For more information about the errors and possible solutions, please read the following articles:
>> >
>> > [ERROR] [Help 1]
>> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionExcep
>> > tio
>> > n
>> >
>> > [ERROR]
>> >
>> > [ERROR] After correcting the problems, you can resume the build 
>> > with the command
>> >
>> > [ERROR]   mvn <args> -rf :nifi-kite-processors
>> >
>> >
>> >
>> > Regards,
>> >
>> > Mike

Re: Nifi 1.15.2 and 1.15.3 compilation errors

Posted by Joe Witt <jo...@gmail.com>.
Mike

Yeah a bit more than two years ago we stopped including the
nifi-kite-nar by default.
https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance

That means the processors in it are no longer included by default.
Since that time though we still build and published the nar to maven
artifact repos.

What we've done now is we've removed the source from our repo and will
not publish the nar going forward.  That said you'll be able to keep
using the already published nars to do this as you need.  Until we
release a nifi 2.0 you should be safe from them breaking.

But as Chris Sampsson just replied you almost certainly want to
discontinue using them anyway and switch to using the record based
processors.  They are far more efficient, far more powerful, and are
extremely actively developed and maintained.

Thanks

On Thu, Jan 20, 2022 at 11:32 AM Chris Sampson
<ch...@naimuri.com> wrote:
>
> If the kite nar is refined then that processor would indeed no longer be present.
>
> A good alternative would be to use a Record based processor such as ConvertRecord with a CSVReader and an AvroWriter. Such processors and controller services typically offer much more powerful options than the older processors such as those in the kite nar.
>
>
> Cheers,
>
> Chris Sampson
>
> On Thu, 20 Jan 2022, 18:08 Michal Tomaszewski, <Mi...@cca.pl> wrote:
>>
>> Joe,
>>
>> Does it mean ConvertCSVToAvro will disappear too?
>>
>> Or you discontinue only a part of org.apache.nifi.processors.kite schema and the rest will be somehow moved to other schemas?
>>
>>
>>
>> Regards,
>>
>> Mike
>>
>>
>>
>>
>>
>> From: Joe Witt <jo...@gmail.com>
>> Sent: środa, 19 stycznia 2022 15:57
>> To: users@nifi.apache.org
>> Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>>
>>
>>
>> We should discontinue Kite processors from the build at all in 1.16.0.
>>
>>
>>
>> Ill file a Jira
>>
>>
>>
>> Thanks
>>
>>
>>
>> On Wed, Jan 19, 2022 at 7:47 AM David Handermann <ex...@apache.org> wrote:
>>
>> Mike,
>>
>>
>>
>> Thanks for the additional details. According to the original output, the problem appears to be in the nifi-kite-processors module.  The nifi-kite-processors module includes a dependency on hive-hcatalog-core, the version of which is based on the hive.version property.  We should be able to add an exclusion for log4j-core within that dependency definition, which will allow it to compile with Hive 3.1.2.  For the moment, if you don't need the Kite processors, you could skip building nifi-kite-nar, or you could manually add the following exclusion:
>>
>> <exclusion>
>>
>>   <groupId>org.apache.logging.log4j</groupId>
>>
>>   <artifactId>log4j-core</artifactId>
>>
>> <exclusion>
>>
>> Regards,
>>
>> David Handermann
>>
>>
>>
>> On Wed, Jan 19, 2022 at 8:27 AM Michal Tomaszewski <Mi...@cca.pl> wrote:
>>
>> Compilation with -Dhive.version=3.1.0 makes the problem.
>> mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0
>> is not successful.
>> We also tested -Dhive.version=3.1.2, that is most recent on Apache Hive site. Also without success.
>>
>> Please note that without this parameter probably hive2 version is compiled into nifi and HiveStreaming is not working then.
>> And hive 3 is most popular novadays.
>>
>> Regards,
>> Mike
>>
>> -----Original Message-----
>> From: Bryan Bende <bb...@gmail.com>
>> Sent: Wednesday, January 19, 2022 3:03 PM
>> To: users@nifi.apache.org
>> Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>>
>> We did ban all use of log4j-core in favor of log4j-to-slf4j...
>>
>> https://issues.apache.org/jira/browse/NIFI-9483
>>
>> With your build specifying the -D versions, it created a different classpath during your build than what existed during the normal build of the release.
>>
>> We should try to fix any issues like this though, so if you can figure out which dependency path is the issue, the fix is to add some exclusions and then to ensure that log4j-to-slf4j dependency is added.
>>
>> On Wed, Jan 19, 2022 at 8:48 AM Michal Tomaszewski <Mi...@cca.pl> wrote:
>> >
>> > OK, but there is information that log4j-core:jar:2.17.1 is blocked:
>> >
>> > [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
>> >
>> > Found Banned Dependency:
>> > org.apache.logging.log4j:log4j-core:jar:2.17.1
>> >
>> > while this version is not impacted by log4j security vulnerability:
>> >
>> > https://logging.apache.org/log4j/2.x/security.html
>> >
>> >
>> >
>> > So for sure it shouldn’t be banned.
>> >
>> >
>> >
>> > Regards,
>> >
>> > Mike
>> >
>> > From: Pierre Villard <pi...@gmail.com>
>> > Sent: Wednesday, January 19, 2022 1:11 PM
>> > To: users@nifi.apache.org
>> > Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>> >
>> >
>> >
>> > We recently changed the build to fail if it's including problematic transitive dependencies for log4j. I think those are coming with the specific versions of HBase/Hive you're using. Not a maven expert but I guess there is a way to exclude the step "enforce-banned-dependencies" from the build.
>> >
>> >
>> >
>> > Le mer. 19 janv. 2022 à 12:57, Michal Tomaszewski <Mi...@cca.pl> a écrit :
>> >
>> > Hi Edward,
>> >
>> > Full mvn dependency:tree log enclosed.
>> >
>> > We’re compiling using command:
>> >
>> > mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0
>> > -Dhbase.version=2.0.2
>> >
>> >
>> >
>> > Regards,
>> >
>> > Mike
>> >
>> >
>> >
>> > From: Edward Armes <ed...@gmail.com>
>> > Sent: Wednesday, January 19, 2022 12:34 PM
>> > To: users@nifi.apache.org
>> > Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>> >
>> >
>> >
>> > Hi Mike,
>> >
>> >
>> >
>> > Can you give the full output you get from mvn dependency:tree as we 15.2 and 3 was done to remove log4j dependences from Nifi as a safety measure due the recent log4shell issues.
>> >
>> >
>> >
>> > Thanks
>> >
>> >
>> >
>> > Edward
>> >
>> >
>> >
>> > On Wed, Jan 19, 2022 at 10:24 AM Michal Tomaszewski <Mi...@cca.pl> wrote:
>> >
>> > Hi,
>> >
>> > We are trying to compile nifi from sources.
>> >
>> > There is no problem with 1.15.1 compilation but in case of 1.15.2 and 1.15.3 there are compilation errors.
>> >
>> >
>> >
>> > Can you suggest how to solve this problem?
>> >
>> >
>> >
>> > mvn dependency:tree has no errors:
>> >
>> >
>> >
>> >
>> >
>> > $ tail log1.txt
>> >
>> > [INFO] nifi-toolkit-flowfile-repo ......................... SUCCESS [
>> > 0.005 s]
>> >
>> > [INFO] nifi-toolkit-flowanalyzer .......................... SUCCESS [
>> > 0.008 s]
>> >
>> > [INFO] nifi-toolkit-assembly .............................. SUCCESS [
>> > 0.463 s]
>> >
>> > [INFO] nifi-toolkit-api ................................... SUCCESS [
>> > 0.023 s]
>> >
>> > [INFO]
>> > ----------------------------------------------------------------------
>> > --
>> >
>> > [INFO] BUILD SUCCESS
>> >
>> > [INFO]
>> > ----------------------------------------------------------------------
>> > --
>> >
>> > [INFO] Total time:  02:41 min
>> >
>> > [INFO] Finished at: 2022-01-19T08:51:46+01:00
>> >
>> >
>> >
>> >
>> >
>> > Compilation of branch rel/nifi-1.15.3:
>> >
>> >
>> >
>> > [DEBUG] Adding ERROR message due to exception
>> >
>> > org.apache.maven.enforcer.rule.api.EnforcerRuleException: Found Banned
>> > Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
>> >
>> > Use 'mvn dependency:tree' to locate the source of the banned dependencies.
>> >
>> >     at
>> > org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute
>> > (AbstractBanDependencies.java:113)
>> >
>> >     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
>> > (EnforceMojo.java:200)
>> >
>> >     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
>> > (DefaultBuildPluginManager.java:137)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:210)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:156)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:148)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
>> > t (LifecycleModuleBuilder.java:117)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
>> > dBuilder$1.call (MultiThreadedBuilder.java:196)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
>> > dBuilder$1.call (MultiThreadedBuilder.java:186)
>> >
>> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> >
>> >     at java.util.concurrent.Executors$RunnableAdapter.call
>> > (Executors.java:511)
>> >
>> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> >
>> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
>> > (ThreadPoolExecutor.java:1149)
>> >
>> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
>> > (ThreadPoolExecutor.java:624)
>> >
>> >     at java.lang.Thread.run (Thread.java:748)
>> >
>> > [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
>> >
>> > Found Banned Dependency:
>> > org.apache.logging.log4j:log4j-core:jar:2.17.1
>> >
>> > Use 'mvn dependency:tree' to locate the source of the banned dependencies.
>> >
>> > [INFO]
>> >
>> >
>> >
>> > ….
>> >
>> >
>> >
>> > [INFO]
>> > ----------------------------------------------------------------------
>> > --
>> >
>> > [ERROR] Failed to execute goal
>> > org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
>> > (enforce-banned-dependencies) on project nifi-kite-processors: Some
>> > Enforcer rules have failed. Look above for specific messages
>> > explaining why the rule failed. -> [Help 1]
>> >
>> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce (enforce-banned-dependencies) on project nifi-kite-processors: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:215)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:156)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:148)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
>> > t (LifecycleModuleBuilder.java:117)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
>> > dBuilder$1.call (MultiThreadedBuilder.java:196)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
>> > dBuilder$1.call (MultiThreadedBuilder.java:186)
>> >
>> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> >
>> >     at java.util.concurrent.Executors$RunnableAdapter.call
>> > (Executors.java:511)
>> >
>> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> >
>> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
>> > (ThreadPoolExecutor.java:1149)
>> >
>> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
>> > (ThreadPoolExecutor.java:624)
>> >
>> >     at java.lang.Thread.run (Thread.java:748)
>> >
>> > Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
>> >
>> >     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
>> > (EnforceMojo.java:255)
>> >
>> >     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
>> > (DefaultBuildPluginManager.java:137)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:210)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:156)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:148)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
>> > t (LifecycleModuleBuilder.java:117)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
>> > dBuilder$1.call (MultiThreadedBuilder.java:196)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
>> > dBuilder$1.call (MultiThreadedBuilder.java:186)
>> >
>> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> >
>> >     at java.util.concurrent.Executors$RunnableAdapter.call
>> > (Executors.java:511)
>> >
>> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> >
>> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
>> > (ThreadPoolExecutor.java:1149)
>> >
>> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
>> > (ThreadPoolExecutor.java:624)
>> >
>> >     at java.lang.Thread.run (Thread.java:748)
>> >
>> > [ERROR]
>> >
>> > [ERROR]
>> >
>> > [ERROR] For more information about the errors and possible solutions, please read the following articles:
>> >
>> > [ERROR] [Help 1]
>> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionExceptio
>> > n
>> >
>> > [ERROR]
>> >
>> > [ERROR] After correcting the problems, you can resume the build with
>> > the command
>> >
>> > [ERROR]   mvn <args> -rf :nifi-kite-processors
>> >
>> >
>> >
>> > Regards,
>> >
>> > Mike

Re: Nifi 1.15.2 and 1.15.3 compilation errors

Posted by Chris Sampson <ch...@naimuri.com>.
If the kite nar is refined then that processor would indeed no longer be
present.

A good alternative would be to use a Record based processor such as
ConvertRecord with a CSVReader and an AvroWriter. Such processors and
controller services typically offer much more powerful options than the
older processors such as those in the kite nar.


Cheers,

Chris Sampson

On Thu, 20 Jan 2022, 18:08 Michal Tomaszewski, <Mi...@cca.pl>
wrote:

> Joe,
>
> Does it mean ConvertCSVToAvro will disappear too?
>
> Or you discontinue only a part of org.apache.nifi.processors.kite schema
> and the rest will be somehow moved to other schemas?
>
>
>
> Regards,
>
> Mike
>
>
>
>
>
> *From:* Joe Witt <jo...@gmail.com>
> *Sent:* środa, 19 stycznia 2022 15:57
> *To:* users@nifi.apache.org
> *Subject:* Re: Nifi 1.15.2 and 1.15.3 compilation errors
>
>
>
> We should discontinue Kite processors from the build at all in 1.16.0.
>
>
>
> Ill file a Jira
>
>
>
> Thanks
>
>
>
> On Wed, Jan 19, 2022 at 7:47 AM David Handermann <
> exceptionfactory@apache.org> wrote:
>
> Mike,
>
>
>
> Thanks for the additional details. According to the original output, the
> problem appears to be in the nifi-kite-processors module.  The
> nifi-kite-processors module includes a dependency on hive-hcatalog-core,
> the version of which is based on the hive.version property.  We should be
> able to add an exclusion for log4j-core within that dependency definition,
> which will allow it to compile with Hive 3.1.2.  For the moment, if you
> don't need the Kite processors, you could skip building nifi-kite-nar, or
> you could manually add the following exclusion:
>
> <exclusion>
>
>   <groupId>org.apache.logging.log4j</groupId>
>
>   <artifactId>log4j-core</artifactId>
>
> <exclusion>
>
> Regards,
>
> David Handermann
>
>
>
> On Wed, Jan 19, 2022 at 8:27 AM Michal Tomaszewski <
> Michal.Tomaszewski@cca.pl> wrote:
>
> Compilation with -Dhive.version=3.1.0 makes the problem.
> mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0
> is not successful.
> We also tested -Dhive.version=3.1.2, that is most recent on Apache Hive
> site. Also without success.
>
> Please note that without this parameter probably hive2 version is compiled
> into nifi and HiveStreaming is not working then.
> And hive 3 is most popular novadays.
>
> Regards,
> Mike
>
> -----Original Message-----
> From: Bryan Bende <bb...@gmail.com>
> Sent: Wednesday, January 19, 2022 3:03 PM
> To: users@nifi.apache.org
> Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>
> We did ban all use of log4j-core in favor of log4j-to-slf4j...
>
> https://issues.apache.org/jira/browse/NIFI-9483
>
> With your build specifying the -D versions, it created a different
> classpath during your build than what existed during the normal build of
> the release.
>
> We should try to fix any issues like this though, so if you can figure out
> which dependency path is the issue, the fix is to add some exclusions and
> then to ensure that log4j-to-slf4j dependency is added.
>
> On Wed, Jan 19, 2022 at 8:48 AM Michal Tomaszewski <
> Michal.Tomaszewski@cca.pl> wrote:
> >
> > OK, but there is information that log4j-core:jar:2.17.1 is blocked:
> >
> > [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies
> failed with message:
> >
> > Found Banned Dependency:
> > org.apache.logging.log4j:log4j-core:jar:2.17.1
> >
> > while this version is not impacted by log4j security vulnerability:
> >
> > https://logging.apache.org/log4j/2.x/security.html
> >
> >
> >
> > So for sure it shouldn’t be banned.
> >
> >
> >
> > Regards,
> >
> > Mike
> >
> > From: Pierre Villard <pi...@gmail.com>
> > Sent: Wednesday, January 19, 2022 1:11 PM
> > To: users@nifi.apache.org
> > Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
> >
> >
> >
> > We recently changed the build to fail if it's including problematic
> transitive dependencies for log4j. I think those are coming with the
> specific versions of HBase/Hive you're using. Not a maven expert but I
> guess there is a way to exclude the step "enforce-banned-dependencies" from
> the build.
> >
> >
> >
> > Le mer. 19 janv. 2022 à 12:57, Michal Tomaszewski <
> Michal.Tomaszewski@cca.pl> a écrit :
> >
> > Hi Edward,
> >
> > Full mvn dependency:tree log enclosed.
> >
> > We’re compiling using command:
> >
> > mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0
> > -Dhbase.version=2.0.2
> >
> >
> >
> > Regards,
> >
> > Mike
> >
> >
> >
> > From: Edward Armes <ed...@gmail.com>
> > Sent: Wednesday, January 19, 2022 12:34 PM
> > To: users@nifi.apache.org
> > Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
> >
> >
> >
> > Hi Mike,
> >
> >
> >
> > Can you give the full output you get from mvn dependency:tree as we 15.2
> and 3 was done to remove log4j dependences from Nifi as a safety measure
> due the recent log4shell issues.
> >
> >
> >
> > Thanks
> >
> >
> >
> > Edward
> >
> >
> >
> > On Wed, Jan 19, 2022 at 10:24 AM Michal Tomaszewski <
> Michal.Tomaszewski@cca.pl> wrote:
> >
> > Hi,
> >
> > We are trying to compile nifi from sources.
> >
> > There is no problem with 1.15.1 compilation but in case of 1.15.2 and
> 1.15.3 there are compilation errors.
> >
> >
> >
> > Can you suggest how to solve this problem?
> >
> >
> >
> > mvn dependency:tree has no errors:
> >
> >
> >
> >
> >
> > $ tail log1.txt
> >
> > [INFO] nifi-toolkit-flowfile-repo ......................... SUCCESS [
> > 0.005 s]
> >
> > [INFO] nifi-toolkit-flowanalyzer .......................... SUCCESS [
> > 0.008 s]
> >
> > [INFO] nifi-toolkit-assembly .............................. SUCCESS [
> > 0.463 s]
> >
> > [INFO] nifi-toolkit-api ................................... SUCCESS [
> > 0.023 s]
> >
> > [INFO]
> > ----------------------------------------------------------------------
> > --
> >
> > [INFO] BUILD SUCCESS
> >
> > [INFO]
> > ----------------------------------------------------------------------
> > --
> >
> > [INFO] Total time:  02:41 min
> >
> > [INFO] Finished at: 2022-01-19T08:51:46+01:00
> >
> >
> >
> >
> >
> > Compilation of branch rel/nifi-1.15.3:
> >
> >
> >
> > [DEBUG] Adding ERROR message due to exception
> >
> > org.apache.maven.enforcer.rule.api.EnforcerRuleException: Found Banned
> > Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
> >
> > Use 'mvn dependency:tree' to locate the source of the banned
> dependencies.
> >
> >     at
> > org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute
> > (AbstractBanDependencies.java:113)
> >
> >     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
> > (EnforceMojo.java:200)
> >
> >     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> > (DefaultBuildPluginManager.java:137)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:210)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:156)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:148)
> >
> >     at
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> > t (LifecycleModuleBuilder.java:117)
> >
> >     at
> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> > dBuilder$1.call (MultiThreadedBuilder.java:196)
> >
> >     at
> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> > dBuilder$1.call (MultiThreadedBuilder.java:186)
> >
> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >
> >     at java.util.concurrent.Executors$RunnableAdapter.call
> > (Executors.java:511)
> >
> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >
> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
> > (ThreadPoolExecutor.java:1149)
> >
> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> > (ThreadPoolExecutor.java:624)
> >
> >     at java.lang.Thread.run (Thread.java:748)
> >
> > [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies
> failed with message:
> >
> > Found Banned Dependency:
> > org.apache.logging.log4j:log4j-core:jar:2.17.1
> >
> > Use 'mvn dependency:tree' to locate the source of the banned
> dependencies.
> >
> > [INFO]
> >
> >
> >
> > ….
> >
> >
> >
> > [INFO]
> > ----------------------------------------------------------------------
> > --
> >
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
> > (enforce-banned-dependencies) on project nifi-kite-processors: Some
> > Enforcer rules have failed. Look above for specific messages
> > explaining why the rule failed. -> [Help 1]
> >
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
> (enforce-banned-dependencies) on project nifi-kite-processors: Some
> Enforcer rules have failed. Look above for specific messages explaining why
> the rule failed.
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:215)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:156)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:148)
> >
> >     at
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> > t (LifecycleModuleBuilder.java:117)
> >
> >     at
> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> > dBuilder$1.call (MultiThreadedBuilder.java:196)
> >
> >     at
> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> > dBuilder$1.call (MultiThreadedBuilder.java:186)
> >
> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >
> >     at java.util.concurrent.Executors$RunnableAdapter.call
> > (Executors.java:511)
> >
> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >
> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
> > (ThreadPoolExecutor.java:1149)
> >
> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> > (ThreadPoolExecutor.java:624)
> >
> >     at java.lang.Thread.run (Thread.java:748)
> >
> > Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer
> rules have failed. Look above for specific messages explaining why the rule
> failed.
> >
> >     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
> > (EnforceMojo.java:255)
> >
> >     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> > (DefaultBuildPluginManager.java:137)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:210)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:156)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:148)
> >
> >     at
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> > t (LifecycleModuleBuilder.java:117)
> >
> >     at
> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> > dBuilder$1.call (MultiThreadedBuilder.java:196)
> >
> >     at
> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> > dBuilder$1.call (MultiThreadedBuilder.java:186)
> >
> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >
> >     at java.util.concurrent.Executors$RunnableAdapter.call
> > (Executors.java:511)
> >
> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >
> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
> > (ThreadPoolExecutor.java:1149)
> >
> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> > (ThreadPoolExecutor.java:624)
> >
> >     at java.lang.Thread.run (Thread.java:748)
> >
> > [ERROR]
> >
> > [ERROR]
> >
> > [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> >
> > [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionExceptio
> > n
> >
> > [ERROR]
> >
> > [ERROR] After correcting the problems, you can resume the build with
> > the command
> >
> > [ERROR]   mvn <args> -rf :nifi-kite-processors
> >
> >
> >
> > Regards,
> >
> > Mike
>
>

RE: Nifi 1.15.2 and 1.15.3 compilation errors

Posted by Michal Tomaszewski <Mi...@cca.pl>.
Joe,
Does it mean ConvertCSVToAvro will disappear too?
Or you discontinue only a part of org.apache.nifi.processors.kite schema and the rest will be somehow moved to other schemas?

Regards,
Mike


From: Joe Witt <jo...@gmail.com>
Sent: środa, 19 stycznia 2022 15:57
To: users@nifi.apache.org
Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors

We should discontinue Kite processors from the build at all in 1.16.0.

Ill file a Jira

Thanks

On Wed, Jan 19, 2022 at 7:47 AM David Handermann <ex...@apache.org>> wrote:
Mike,

Thanks for the additional details. According to the original output, the problem appears to be in the nifi-kite-processors module.  The nifi-kite-processors module includes a dependency on hive-hcatalog-core, the version of which is based on the hive.version property.  We should be able to add an exclusion for log4j-core within that dependency definition, which will allow it to compile with Hive 3.1.2.  For the moment, if you don't need the Kite processors, you could skip building nifi-kite-nar, or you could manually add the following exclusion:
<exclusion>
  <groupId>org.apache.logging.log4j</groupId>
  <artifactId>log4j-core</artifactId>
<exclusion>
Regards,
David Handermann

On Wed, Jan 19, 2022 at 8:27 AM Michal Tomaszewski <Mi...@cca.pl>> wrote:
Compilation with -Dhive.version=3.1.0 makes the problem.
mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0
is not successful.
We also tested -Dhive.version=3.1.2, that is most recent on Apache Hive site. Also without success.

Please note that without this parameter probably hive2 version is compiled into nifi and HiveStreaming is not working then.
And hive 3 is most popular novadays.

Regards,
Mike

-----Original Message-----
From: Bryan Bende <bb...@gmail.com>>
Sent: Wednesday, January 19, 2022 3:03 PM
To: users@nifi.apache.org<ma...@nifi.apache.org>
Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors

We did ban all use of log4j-core in favor of log4j-to-slf4j...

https://issues.apache.org/jira/browse/NIFI-9483

With your build specifying the -D versions, it created a different classpath during your build than what existed during the normal build of the release.

We should try to fix any issues like this though, so if you can figure out which dependency path is the issue, the fix is to add some exclusions and then to ensure that log4j-to-slf4j dependency is added.

On Wed, Jan 19, 2022 at 8:48 AM Michal Tomaszewski <Mi...@cca.pl>> wrote:
>
> OK, but there is information that log4j-core:jar:2.17.1 is blocked:
>
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
>
> Found Banned Dependency:
> org.apache.logging.log4j:log4j-core:jar:2.17.1
>
> while this version is not impacted by log4j security vulnerability:
>
> https://logging.apache.org/log4j/2.x/security.html
>
>
>
> So for sure it shouldn’t be banned.
>
>
>
> Regards,
>
> Mike
>
> From: Pierre Villard <pi...@gmail.com>>
> Sent: Wednesday, January 19, 2022 1:11 PM
> To: users@nifi.apache.org<ma...@nifi.apache.org>
> Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>
>
>
> We recently changed the build to fail if it's including problematic transitive dependencies for log4j. I think those are coming with the specific versions of HBase/Hive you're using. Not a maven expert but I guess there is a way to exclude the step "enforce-banned-dependencies" from the build.
>
>
>
> Le mer. 19 janv. 2022 à 12:57, Michal Tomaszewski <Mi...@cca.pl>> a écrit :
>
> Hi Edward,
>
> Full mvn dependency:tree log enclosed.
>
> We’re compiling using command:
>
> mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0
> -Dhbase.version=2.0.2
>
>
>
> Regards,
>
> Mike
>
>
>
> From: Edward Armes <ed...@gmail.com>>
> Sent: Wednesday, January 19, 2022 12:34 PM
> To: users@nifi.apache.org<ma...@nifi.apache.org>
> Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>
>
>
> Hi Mike,
>
>
>
> Can you give the full output you get from mvn dependency:tree as we 15.2 and 3 was done to remove log4j dependences from Nifi as a safety measure due the recent log4shell issues.
>
>
>
> Thanks
>
>
>
> Edward
>
>
>
> On Wed, Jan 19, 2022 at 10:24 AM Michal Tomaszewski <Mi...@cca.pl>> wrote:
>
> Hi,
>
> We are trying to compile nifi from sources.
>
> There is no problem with 1.15.1 compilation but in case of 1.15.2 and 1.15.3 there are compilation errors.
>
>
>
> Can you suggest how to solve this problem?
>
>
>
> mvn dependency:tree has no errors:
>
>
>
>
>
> $ tail log1.txt
>
> [INFO] nifi-toolkit-flowfile-repo ......................... SUCCESS [
> 0.005 s]
>
> [INFO] nifi-toolkit-flowanalyzer .......................... SUCCESS [
> 0.008 s]
>
> [INFO] nifi-toolkit-assembly .............................. SUCCESS [
> 0.463 s]
>
> [INFO] nifi-toolkit-api ................................... SUCCESS [
> 0.023 s]
>
> [INFO]
> ----------------------------------------------------------------------
> --
>
> [INFO] BUILD SUCCESS
>
> [INFO]
> ----------------------------------------------------------------------
> --
>
> [INFO] Total time:  02:41 min
>
> [INFO] Finished at: 2022-01-19T08:51:46+01:00
>
>
>
>
>
> Compilation of branch rel/nifi-1.15.3:
>
>
>
> [DEBUG] Adding ERROR message due to exception
>
> org.apache.maven.enforcer.rule.api.EnforcerRuleException: Found Banned
> Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
>
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
>
>     at
> org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute
> (AbstractBanDependencies.java:113)
>
>     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
> (EnforceMojo.java:200)
>
>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
>
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> t (LifecycleModuleBuilder.java:117)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> dBuilder$1.call (MultiThreadedBuilder.java:196)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> dBuilder$1.call (MultiThreadedBuilder.java:186)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:511)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1149)
>
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:624)
>
>     at java.lang.Thread.run (Thread.java:748)
>
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
>
> Found Banned Dependency:
> org.apache.logging.log4j:log4j-core:jar:2.17.1
>
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
>
> [INFO]
>
>
>
> ….
>
>
>
> [INFO]
> ----------------------------------------------------------------------
> --
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
> (enforce-banned-dependencies) on project nifi-kite-processors: Some
> Enforcer rules have failed. Look above for specific messages
> explaining why the rule failed. -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce (enforce-banned-dependencies) on project nifi-kite-processors: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
>
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> t (LifecycleModuleBuilder.java:117)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> dBuilder$1.call (MultiThreadedBuilder.java:196)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> dBuilder$1.call (MultiThreadedBuilder.java:186)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:511)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1149)
>
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:624)
>
>     at java.lang.Thread.run (Thread.java:748)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
>
>     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
> (EnforceMojo.java:255)
>
>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
>
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> t (LifecycleModuleBuilder.java:117)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> dBuilder$1.call (MultiThreadedBuilder.java:196)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> dBuilder$1.call (MultiThreadedBuilder.java:186)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:511)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1149)
>
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:624)
>
>     at java.lang.Thread.run (Thread.java:748)
>
> [ERROR]
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
>
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionExceptio
> n
>
> [ERROR]
>
> [ERROR] After correcting the problems, you can resume the build with
> the command
>
> [ERROR]   mvn <args> -rf :nifi-kite-processors
>
>
>
> Regards,
>
> Mike

Re: Nifi 1.15.2 and 1.15.3 compilation errors

Posted by Joe Witt <jo...@gmail.com>.
We should discontinue Kite processors from the build at all in 1.16.0.

Ill file a Jira

Thanks

On Wed, Jan 19, 2022 at 7:47 AM David Handermann <
exceptionfactory@apache.org> wrote:

> Mike,
>
> Thanks for the additional details. According to the original output, the
> problem appears to be in the nifi-kite-processors module.  The
> nifi-kite-processors module includes a dependency on hive-hcatalog-core,
> the version of which is based on the hive.version property.  We should be
> able to add an exclusion for log4j-core within that dependency definition,
> which will allow it to compile with Hive 3.1.2.  For the moment, if you
> don't need the Kite processors, you could skip building nifi-kite-nar, or
> you could manually add the following exclusion:
>
> <exclusion>
>   <groupId>org.apache.logging.log4j</groupId>
>   <artifactId>log4j-core</artifactId>
> <exclusion>
>
> Regards,
> David Handermann
>
> On Wed, Jan 19, 2022 at 8:27 AM Michal Tomaszewski <
> Michal.Tomaszewski@cca.pl> wrote:
>
>> Compilation with -Dhive.version=3.1.0 makes the problem.
>> mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0
>> is not successful.
>> We also tested -Dhive.version=3.1.2, that is most recent on Apache Hive
>> site. Also without success.
>>
>> Please note that without this parameter probably hive2 version is
>> compiled into nifi and HiveStreaming is not working then.
>> And hive 3 is most popular novadays.
>>
>> Regards,
>> Mike
>>
>> -----Original Message-----
>> From: Bryan Bende <bb...@gmail.com>
>> Sent: Wednesday, January 19, 2022 3:03 PM
>> To: users@nifi.apache.org
>> Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>>
>> We did ban all use of log4j-core in favor of log4j-to-slf4j...
>>
>> https://issues.apache.org/jira/browse/NIFI-9483
>>
>> With your build specifying the -D versions, it created a different
>> classpath during your build than what existed during the normal build of
>> the release.
>>
>> We should try to fix any issues like this though, so if you can figure
>> out which dependency path is the issue, the fix is to add some exclusions
>> and then to ensure that log4j-to-slf4j dependency is added.
>>
>> On Wed, Jan 19, 2022 at 8:48 AM Michal Tomaszewski <
>> Michal.Tomaszewski@cca.pl> wrote:
>> >
>> > OK, but there is information that log4j-core:jar:2.17.1 is blocked:
>> >
>> > [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies
>> failed with message:
>> >
>> > Found Banned Dependency:
>> > org.apache.logging.log4j:log4j-core:jar:2.17.1
>> >
>> > while this version is not impacted by log4j security vulnerability:
>> >
>> > https://logging.apache.org/log4j/2.x/security.html
>> >
>> >
>> >
>> > So for sure it shouldn’t be banned.
>> >
>> >
>> >
>> > Regards,
>> >
>> > Mike
>> >
>> > From: Pierre Villard <pi...@gmail.com>
>> > Sent: Wednesday, January 19, 2022 1:11 PM
>> > To: users@nifi.apache.org
>> > Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>> >
>> >
>> >
>> > We recently changed the build to fail if it's including problematic
>> transitive dependencies for log4j. I think those are coming with the
>> specific versions of HBase/Hive you're using. Not a maven expert but I
>> guess there is a way to exclude the step "enforce-banned-dependencies" from
>> the build.
>> >
>> >
>> >
>> > Le mer. 19 janv. 2022 à 12:57, Michal Tomaszewski <
>> Michal.Tomaszewski@cca.pl> a écrit :
>> >
>> > Hi Edward,
>> >
>> > Full mvn dependency:tree log enclosed.
>> >
>> > We’re compiling using command:
>> >
>> > mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0
>> > -Dhbase.version=2.0.2
>> >
>> >
>> >
>> > Regards,
>> >
>> > Mike
>> >
>> >
>> >
>> > From: Edward Armes <ed...@gmail.com>
>> > Sent: Wednesday, January 19, 2022 12:34 PM
>> > To: users@nifi.apache.org
>> > Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>> >
>> >
>> >
>> > Hi Mike,
>> >
>> >
>> >
>> > Can you give the full output you get from mvn dependency:tree as we
>> 15.2 and 3 was done to remove log4j dependences from Nifi as a safety
>> measure due the recent log4shell issues.
>> >
>> >
>> >
>> > Thanks
>> >
>> >
>> >
>> > Edward
>> >
>> >
>> >
>> > On Wed, Jan 19, 2022 at 10:24 AM Michal Tomaszewski <
>> Michal.Tomaszewski@cca.pl> wrote:
>> >
>> > Hi,
>> >
>> > We are trying to compile nifi from sources.
>> >
>> > There is no problem with 1.15.1 compilation but in case of 1.15.2 and
>> 1.15.3 there are compilation errors.
>> >
>> >
>> >
>> > Can you suggest how to solve this problem?
>> >
>> >
>> >
>> > mvn dependency:tree has no errors:
>> >
>> >
>> >
>> >
>> >
>> > $ tail log1.txt
>> >
>> > [INFO] nifi-toolkit-flowfile-repo ......................... SUCCESS [
>> > 0.005 s]
>> >
>> > [INFO] nifi-toolkit-flowanalyzer .......................... SUCCESS [
>> > 0.008 s]
>> >
>> > [INFO] nifi-toolkit-assembly .............................. SUCCESS [
>> > 0.463 s]
>> >
>> > [INFO] nifi-toolkit-api ................................... SUCCESS [
>> > 0.023 s]
>> >
>> > [INFO]
>> > ----------------------------------------------------------------------
>> > --
>> >
>> > [INFO] BUILD SUCCESS
>> >
>> > [INFO]
>> > ----------------------------------------------------------------------
>> > --
>> >
>> > [INFO] Total time:  02:41 min
>> >
>> > [INFO] Finished at: 2022-01-19T08:51:46+01:00
>> >
>> >
>> >
>> >
>> >
>> > Compilation of branch rel/nifi-1.15.3:
>> >
>> >
>> >
>> > [DEBUG] Adding ERROR message due to exception
>> >
>> > org.apache.maven.enforcer.rule.api.EnforcerRuleException: Found Banned
>> > Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
>> >
>> > Use 'mvn dependency:tree' to locate the source of the banned
>> dependencies.
>> >
>> >     at
>> > org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute
>> > (AbstractBanDependencies.java:113)
>> >
>> >     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
>> > (EnforceMojo.java:200)
>> >
>> >     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
>> > (DefaultBuildPluginManager.java:137)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:210)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:156)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:148)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
>> > t (LifecycleModuleBuilder.java:117)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
>> > dBuilder$1.call (MultiThreadedBuilder.java:196)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
>> > dBuilder$1.call (MultiThreadedBuilder.java:186)
>> >
>> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> >
>> >     at java.util.concurrent.Executors$RunnableAdapter.call
>> > (Executors.java:511)
>> >
>> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> >
>> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
>> > (ThreadPoolExecutor.java:1149)
>> >
>> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
>> > (ThreadPoolExecutor.java:624)
>> >
>> >     at java.lang.Thread.run (Thread.java:748)
>> >
>> > [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies
>> failed with message:
>> >
>> > Found Banned Dependency:
>> > org.apache.logging.log4j:log4j-core:jar:2.17.1
>> >
>> > Use 'mvn dependency:tree' to locate the source of the banned
>> dependencies.
>> >
>> > [INFO]
>> >
>> >
>> >
>> > ….
>> >
>> >
>> >
>> > [INFO]
>> > ----------------------------------------------------------------------
>> > --
>> >
>> > [ERROR] Failed to execute goal
>> > org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
>> > (enforce-banned-dependencies) on project nifi-kite-processors: Some
>> > Enforcer rules have failed. Look above for specific messages
>> > explaining why the rule failed. -> [Help 1]
>> >
>> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>> execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
>> (enforce-banned-dependencies) on project nifi-kite-processors: Some
>> Enforcer rules have failed. Look above for specific messages explaining why
>> the rule failed.
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:215)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:156)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:148)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
>> > t (LifecycleModuleBuilder.java:117)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
>> > dBuilder$1.call (MultiThreadedBuilder.java:196)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
>> > dBuilder$1.call (MultiThreadedBuilder.java:186)
>> >
>> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> >
>> >     at java.util.concurrent.Executors$RunnableAdapter.call
>> > (Executors.java:511)
>> >
>> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> >
>> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
>> > (ThreadPoolExecutor.java:1149)
>> >
>> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
>> > (ThreadPoolExecutor.java:624)
>> >
>> >     at java.lang.Thread.run (Thread.java:748)
>> >
>> > Caused by: org.apache.maven.plugin.MojoExecutionException: Some
>> Enforcer rules have failed. Look above for specific messages explaining why
>> the rule failed.
>> >
>> >     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
>> > (EnforceMojo.java:255)
>> >
>> >     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
>> > (DefaultBuildPluginManager.java:137)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:210)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:156)
>> >
>> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
>> > (MojoExecutor.java:148)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
>> > t (LifecycleModuleBuilder.java:117)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
>> > dBuilder$1.call (MultiThreadedBuilder.java:196)
>> >
>> >     at
>> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
>> > dBuilder$1.call (MultiThreadedBuilder.java:186)
>> >
>> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> >
>> >     at java.util.concurrent.Executors$RunnableAdapter.call
>> > (Executors.java:511)
>> >
>> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>> >
>> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
>> > (ThreadPoolExecutor.java:1149)
>> >
>> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
>> > (ThreadPoolExecutor.java:624)
>> >
>> >     at java.lang.Thread.run (Thread.java:748)
>> >
>> > [ERROR]
>> >
>> > [ERROR]
>> >
>> > [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> >
>> > [ERROR] [Help 1]
>> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionExceptio
>> > n
>> >
>> > [ERROR]
>> >
>> > [ERROR] After correcting the problems, you can resume the build with
>> > the command
>> >
>> > [ERROR]   mvn <args> -rf :nifi-kite-processors
>> >
>> >
>> >
>> > Regards,
>> >
>> > Mike
>>
>

Re: Nifi 1.15.2 and 1.15.3 compilation errors

Posted by David Handermann <ex...@apache.org>.
Mike,

Thanks for the additional details. According to the original output, the
problem appears to be in the nifi-kite-processors module.  The
nifi-kite-processors module includes a dependency on hive-hcatalog-core,
the version of which is based on the hive.version property.  We should be
able to add an exclusion for log4j-core within that dependency definition,
which will allow it to compile with Hive 3.1.2.  For the moment, if you
don't need the Kite processors, you could skip building nifi-kite-nar, or
you could manually add the following exclusion:

<exclusion>
  <groupId>org.apache.logging.log4j</groupId>
  <artifactId>log4j-core</artifactId>
<exclusion>

Regards,
David Handermann

On Wed, Jan 19, 2022 at 8:27 AM Michal Tomaszewski <
Michal.Tomaszewski@cca.pl> wrote:

> Compilation with -Dhive.version=3.1.0 makes the problem.
> mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0
> is not successful.
> We also tested -Dhive.version=3.1.2, that is most recent on Apache Hive
> site. Also without success.
>
> Please note that without this parameter probably hive2 version is compiled
> into nifi and HiveStreaming is not working then.
> And hive 3 is most popular novadays.
>
> Regards,
> Mike
>
> -----Original Message-----
> From: Bryan Bende <bb...@gmail.com>
> Sent: Wednesday, January 19, 2022 3:03 PM
> To: users@nifi.apache.org
> Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>
> We did ban all use of log4j-core in favor of log4j-to-slf4j...
>
> https://issues.apache.org/jira/browse/NIFI-9483
>
> With your build specifying the -D versions, it created a different
> classpath during your build than what existed during the normal build of
> the release.
>
> We should try to fix any issues like this though, so if you can figure out
> which dependency path is the issue, the fix is to add some exclusions and
> then to ensure that log4j-to-slf4j dependency is added.
>
> On Wed, Jan 19, 2022 at 8:48 AM Michal Tomaszewski <
> Michal.Tomaszewski@cca.pl> wrote:
> >
> > OK, but there is information that log4j-core:jar:2.17.1 is blocked:
> >
> > [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies
> failed with message:
> >
> > Found Banned Dependency:
> > org.apache.logging.log4j:log4j-core:jar:2.17.1
> >
> > while this version is not impacted by log4j security vulnerability:
> >
> > https://logging.apache.org/log4j/2.x/security.html
> >
> >
> >
> > So for sure it shouldn’t be banned.
> >
> >
> >
> > Regards,
> >
> > Mike
> >
> > From: Pierre Villard <pi...@gmail.com>
> > Sent: Wednesday, January 19, 2022 1:11 PM
> > To: users@nifi.apache.org
> > Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
> >
> >
> >
> > We recently changed the build to fail if it's including problematic
> transitive dependencies for log4j. I think those are coming with the
> specific versions of HBase/Hive you're using. Not a maven expert but I
> guess there is a way to exclude the step "enforce-banned-dependencies" from
> the build.
> >
> >
> >
> > Le mer. 19 janv. 2022 à 12:57, Michal Tomaszewski <
> Michal.Tomaszewski@cca.pl> a écrit :
> >
> > Hi Edward,
> >
> > Full mvn dependency:tree log enclosed.
> >
> > We’re compiling using command:
> >
> > mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0
> > -Dhbase.version=2.0.2
> >
> >
> >
> > Regards,
> >
> > Mike
> >
> >
> >
> > From: Edward Armes <ed...@gmail.com>
> > Sent: Wednesday, January 19, 2022 12:34 PM
> > To: users@nifi.apache.org
> > Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
> >
> >
> >
> > Hi Mike,
> >
> >
> >
> > Can you give the full output you get from mvn dependency:tree as we 15.2
> and 3 was done to remove log4j dependences from Nifi as a safety measure
> due the recent log4shell issues.
> >
> >
> >
> > Thanks
> >
> >
> >
> > Edward
> >
> >
> >
> > On Wed, Jan 19, 2022 at 10:24 AM Michal Tomaszewski <
> Michal.Tomaszewski@cca.pl> wrote:
> >
> > Hi,
> >
> > We are trying to compile nifi from sources.
> >
> > There is no problem with 1.15.1 compilation but in case of 1.15.2 and
> 1.15.3 there are compilation errors.
> >
> >
> >
> > Can you suggest how to solve this problem?
> >
> >
> >
> > mvn dependency:tree has no errors:
> >
> >
> >
> >
> >
> > $ tail log1.txt
> >
> > [INFO] nifi-toolkit-flowfile-repo ......................... SUCCESS [
> > 0.005 s]
> >
> > [INFO] nifi-toolkit-flowanalyzer .......................... SUCCESS [
> > 0.008 s]
> >
> > [INFO] nifi-toolkit-assembly .............................. SUCCESS [
> > 0.463 s]
> >
> > [INFO] nifi-toolkit-api ................................... SUCCESS [
> > 0.023 s]
> >
> > [INFO]
> > ----------------------------------------------------------------------
> > --
> >
> > [INFO] BUILD SUCCESS
> >
> > [INFO]
> > ----------------------------------------------------------------------
> > --
> >
> > [INFO] Total time:  02:41 min
> >
> > [INFO] Finished at: 2022-01-19T08:51:46+01:00
> >
> >
> >
> >
> >
> > Compilation of branch rel/nifi-1.15.3:
> >
> >
> >
> > [DEBUG] Adding ERROR message due to exception
> >
> > org.apache.maven.enforcer.rule.api.EnforcerRuleException: Found Banned
> > Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
> >
> > Use 'mvn dependency:tree' to locate the source of the banned
> dependencies.
> >
> >     at
> > org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute
> > (AbstractBanDependencies.java:113)
> >
> >     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
> > (EnforceMojo.java:200)
> >
> >     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> > (DefaultBuildPluginManager.java:137)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:210)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:156)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:148)
> >
> >     at
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> > t (LifecycleModuleBuilder.java:117)
> >
> >     at
> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> > dBuilder$1.call (MultiThreadedBuilder.java:196)
> >
> >     at
> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> > dBuilder$1.call (MultiThreadedBuilder.java:186)
> >
> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >
> >     at java.util.concurrent.Executors$RunnableAdapter.call
> > (Executors.java:511)
> >
> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >
> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
> > (ThreadPoolExecutor.java:1149)
> >
> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> > (ThreadPoolExecutor.java:624)
> >
> >     at java.lang.Thread.run (Thread.java:748)
> >
> > [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies
> failed with message:
> >
> > Found Banned Dependency:
> > org.apache.logging.log4j:log4j-core:jar:2.17.1
> >
> > Use 'mvn dependency:tree' to locate the source of the banned
> dependencies.
> >
> > [INFO]
> >
> >
> >
> > ….
> >
> >
> >
> > [INFO]
> > ----------------------------------------------------------------------
> > --
> >
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
> > (enforce-banned-dependencies) on project nifi-kite-processors: Some
> > Enforcer rules have failed. Look above for specific messages
> > explaining why the rule failed. -> [Help 1]
> >
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
> (enforce-banned-dependencies) on project nifi-kite-processors: Some
> Enforcer rules have failed. Look above for specific messages explaining why
> the rule failed.
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:215)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:156)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:148)
> >
> >     at
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> > t (LifecycleModuleBuilder.java:117)
> >
> >     at
> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> > dBuilder$1.call (MultiThreadedBuilder.java:196)
> >
> >     at
> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> > dBuilder$1.call (MultiThreadedBuilder.java:186)
> >
> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >
> >     at java.util.concurrent.Executors$RunnableAdapter.call
> > (Executors.java:511)
> >
> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >
> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
> > (ThreadPoolExecutor.java:1149)
> >
> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> > (ThreadPoolExecutor.java:624)
> >
> >     at java.lang.Thread.run (Thread.java:748)
> >
> > Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer
> rules have failed. Look above for specific messages explaining why the rule
> failed.
> >
> >     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
> > (EnforceMojo.java:255)
> >
> >     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> > (DefaultBuildPluginManager.java:137)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:210)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:156)
> >
> >     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > (MojoExecutor.java:148)
> >
> >     at
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> > t (LifecycleModuleBuilder.java:117)
> >
> >     at
> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> > dBuilder$1.call (MultiThreadedBuilder.java:196)
> >
> >     at
> > org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> > dBuilder$1.call (MultiThreadedBuilder.java:186)
> >
> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >
> >     at java.util.concurrent.Executors$RunnableAdapter.call
> > (Executors.java:511)
> >
> >     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
> >
> >     at java.util.concurrent.ThreadPoolExecutor.runWorker
> > (ThreadPoolExecutor.java:1149)
> >
> >     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> > (ThreadPoolExecutor.java:624)
> >
> >     at java.lang.Thread.run (Thread.java:748)
> >
> > [ERROR]
> >
> > [ERROR]
> >
> > [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> >
> > [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionExceptio
> > n
> >
> > [ERROR]
> >
> > [ERROR] After correcting the problems, you can resume the build with
> > the command
> >
> > [ERROR]   mvn <args> -rf :nifi-kite-processors
> >
> >
> >
> > Regards,
> >
> > Mike
>

RE: Nifi 1.15.2 and 1.15.3 compilation errors

Posted by Michal Tomaszewski <Mi...@cca.pl>.
Compilation with -Dhive.version=3.1.0 makes the problem.
mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0
is not successful.
We also tested -Dhive.version=3.1.2, that is most recent on Apache Hive site. Also without success.

Please note that without this parameter probably hive2 version is compiled into nifi and HiveStreaming is not working then.
And hive 3 is most popular novadays.

Regards,
Mike

-----Original Message-----
From: Bryan Bende <bb...@gmail.com> 
Sent: Wednesday, January 19, 2022 3:03 PM
To: users@nifi.apache.org
Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors

We did ban all use of log4j-core in favor of log4j-to-slf4j...

https://issues.apache.org/jira/browse/NIFI-9483

With your build specifying the -D versions, it created a different classpath during your build than what existed during the normal build of the release.

We should try to fix any issues like this though, so if you can figure out which dependency path is the issue, the fix is to add some exclusions and then to ensure that log4j-to-slf4j dependency is added.

On Wed, Jan 19, 2022 at 8:48 AM Michal Tomaszewski <Mi...@cca.pl> wrote:
>
> OK, but there is information that log4j-core:jar:2.17.1 is blocked:
>
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
>
> Found Banned Dependency: 
> org.apache.logging.log4j:log4j-core:jar:2.17.1
>
> while this version is not impacted by log4j security vulnerability:
>
> https://logging.apache.org/log4j/2.x/security.html
>
>
>
> So for sure it shouldn’t be banned.
>
>
>
> Regards,
>
> Mike
>
> From: Pierre Villard <pi...@gmail.com>
> Sent: Wednesday, January 19, 2022 1:11 PM
> To: users@nifi.apache.org
> Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>
>
>
> We recently changed the build to fail if it's including problematic transitive dependencies for log4j. I think those are coming with the specific versions of HBase/Hive you're using. Not a maven expert but I guess there is a way to exclude the step "enforce-banned-dependencies" from the build.
>
>
>
> Le mer. 19 janv. 2022 à 12:57, Michal Tomaszewski <Mi...@cca.pl> a écrit :
>
> Hi Edward,
>
> Full mvn dependency:tree log enclosed.
>
> We’re compiling using command:
>
> mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0 
> -Dhbase.version=2.0.2
>
>
>
> Regards,
>
> Mike
>
>
>
> From: Edward Armes <ed...@gmail.com>
> Sent: Wednesday, January 19, 2022 12:34 PM
> To: users@nifi.apache.org
> Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>
>
>
> Hi Mike,
>
>
>
> Can you give the full output you get from mvn dependency:tree as we 15.2 and 3 was done to remove log4j dependences from Nifi as a safety measure due the recent log4shell issues.
>
>
>
> Thanks
>
>
>
> Edward
>
>
>
> On Wed, Jan 19, 2022 at 10:24 AM Michal Tomaszewski <Mi...@cca.pl> wrote:
>
> Hi,
>
> We are trying to compile nifi from sources.
>
> There is no problem with 1.15.1 compilation but in case of 1.15.2 and 1.15.3 there are compilation errors.
>
>
>
> Can you suggest how to solve this problem?
>
>
>
> mvn dependency:tree has no errors:
>
>
>
>
>
> $ tail log1.txt
>
> [INFO] nifi-toolkit-flowfile-repo ......................... SUCCESS [  
> 0.005 s]
>
> [INFO] nifi-toolkit-flowanalyzer .......................... SUCCESS [  
> 0.008 s]
>
> [INFO] nifi-toolkit-assembly .............................. SUCCESS [  
> 0.463 s]
>
> [INFO] nifi-toolkit-api ................................... SUCCESS [  
> 0.023 s]
>
> [INFO] 
> ----------------------------------------------------------------------
> --
>
> [INFO] BUILD SUCCESS
>
> [INFO] 
> ----------------------------------------------------------------------
> --
>
> [INFO] Total time:  02:41 min
>
> [INFO] Finished at: 2022-01-19T08:51:46+01:00
>
>
>
>
>
> Compilation of branch rel/nifi-1.15.3:
>
>
>
> [DEBUG] Adding ERROR message due to exception
>
> org.apache.maven.enforcer.rule.api.EnforcerRuleException: Found Banned 
> Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
>
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
>
>     at 
> org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute 
> (AbstractBanDependencies.java:113)
>
>     at org.apache.maven.plugins.enforcer.EnforceMojo.execute 
> (EnforceMojo.java:200)
>
>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:210)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:156)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:148)
>
>     at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> t (LifecycleModuleBuilder.java:117)
>
>     at 
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> dBuilder$1.call (MultiThreadedBuilder.java:196)
>
>     at 
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> dBuilder$1.call (MultiThreadedBuilder.java:186)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.Executors$RunnableAdapter.call 
> (Executors.java:511)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.ThreadPoolExecutor.runWorker 
> (ThreadPoolExecutor.java:1149)
>
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run 
> (ThreadPoolExecutor.java:624)
>
>     at java.lang.Thread.run (Thread.java:748)
>
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
>
> Found Banned Dependency: 
> org.apache.logging.log4j:log4j-core:jar:2.17.1
>
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
>
> [INFO]
>
>
>
> ….
>
>
>
> [INFO] 
> ----------------------------------------------------------------------
> --
>
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce 
> (enforce-banned-dependencies) on project nifi-kite-processors: Some 
> Enforcer rules have failed. Look above for specific messages 
> explaining why the rule failed. -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce (enforce-banned-dependencies) on project nifi-kite-processors: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:215)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:156)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:148)
>
>     at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> t (LifecycleModuleBuilder.java:117)
>
>     at 
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> dBuilder$1.call (MultiThreadedBuilder.java:196)
>
>     at 
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> dBuilder$1.call (MultiThreadedBuilder.java:186)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.Executors$RunnableAdapter.call 
> (Executors.java:511)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.ThreadPoolExecutor.runWorker 
> (ThreadPoolExecutor.java:1149)
>
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run 
> (ThreadPoolExecutor.java:624)
>
>     at java.lang.Thread.run (Thread.java:748)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
>
>     at org.apache.maven.plugins.enforcer.EnforceMojo.execute 
> (EnforceMojo.java:255)
>
>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:210)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:156)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:148)
>
>     at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> t (LifecycleModuleBuilder.java:117)
>
>     at 
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> dBuilder$1.call (MultiThreadedBuilder.java:196)
>
>     at 
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreade
> dBuilder$1.call (MultiThreadedBuilder.java:186)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.Executors$RunnableAdapter.call 
> (Executors.java:511)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.ThreadPoolExecutor.runWorker 
> (ThreadPoolExecutor.java:1149)
>
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run 
> (ThreadPoolExecutor.java:624)
>
>     at java.lang.Thread.run (Thread.java:748)
>
> [ERROR]
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
>
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionExceptio
> n
>
> [ERROR]
>
> [ERROR] After correcting the problems, you can resume the build with 
> the command
>
> [ERROR]   mvn <args> -rf :nifi-kite-processors
>
>
>
> Regards,
>
> Mike

Re: Nifi 1.15.2 and 1.15.3 compilation errors

Posted by Bryan Bende <bb...@gmail.com>.
We did ban all use of log4j-core in favor of log4j-to-slf4j...

https://issues.apache.org/jira/browse/NIFI-9483

With your build specifying the -D versions, it created a different
classpath during your build than what existed during the normal build
of the release.

We should try to fix any issues like this though, so if you can figure
out which dependency path is the issue, the fix is to add some
exclusions and then to ensure that log4j-to-slf4j dependency is added.

On Wed, Jan 19, 2022 at 8:48 AM Michal Tomaszewski
<Mi...@cca.pl> wrote:
>
> OK, but there is information that log4j-core:jar:2.17.1 is blocked:
>
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
>
> Found Banned Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
>
> while this version is not impacted by log4j security vulnerability:
>
> https://logging.apache.org/log4j/2.x/security.html
>
>
>
> So for sure it shouldn’t be banned.
>
>
>
> Regards,
>
> Mike
>
> From: Pierre Villard <pi...@gmail.com>
> Sent: Wednesday, January 19, 2022 1:11 PM
> To: users@nifi.apache.org
> Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>
>
>
> We recently changed the build to fail if it's including problematic transitive dependencies for log4j. I think those are coming with the specific versions of HBase/Hive you're using. Not a maven expert but I guess there is a way to exclude the step "enforce-banned-dependencies" from the build.
>
>
>
> Le mer. 19 janv. 2022 à 12:57, Michal Tomaszewski <Mi...@cca.pl> a écrit :
>
> Hi Edward,
>
> Full mvn dependency:tree log enclosed.
>
> We’re compiling using command:
>
> mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0 -Dhbase.version=2.0.2
>
>
>
> Regards,
>
> Mike
>
>
>
> From: Edward Armes <ed...@gmail.com>
> Sent: Wednesday, January 19, 2022 12:34 PM
> To: users@nifi.apache.org
> Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors
>
>
>
> Hi Mike,
>
>
>
> Can you give the full output you get from mvn dependency:tree as we 15.2 and 3 was done to remove log4j dependences from Nifi as a safety measure due the recent log4shell issues.
>
>
>
> Thanks
>
>
>
> Edward
>
>
>
> On Wed, Jan 19, 2022 at 10:24 AM Michal Tomaszewski <Mi...@cca.pl> wrote:
>
> Hi,
>
> We are trying to compile nifi from sources.
>
> There is no problem with 1.15.1 compilation but in case of 1.15.2 and 1.15.3 there are compilation errors.
>
>
>
> Can you suggest how to solve this problem?
>
>
>
> mvn dependency:tree has no errors:
>
>
>
>
>
> $ tail log1.txt
>
> [INFO] nifi-toolkit-flowfile-repo ......................... SUCCESS [  0.005 s]
>
> [INFO] nifi-toolkit-flowanalyzer .......................... SUCCESS [  0.008 s]
>
> [INFO] nifi-toolkit-assembly .............................. SUCCESS [  0.463 s]
>
> [INFO] nifi-toolkit-api ................................... SUCCESS [  0.023 s]
>
> [INFO] ------------------------------------------------------------------------
>
> [INFO] BUILD SUCCESS
>
> [INFO] ------------------------------------------------------------------------
>
> [INFO] Total time:  02:41 min
>
> [INFO] Finished at: 2022-01-19T08:51:46+01:00
>
>
>
>
>
> Compilation of branch rel/nifi-1.15.3:
>
>
>
> [DEBUG] Adding ERROR message due to exception
>
> org.apache.maven.enforcer.rule.api.EnforcerRuleException: Found Banned Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
>
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
>
>     at org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute (AbstractBanDependencies.java:113)
>
>     at org.apache.maven.plugins.enforcer.EnforceMojo.execute (EnforceMojo.java:200)
>
>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
>
>     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
>
>     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:196)
>
>     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:186)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)
>
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)
>
>     at java.lang.Thread.run (Thread.java:748)
>
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
>
> Found Banned Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
>
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
>
> [INFO]
>
>
>
> ….
>
>
>
> [INFO] ------------------------------------------------------------------------
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce (enforce-banned-dependencies) on project nifi-kite-processors: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce (enforce-banned-dependencies) on project nifi-kite-processors: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
>
>     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
>
>     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:196)
>
>     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:186)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)
>
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)
>
>     at java.lang.Thread.run (Thread.java:748)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
>
>     at org.apache.maven.plugins.enforcer.EnforceMojo.execute (EnforceMojo.java:255)
>
>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
>
>     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
>
>     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:196)
>
>     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:186)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)
>
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)
>
>     at java.lang.Thread.run (Thread.java:748)
>
> [ERROR]
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
>
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>
> [ERROR]
>
> [ERROR] After correcting the problems, you can resume the build with the command
>
> [ERROR]   mvn <args> -rf :nifi-kite-processors
>
>
>
> Regards,
>
> Mike

RE: Nifi 1.15.2 and 1.15.3 compilation errors

Posted by Michal Tomaszewski <Mi...@cca.pl>.
OK, but there is information that log4j-core:jar:2.17.1 is blocked:
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
Found Banned Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
while this version is not impacted by log4j security vulnerability:
https://logging.apache.org/log4j/2.x/security.html

So for sure it shouldn’t be banned.

Regards,
Mike
From: Pierre Villard <pi...@gmail.com>
Sent: Wednesday, January 19, 2022 1:11 PM
To: users@nifi.apache.org
Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors

We recently changed the build to fail if it's including problematic transitive dependencies for log4j. I think those are coming with the specific versions of HBase/Hive you're using. Not a maven expert but I guess there is a way to exclude the step "enforce-banned-dependencies" from the build.

Le mer. 19 janv. 2022 à 12:57, Michal Tomaszewski <Mi...@cca.pl>> a écrit :
Hi Edward,
Full mvn dependency:tree log enclosed.
We’re compiling using command:
mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0 -Dhbase.version=2.0.2

Regards,
Mike

From: Edward Armes <ed...@gmail.com>>
Sent: Wednesday, January 19, 2022 12:34 PM
To: users@nifi.apache.org<ma...@nifi.apache.org>
Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors

Hi Mike,

Can you give the full output you get from mvn dependency:tree as we 15.2 and 3 was done to remove log4j dependences from Nifi as a safety measure due the recent log4shell issues.

Thanks

Edward

On Wed, Jan 19, 2022 at 10:24 AM Michal Tomaszewski <Mi...@cca.pl>> wrote:
Hi,
We are trying to compile nifi from sources.
There is no problem with 1.15.1 compilation but in case of 1.15.2 and 1.15.3 there are compilation errors.

Can you suggest how to solve this problem?

mvn dependency:tree has no errors:


$ tail log1.txt
[INFO] nifi-toolkit-flowfile-repo ......................... SUCCESS [  0.005 s]
[INFO] nifi-toolkit-flowanalyzer .......................... SUCCESS [  0.008 s]
[INFO] nifi-toolkit-assembly .............................. SUCCESS [  0.463 s]
[INFO] nifi-toolkit-api ................................... SUCCESS [  0.023 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  02:41 min
[INFO] Finished at: 2022-01-19T08:51:46+01:00


Compilation of branch rel/nifi-1.15.3:

[DEBUG] Adding ERROR message due to exception
org.apache.maven.enforcer.rule.api.EnforcerRuleException: Found Banned Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
    at org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute (AbstractBanDependencies.java:113)
    at org.apache.maven.plugins.enforcer.EnforceMojo.execute (EnforceMojo.java:200)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:196)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:186)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)
    at java.lang.Thread.run (Thread.java:748)
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
Found Banned Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
[INFO]

….

[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce (enforce-banned-dependencies) on project nifi-kite-processors: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce (enforce-banned-dependencies) on project nifi-kite-processors: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:196)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:186)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)
    at java.lang.Thread.run (Thread.java:748)
Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
    at org.apache.maven.plugins.enforcer.EnforceMojo.execute (EnforceMojo.java:255)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:196)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:186)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)
    at java.lang.Thread.run (Thread.java:748)
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :nifi-kite-processors

Regards,
Mike

Re: Nifi 1.15.2 and 1.15.3 compilation errors

Posted by Pierre Villard <pi...@gmail.com>.
We recently changed the build to fail if it's including problematic
transitive dependencies for log4j. I think those are coming with the
specific versions of HBase/Hive you're using. Not a maven expert but I
guess there is a way to exclude the step "enforce-banned-dependencies" from
the build.

Le mer. 19 janv. 2022 à 12:57, Michal Tomaszewski <Mi...@cca.pl>
a écrit :

> Hi Edward,
>
> Full mvn dependency:tree log enclosed.
>
> We’re compiling using command:
>
> mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0
> -Dhbase.version=2.0.2
>
>
>
> Regards,
>
> Mike
>
>
>
> *From:* Edward Armes <ed...@gmail.com>
> *Sent:* Wednesday, January 19, 2022 12:34 PM
> *To:* users@nifi.apache.org
> *Subject:* Re: Nifi 1.15.2 and 1.15.3 compilation errors
>
>
>
> Hi Mike,
>
>
>
> Can you give the full output you get from mvn dependency:tree as we 15.2
> and 3 was done to remove log4j dependences from Nifi as a safety measure
> due the recent log4shell issues.
>
>
>
> Thanks
>
>
>
> Edward
>
>
>
> On Wed, Jan 19, 2022 at 10:24 AM Michal Tomaszewski <
> Michal.Tomaszewski@cca.pl> wrote:
>
> Hi,
>
> We are trying to compile nifi from sources.
>
> There is no problem with 1.15.1 compilation but in case of 1.15.2 and
> 1.15.3 there are compilation errors.
>
>
>
> Can you suggest how to solve this problem?
>
>
>
> mvn dependency:tree has no errors:
>
>
>
>
>
> $ tail log1.txt
>
> [INFO] nifi-toolkit-flowfile-repo ......................... SUCCESS [
> 0.005 s]
>
> [INFO] nifi-toolkit-flowanalyzer .......................... SUCCESS [
> 0.008 s]
>
> [INFO] nifi-toolkit-assembly .............................. SUCCESS [
> 0.463 s]
>
> [INFO] nifi-toolkit-api ................................... SUCCESS [
> 0.023 s]
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] BUILD SUCCESS
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Total time:  02:41 min
>
> [INFO] Finished at: 2022-01-19T08:51:46+01:00
>
>
>
>
>
> Compilation of branch rel/nifi-1.15.3:
>
>
>
> [DEBUG] Adding ERROR message due to exception
>
> org.apache.maven.enforcer.rule.api.EnforcerRuleException: Found Banned
> Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
>
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
>
>     at org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute
> (AbstractBanDependencies.java:113)
>
>     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
> (EnforceMojo.java:200)
>
>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
>
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:196)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:186)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:511)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1149)
>
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:624)
>
>     at java.lang.Thread.run (Thread.java:748)
>
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies
> failed with message:
>
> Found Banned Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
>
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
>
> [INFO]
>
>
>
> ….
>
>
>
> [INFO]
> ------------------------------------------------------------------------
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
> (enforce-banned-dependencies) on project nifi-kite-processors: Some
> Enforcer rules have failed. Look above for specific messages explaining why
> the rule failed. -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
> (enforce-banned-dependencies) on project nifi-kite-processors: Some
> Enforcer rules have failed. Look above for specific messages explaining why
> the rule failed.
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
>
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:196)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:186)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:511)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1149)
>
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:624)
>
>     at java.lang.Thread.run (Thread.java:748)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer
> rules have failed. Look above for specific messages explaining why the rule
> failed.
>
>     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
> (EnforceMojo.java:255)
>
>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
>
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:196)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:186)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:511)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1149)
>
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:624)
>
>     at java.lang.Thread.run (Thread.java:748)
>
> [ERROR]
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
>
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>
> [ERROR]
>
> [ERROR] After correcting the problems, you can resume the build with the
> command
>
> [ERROR]   mvn <args> -rf :nifi-kite-processors
>
>
>
> Regards,
>
> Mike
>
>

RE: Nifi 1.15.2 and 1.15.3 compilation errors

Posted by Michal Tomaszewski <Mi...@cca.pl>.
Hi Edward,
Full mvn dependency:tree log enclosed.
We’re compiling using command:
mvn -e -X -T C2.0 clean install -DskipTests -Dhive.version=3.1.0 -Dhbase.version=2.0.2

Regards,
Mike

From: Edward Armes <ed...@gmail.com>
Sent: Wednesday, January 19, 2022 12:34 PM
To: users@nifi.apache.org
Subject: Re: Nifi 1.15.2 and 1.15.3 compilation errors

Hi Mike,

Can you give the full output you get from mvn dependency:tree as we 15.2 and 3 was done to remove log4j dependences from Nifi as a safety measure due the recent log4shell issues.

Thanks

Edward

On Wed, Jan 19, 2022 at 10:24 AM Michal Tomaszewski <Mi...@cca.pl>> wrote:
Hi,
We are trying to compile nifi from sources.
There is no problem with 1.15.1 compilation but in case of 1.15.2 and 1.15.3 there are compilation errors.

Can you suggest how to solve this problem?

mvn dependency:tree has no errors:


$ tail log1.txt
[INFO] nifi-toolkit-flowfile-repo ......................... SUCCESS [  0.005 s]
[INFO] nifi-toolkit-flowanalyzer .......................... SUCCESS [  0.008 s]
[INFO] nifi-toolkit-assembly .............................. SUCCESS [  0.463 s]
[INFO] nifi-toolkit-api ................................... SUCCESS [  0.023 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  02:41 min
[INFO] Finished at: 2022-01-19T08:51:46+01:00


Compilation of branch rel/nifi-1.15.3:

[DEBUG] Adding ERROR message due to exception
org.apache.maven.enforcer.rule.api.EnforcerRuleException: Found Banned Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
    at org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute (AbstractBanDependencies.java:113)
    at org.apache.maven.plugins.enforcer.EnforceMojo.execute (EnforceMojo.java:200)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:196)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:186)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)
    at java.lang.Thread.run (Thread.java:748)
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
Found Banned Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
[INFO]

….

[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce (enforce-banned-dependencies) on project nifi-kite-processors: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce (enforce-banned-dependencies) on project nifi-kite-processors: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:196)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:186)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)
    at java.lang.Thread.run (Thread.java:748)
Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
    at org.apache.maven.plugins.enforcer.EnforceMojo.execute (EnforceMojo.java:255)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:196)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:186)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)
    at java.lang.Thread.run (Thread.java:748)
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :nifi-kite-processors

Regards,
Mike

Re: Nifi 1.15.2 and 1.15.3 compilation errors

Posted by Edward Armes <ed...@gmail.com>.
Hi Mike,

Can you give the full output you get from mvn dependency:tree as we 15.2
and 3 was done to remove log4j dependences from Nifi as a safety measure
due the recent log4shell issues.

Thanks

Edward

On Wed, Jan 19, 2022 at 10:24 AM Michal Tomaszewski <
Michal.Tomaszewski@cca.pl> wrote:

> Hi,
>
> We are trying to compile nifi from sources.
>
> There is no problem with 1.15.1 compilation but in case of 1.15.2 and
> 1.15.3 there are compilation errors.
>
>
>
> Can you suggest how to solve this problem?
>
>
>
> mvn dependency:tree has no errors:
>
>
>
>
>
> $ tail log1.txt
>
> [INFO] nifi-toolkit-flowfile-repo ......................... SUCCESS [
> 0.005 s]
>
> [INFO] nifi-toolkit-flowanalyzer .......................... SUCCESS [
> 0.008 s]
>
> [INFO] nifi-toolkit-assembly .............................. SUCCESS [
> 0.463 s]
>
> [INFO] nifi-toolkit-api ................................... SUCCESS [
> 0.023 s]
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] BUILD SUCCESS
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Total time:  02:41 min
>
> [INFO] Finished at: 2022-01-19T08:51:46+01:00
>
>
>
>
>
> Compilation of branch rel/nifi-1.15.3:
>
>
>
> [DEBUG] Adding ERROR message due to exception
>
> org.apache.maven.enforcer.rule.api.EnforcerRuleException: Found Banned
> Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
>
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
>
>     at org.apache.maven.plugins.enforcer.AbstractBanDependencies.execute
> (AbstractBanDependencies.java:113)
>
>     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
> (EnforceMojo.java:200)
>
>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
>
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:196)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:186)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:511)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1149)
>
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:624)
>
>     at java.lang.Thread.run (Thread.java:748)
>
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies
> failed with message:
>
> Found Banned Dependency: org.apache.logging.log4j:log4j-core:jar:2.17.1
>
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
>
> [INFO]
>
>
>
> ….
>
>
>
> [INFO]
> ------------------------------------------------------------------------
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
> (enforce-banned-dependencies) on project nifi-kite-processors: Some
> Enforcer rules have failed. Look above for specific messages explaining why
> the rule failed. -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
> (enforce-banned-dependencies) on project nifi-kite-processors: Some
> Enforcer rules have failed. Look above for specific messages explaining why
> the rule failed.
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
>
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:196)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:186)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:511)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1149)
>
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:624)
>
>     at java.lang.Thread.run (Thread.java:748)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer
> rules have failed. Look above for specific messages explaining why the rule
> failed.
>
>     at org.apache.maven.plugins.enforcer.EnforceMojo.execute
> (EnforceMojo.java:255)
>
>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
>
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
>
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:196)
>
>     at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
> (MultiThreadedBuilder.java:186)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.Executors$RunnableAdapter.call
> (Executors.java:511)
>
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>
>     at java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1149)
>
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:624)
>
>     at java.lang.Thread.run (Thread.java:748)
>
> [ERROR]
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
>
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>
> [ERROR]
>
> [ERROR] After correcting the problems, you can resume the build with the
> command
>
> [ERROR]   mvn <args> -rf :nifi-kite-processors
>
>
>
> Regards,
>
> Mike
>