You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Tony Kurc <tr...@gmail.com> on 2015/10/30 15:48:44 UTC
"External" extensions
All,
I wanted to start a conversation about projects that are good for people
using or developing NiFi, but either can't or don't belong in the source
tree. This could be due to licensing issues (for example not compatible (or
not yet determined if it is compatible (GPL [1])) with the Apache License),
or other thought provoking mild concerns like we're discussing on NIFI-1074
[2].
I'd like to propose either capturing these on the website or on the wiki or
some other approach I didn't think of. I was hoping to find a good
archetype for this type of documentation in another apache project, but
didn't find anything I personally liked. If you have seen something you
like or don't, I'd be interested to hear.
[1] http://www.apache.org/licenses/GPL-compatibility.html
[2] https://issues.apache.org/jira/browse/NIFI-1074
Re: nifi fails build on CentOS 7
Posted by Tony Kurc <tr...@gmail.com>.
Jeff,
What did you have JAVA_HOME set to?
can you do a 'find /usr/lib/jvm -name javac'
On Tue, Nov 3, 2015 at 7:06 PM, Jeff <j....@gmail.com> wrote:
> The only other message I see is
>
> [WARNING] Unable to autodetect 'javac' path, using 'javac' from the
> environment.
>
> No worries, it can wait.
>
> Thanks,
>
> > On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com> wrote:
> >
> > if i weren't on horrible hotel wifi right now i'd try to pull down
> > centos. Is there anymore that can be found with those stack traces .
> > They're not saying much. Your java and maven versions seem quite good
> > so need to dig further.
> >
> > On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j....@gmail.com> wrote:
> >> JAVA_HOME is currently not set but I’ve tried both ways.
> >>
> >> [root@localhost nifi]# java -version
> >> openjdk version "1.8.0_65"
> >> OpenJDK Runtime Environment (build 1.8.0_65-b17)
> >> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
> >>
> >>
> >> [root@localhost nifi]# mvn -version
> >> which: no javac in
> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
> >> Warning: JAVA_HOME environment variable is not set.
> >> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
> 2015-04-22T06:57:37-05:00)
> >> Maven home: /opt/apache-maven-3.3.3
> >> Java version: 1.8.0_65, vendor: Oracle Corporation
> >> Java home:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
> >> Default locale: en_US, platform encoding: UTF-8
> >> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch: "amd64",
> family: "unix"
> >>
> >>
> >>
> >>> On Nov 3, 2015, at 5:37 PM, Joe Witt <jo...@gmail.com> wrote:
> >>>
> >>> Jeff
> >>>
> >>> When you run 'java -version' and 'mvn -version' what do you get back?
> >>>
> >>> Thanks
> >>> Joe
> >>>
> >>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com> wrote:
> >>>> I’m getting the below on a VM. It does build successfully on my Mac,
> though.
> >>>>
> >>>> mvn -e -X -T 2.0C clean install
> >>>> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> (default-compile) on project nifi-api: Compilation failure -> [Help 1]
> >>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> (default-compile) on project nifi-api: Compilation failure
> >>>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> >>>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> >>>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> >>>> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> >>>> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
> >>>> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
> >>>> 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:1142)
> >>>> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> >>>> at java.lang.Thread.run(Thread.java:745)
> >>>> Caused by:
> org.apache.maven.plugin.compiler.CompilationFailureException: Compilation
> failure
> >>>> at
> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
> >>>> at
> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
> >>>> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> >>>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> >>>> ... 11 more
> >>>>
> >>>> Thanks,
> >>>> Jeff
> >>
>
>
Re: nifi fails build on CentOS 7
Posted by Joe Witt <jo...@gmail.com>.
Jeff
Can you send the results referenced in here
'Please refer to
/root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports'
Thanks
Joe
On Mon, Dec 7, 2015 at 4:24 PM, Jeff <j....@gmail.com> wrote:
> I just cloned Nifi but I’m still seeing these errors when I do mvn -e -X -T 2.0C clean install
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on project nifi-hdfs-processors: There are test failures.
> [ERROR]
> [ERROR] Please refer to /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports for the individual test results.
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on project nifi-hdfs-processors: There are test failures.
>
> Please refer to /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports for the individual test results.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
> at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
> 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:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures.
>
> Please refer to /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports for the individual test results.
> at org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
> at org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 11 more
> [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/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :nifi-hdfs-processors
>
>
>
>> On Nov 10, 2015, at 12:33 PM, Aldrin Piri <al...@gmail.com> wrote:
>>
>> Seems there is in fact an issue with the test cited prior. I received the
>> following on my Travis CI build on a branch which has the latest of master
>> merged into it. Unfortunately, it seems that the environment is not the
>> same as before.
>>
>> In this case, Travis CI is running with Ubuntu 12.04 LTS [1]. For the
>> particular build [2], Oracle JDK 7 built without issue, but Oracle JDK 8
>> exhibited the same problem [3] as reported by Jeff.
>>
>> NIFI-1145 was created to track this issue [4]
>>
>> [1]
>> http://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
>> [2] https://travis-ci.org/apiri/incubator-nifi/builds/90353191
>> [3] https://s3.amazonaws.com/archive.travis-ci.org/jobs/90353192/log.txt
>> [4] https://issues.apache.org/jira/browse/NIFI-1145
>>
>> On Thu, Nov 5, 2015 at 5:17 PM, Jeff <j....@gmail.com> wrote:
>>
>>>
>>>
>>> I built a new VM CentOS7
>>>
>>> I get the below most of the time though last night it did succeeded.
>>>
>>> [INFO] nifi-framework-core ................................ FAILURE [02:41
>>> min]
>>>
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Total time: 08:51 min (Wall Clock)
>>> [INFO] Finished at: 2015-11-05T16:09:51-06:00
>>> [INFO] Final Memory: 183M/514M
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
>>> project nifi-framework-core: There are test failures.
>>> [ERROR]
>>> [ERROR] Please refer to
>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>> for the individual test results.
>>> [ERROR] -> [Help 1]
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>>> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>> (default-test) on project nifi-framework-core: There are test failures.
>>>
>>> Please refer to
>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>> for the individual test results.
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>> at
>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>> at
>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>> 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:1142)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>> at java.lang.Thread.run(Thread.java:745)
>>> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
>>> failures.
>>>
>>> Please refer to
>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>> for the individual test results.
>>> at
>>> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
>>> at
>>> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
>>> at
>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
>>> at
>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>>> at
>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>> ... 11 more
>>> [ERROR]
>>>
>>>
>>>
>>>
>>>> On Nov 4, 2015, at 9:01 AM, Mark Payne <ma...@hotmail.com> wrote:
>>>>
>>>> Jeff,
>>>>
>>>> I just checked out a fresh build from master, running on CentOS 7 and
>>> was able to build without any problems.
>>>> So I don't think it is specifically a problem with CentOS 7. Can you
>>> provide the output of the unit tests?
>>>>
>>>> They should be in
>>> ${NIFI_SRC_DIR}/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>
>>>> The two files of interest are
>>> org.apache.nifi.controller.TestStandardFlowFileQueue.txt and
>>> org.apache.nifi.controller.TestStandardFlowFileQueue-output.txt
>>>>
>>>> Thanks!
>>>> -Mark
>>>>
>>>>
>>>>> On Nov 4, 2015, at 8:53 AM, Jeff <j....@gmail.com> wrote:
>>>>>
>>>>> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.916
>>> sec <<< FAILURE! - in org.apache.nifi.controller.TestStandardFlowFileQueue
>>>>>
>>> testDropSwappedFlowFiles(org.apache.nifi.controller.TestStandardFlowFileQueue)
>>> Time elapsed: 21.825 sec <<< ERROR!
>>>>> org.junit.runners.model.TestTimedOutException: test timed out after
>>> 20000 milliseconds
>>>>> at java.lang.Throwable.fillInStackTrace(Native Method)
>>>>> at java.lang.Throwable.fillInStackTrace(Throwable.java:783)
>>>>> at java.lang.Throwable.<init>(Throwable.java:250)
>>>>> at
>>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:24)
>>>>> at
>>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:19)
>>>>> at
>>> org.mockito.internal.invocation.InvocationImpl.<init>(InvocationImpl.java:50)
>>>>> at
>>> org.mockito.internal.creation.cglib.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:58)
>>>>> at
>>> org.apache.nifi.connectable.Connection$$EnhancerByMockitoWithCGLIB$$8aa704ad.getDestination(<generated>)
>>>>> at
>>> org.apache.nifi.controller.StandardFlowFileQueue.put(StandardFlowFileQueue.java:315)
>>>>> at
>>> org.apache.nifi.controller.TestStandardFlowFileQueue.testDropSwappedFlowFiles(TestStandardFlowFileQueue.java:169)
>>>>>
>>>>>> On Nov 4, 2015, at 7:51 AM, Brandon DeVries <br...@jhu.edu> wrote:
>>>>>>
>>>>>> Jeff,
>>>>>>
>>>>>> Can you see what tests had failures? Also, if you just want to verify
>>> that
>>>>>> your system can do the build, you could do something like "mvn clean
>>>>>> install -DskipTests". Let us know what you see. Thanks.
>>>>>>
>>>>>> Brandon
>>>>>>
>>>>>> On Wed, Nov 4, 2015 at 8:46 AM, Jeff <j....@gmail.com> wrote:
>>>>>>
>>>>>>>
>>>>>>> Well, the build got much further with the Oracle JDK but still failed;
>>>>>>>
>>>>>>> [INFO]
>>>>>>>
>>> ------------------------------------------------------------------------
>>>>>>> [INFO] BUILD FAILURE
>>>>>>> [INFO]
>>>>>>>
>>> ------------------------------------------------------------------------
>>>>>>> [INFO] Total time: 07:47 min (Wall Clock)
>>>>>>> [INFO] Finished at: 2015-11-03T17:07:40-06:00
>>>>>>> [INFO] Final Memory: 183M/564M
>>>>>>> [INFO]
>>>>>>>
>>> ------------------------------------------------------------------------
>>>>>>> [ERROR] Failed to execute goal
>>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>> (default-test) on
>>>>>>> project nifi-framework-core: There are test failures.
>>>>>>> [ERROR]
>>>>>>> [ERROR] Please refer to
>>>>>>>
>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>> for the individual test results.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> On Nov 3, 2015, at 6:54 PM, Cerulean Blue <j....@gmail.com>
>>> wrote:
>>>>>>>>
>>>>>>>> Oh, I also adjusted the memory!
>>>>>>>>
>>>>>>>> Sent from my iPhone
>>>>>>>>
>>>>>>>>> On Nov 3, 2015, at 6:50 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Jeff - can you please send another note telling Tony that it turns
>>> out
>>>>>>>>> it was memory settings :-)
>>>>>>>>>
>>>>>>>>> He is making fun of me off-list. He should totally do that on-list!
>>>>>>>>>
>>>>>>>>> Glad you're in business now and sorry for my terrible misdirection.
>>>>>>>>>
>>>>>>>>> Joe
>>>>>>>>>
>>>>>>>>>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com>
>>> wrote:
>>>>>>>>>> Huzzah
>>>>>>>>>>
>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> I removed openjdk and installed the Oracle jdk and it now works.
>>>>>>>>>>>
>>>>>>>>>>> Thanks for the help!!
>>>>>>>>>>>
>>>>>>>>>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> it is entirely possible that you only have the jre installed.
>>> 'yum
>>>>>>>>>>>> whatprovides "*/bin/javac"' may tell you packages which you can
>>>>>>> install
>>>>>>>>>>>> which include a compiler.
>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com>
>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> find / -name javac did not return anything
>>>>>>>>>>>>>
>>>>>>>>>>>>> I had JAVA_HOME set to
>>>>>>>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com>
>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Jeff,
>>>>>>>>>>>>>> Were you able to run that find command?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com>
>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>
>>>>>>>
>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>>> [INFO] Total time: 8.091 s
>>>>>>>>>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
>>>>>>>>>>>>>>> [INFO] Final Memory: 76M/365M
>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>
>>>>>>>
>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure ->
>>>>>>> [Help 1]
>>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run
>>> Maven
>>>>>>> with
>>>>>>>>>>> the
>>>>>>>>>>>>>>> -e switch.
>>>>>>>>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
>>>>>>> logging.
>>>>>>>>>>>>>>> [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/MojoFailureException
>>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>>> [ERROR] After correcting the problems, you can resume the
>>> build
>>>>>>> with
>>>>>>>>>>> the
>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>> [ERROR] mvn <goals> -rf :nifi-api
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com>
>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Can you go ahead and try just plain ol'
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I am curious if there is a memory/settings issue that is
>>>>>>> manifesting
>>>>>>>>>>>>>>>> as an exception during compilation but that it isn't
>>> actually a
>>>>>>>>>>>>>>>> compilation problem at all...
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j....@gmail.com>
>>>>>>> wrote:
>>>>>>>>>>>>>>>>> The only other message I see is
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac'
>>> from
>>>>>>> the
>>>>>>>>>>>>>>> environment.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> No worries, it can wait.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com>
>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to
>>> pull
>>>>>>> down
>>>>>>>>>>>>>>>>>> centos. Is there anymore that can be found with those
>>> stack
>>>>>>>>>>> traces .
>>>>>>>>>>>>>>>>>> They're not saying much. Your java and maven versions seem
>>>>>>> quite
>>>>>>>>>>>>> good
>>>>>>>>>>>>>>>>>> so need to dig further.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j.007ba7@gmail.com
>>>>
>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> [root@localhost nifi]# java -version
>>>>>>>>>>>>>>>>>>> openjdk version "1.8.0_65"
>>>>>>>>>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>>>>>>>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> [root@localhost nifi]# mvn -version
>>>>>>>>>>>>>>>>>>> which: no javac in
>>>>>>>>>>>
>>>>>>>
>>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>>>>>>>>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set.
>>>>>>>>>>>>>>>>>>> Apache Maven 3.3.3
>>> (7994120775791599e205a5524ec3e0dfe41d4a06;
>>>>>>>>>>>>>>> 2015-04-22T06:57:37-05:00)
>>>>>>>>>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3
>>>>>>>>>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>>>>>>>>>>>>>>>>>> Java home:
>>>>>>>>>>>>>>>
>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>>>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64",
>>> arch:
>>>>>>>>>>>>>>> "amd64", family: "unix"
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <joe.witt@gmail.com
>>>>
>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do
>>> you
>>>>>>> get
>>>>>>>>>>>>> back?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <
>>> j.007ba7@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>> I’m getting the below on a VM. It does build
>>> successfully
>>>>>>> on my
>>>>>>>>>>>>>>> Mac, though.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install
>>>>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure ->
>>>>>>> [Help 1]
>>>>>>>>>>>>>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException:
>>>>>>> Failed
>>>>>>>>>>> to
>>>>>>>>>>>>>>> execute goal
>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>
>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>
>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>>>>>>>>>>>>>> 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:1142)
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>>>>>>>>>>>>>> Caused by:
>>>>>>>>>>>>>>> org.apache.maven.plugin.compiler.CompilationFailureException:
>>>>>>>>>>>>> Compilation
>>>>>>>>>>>>>>> failure
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>
>>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>
>>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>
>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>>>>>>>>>>>>>> ... 11 more
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>
>>>
>>>
>
Re: nifi fails build on CentOS 7
Posted by Joe Witt <jo...@gmail.com>.
Jeff,
Please be sure you're on latest master and manually delete those
target dirs (as root) once more. I had a bug in that test last night.
But it should now be fixed. the issue was that it made a file,
changed its perms to be something we cannot delete, then moves on.
Second pass, it will fail and cannot delete it so requires manual
delete as root. This was resolved.
Thanks
Joe
On Tue, Dec 8, 2015 at 11:01 AM, Jeff <j....@gmail.com> wrote:
> I created a nifi user on my VM, moved the /root/nifi folder to / and changed the owner of /nifi to nifi:nifi recursively
>
> I executed mvn -e -X -T 2.0C clean install as the nifi user
>
> Below is the error;
>
> Downloaded: https://repo1.maven.org/maven2/com/yammer/metrics/metrics-ganglia/2.2.0/metrics-ganglia-2.2.0.jar (12 KB at 3.8 KB/sec)
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-clean-plugin:2.5:clean (default-clean) on project nifi-hdfs-processors: Failed to clean project: Failed to delete /nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/testPutFileWrongPermissions -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-clean-plugin:2.5:clean (default-clean) on project nifi-hdfs-processors: Failed to clean project: Failed to delete /nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/testPutFileWrongPermissions
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
> at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
> 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:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to clean project: Failed to delete /nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/testPutFileWrongPermissions
> at org.apache.maven.plugin.clean.CleanMojo.execute(CleanMojo.java:215)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 11 more
> Caused by: java.io.IOException: Failed to delete /nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/testPutFileWrongPermissions
> at org.apache.maven.plugin.clean.Cleaner.delete(Cleaner.java:249)
> at org.apache.maven.plugin.clean.Cleaner.delete(Cleaner.java:191)
> at org.apache.maven.plugin.clean.Cleaner.delete(Cleaner.java:158)
> at org.apache.maven.plugin.clean.Cleaner.delete(Cleaner.java:117)
> at org.apache.maven.plugin.clean.CleanMojo.execute(CleanMojo.java:193)
> ... 13 more
> [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 <goals> -rf :nifi-hdfs-processors
> [DEBUG] incrementalBuildHelper#afterRebuildExecution
> [INFO]
> [INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ nifi-standard-prioritizers ---
> [DEBUG] Configuring mojo org.apache.maven.plugins:maven-resources-plugin:2.7:testResources from plugin realm ClassRealm[plugin>org.apache.maven.plugins:maven-resources-plugin:2.7, parent: sun.misc.Launcher$AppClassLoader@70dea4e]
> Downloaded: https://repo1.maven.org/maven2/com/yammer/metrics/metrics-core/2.2.0/metrics-core-2.2.0.jar (81 KB at 26.7 KB/sec)
>
>> On Dec 7, 2015, at 4:05 PM, Joe Witt <jo...@gmail.com> wrote:
>>
>> we now understand the TestPutHDFS issue.
>> https://issues.apache.org/jira/browse/NIFI-1267
>>
>> The test assumes that a user would not be able to write to a file
>> unless it has write perms. However, root can do that. So users
>> building as root would see this.
>>
>> Thanks
>> Joe
>>
>> On Mon, Dec 7, 2015 at 4:45 PM, Joe Witt <jo...@gmail.com> wrote:
>>> jeff - out of curiosity can you confirm you're running as root on that
>>> VM when you build?
>>>
>>> On Mon, Dec 7, 2015 at 4:42 PM, Jeff <j....@gmail.com> wrote:
>>>> Hi Joe,
>>>>
>>>> You are welcome. Below is what I’m seeing
>>>>
>>>> -------------------------------------------------------------------------------
>>>> Test set: org.apache.nifi.processors.hadoop.PutHDFSTest
>>>> -------------------------------------------------------------------------------
>>>> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.949 sec <<< FAILURE! - in org.apache.nifi.processors.hadoop.PutHDFSTest
>>>> testPutFileWithException(org.apache.nifi.processors.hadoop.PutHDFSTest) Time elapsed: 0.532 sec <<< FAILURE!
>>>> java.lang.AssertionError: null
>>>> at org.junit.Assert.fail(Assert.java:86)
>>>> at org.junit.Assert.assertTrue(Assert.java:41)
>>>> at org.junit.Assert.assertFalse(Assert.java:64)
>>>> at org.junit.Assert.assertFalse(Assert.java:74)
>>>> at org.apache.nifi.processors.hadoop.PutHDFSTest.testPutFileWithException(PutHDFSTest.java:230)
>>>>
>>>>> On Dec 7, 2015, at 3:36 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>
>>>>> thanks for reporting this Jeff and your timing could not have been better!
>>>>>
>>>>> It's happening for Gilman as well.
>>>>>
>>>>> Joe
>>>>>
>>>>> On Mon, Dec 7, 2015 at 4:31 PM, Jeff <j....@gmail.com> wrote:
>>>>>> Yes, CentOS 7
>>>>>>
>>>>>> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.703 sec - in org.apache.nifi.processors.hadoop.TestListHDFS
>>>>>>
>>>>>> Results :
>>>>>>
>>>>>> Failed tests:
>>>>>> PutHDFSTest.testPutFileWithException:230 null
>>>>>>
>>>>>>
>>>>>>
>>>>>> Tests run: 21, Failures: 1, Errors: 0, Skipped: 0
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On Dec 7, 2015, at 3:28 PM, Matt Gilman <ma...@gmail.com> wrote:
>>>>>>>
>>>>>>> Jeff,
>>>>>>>
>>>>>>> Are you still running on CentOS 7? Can you provide more details about the
>>>>>>> unit test is failing? Thanks!
>>>>>>>
>>>>>>> Matt
>>>>>>>
>>>>>>> On Mon, Dec 7, 2015 at 4:24 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>
>>>>>>>> I just cloned Nifi but I’m still seeing these errors when I do mvn -e -X
>>>>>>>> -T 2.0C clean install
>>>>>>>>
>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
>>>>>>>> project nifi-hdfs-processors: There are test failures.
>>>>>>>> [ERROR]
>>>>>>>> [ERROR] Please refer to
>>>>>>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>>>>>>> for the individual test results.
>>>>>>>> [ERROR] -> [Help 1]
>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>>>>>>>> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>>>>>> (default-test) on project nifi-hdfs-processors: There are test failures.
>>>>>>>>
>>>>>>>> Please refer to
>>>>>>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>>>>>>> for the individual test results.
>>>>>>>> at
>>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>> at
>>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>> at
>>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>> at
>>>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>> at
>>>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>> at
>>>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>> 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:1142)
>>>>>>>> at
>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
>>>>>>>> failures.
>>>>>>>>
>>>>>>>> Please refer to
>>>>>>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>>>>>>> for the individual test results.
>>>>>>>> at
>>>>>>>> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
>>>>>>>> at
>>>>>>>> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
>>>>>>>> at
>>>>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
>>>>>>>> at
>>>>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>>>>>>>> at
>>>>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>> at
>>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>> ... 11 more
>>>>>>>> [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/MojoFailureException
>>>>>>>> [ERROR]
>>>>>>>> [ERROR] After correcting the problems, you can resume the build with the
>>>>>>>> command
>>>>>>>> [ERROR] mvn <goals> -rf :nifi-hdfs-processors
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Nov 10, 2015, at 12:33 PM, Aldrin Piri <al...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Seems there is in fact an issue with the test cited prior. I received
>>>>>>>> the
>>>>>>>>> following on my Travis CI build on a branch which has the latest of
>>>>>>>> master
>>>>>>>>> merged into it. Unfortunately, it seems that the environment is not the
>>>>>>>>> same as before.
>>>>>>>>>
>>>>>>>>> In this case, Travis CI is running with Ubuntu 12.04 LTS [1]. For the
>>>>>>>>> particular build [2], Oracle JDK 7 built without issue, but Oracle JDK 8
>>>>>>>>> exhibited the same problem [3] as reported by Jeff.
>>>>>>>>>
>>>>>>>>> NIFI-1145 was created to track this issue [4]
>>>>>>>>>
>>>>>>>>> [1]
>>>>>>>>>
>>>>>>>> http://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
>>>>>>>>> [2] https://travis-ci.org/apiri/incubator-nifi/builds/90353191
>>>>>>>>> [3] https://s3.amazonaws.com/archive.travis-ci.org/jobs/90353192/log.txt
>>>>>>>>> [4] https://issues.apache.org/jira/browse/NIFI-1145
>>>>>>>>>
>>>>>>>>> On Thu, Nov 5, 2015 at 5:17 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I built a new VM CentOS7
>>>>>>>>>>
>>>>>>>>>> I get the below most of the time though last night it did succeeded.
>>>>>>>>>>
>>>>>>>>>> [INFO] nifi-framework-core ................................ FAILURE
>>>>>>>> [02:41
>>>>>>>>>> min]
>>>>>>>>>>
>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>> [INFO]
>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>> [INFO] Total time: 08:51 min (Wall Clock)
>>>>>>>>>> [INFO] Finished at: 2015-11-05T16:09:51-06:00
>>>>>>>>>> [INFO] Final Memory: 183M/514M
>>>>>>>>>> [INFO]
>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test)
>>>>>>>> on
>>>>>>>>>> project nifi-framework-core: There are test failures.
>>>>>>>>>> [ERROR]
>>>>>>>>>> [ERROR] Please refer to
>>>>>>>>>>
>>>>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>>> for the individual test results.
>>>>>>>>>> [ERROR] -> [Help 1]
>>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>>>>>> execute
>>>>>>>>>> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>>>>>>>> (default-test) on project nifi-framework-core: There are test failures.
>>>>>>>>>>
>>>>>>>>>> Please refer to
>>>>>>>>>>
>>>>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>>> for the individual test results.
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>>> 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:1142)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
>>>>>>>>>> failures.
>>>>>>>>>>
>>>>>>>>>> Please refer to
>>>>>>>>>>
>>>>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>>> for the individual test results.
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>>> ... 11 more
>>>>>>>>>> [ERROR]
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> On Nov 4, 2015, at 9:01 AM, Mark Payne <ma...@hotmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Jeff,
>>>>>>>>>>>
>>>>>>>>>>> I just checked out a fresh build from master, running on CentOS 7 and
>>>>>>>>>> was able to build without any problems.
>>>>>>>>>>> So I don't think it is specifically a problem with CentOS 7. Can you
>>>>>>>>>> provide the output of the unit tests?
>>>>>>>>>>>
>>>>>>>>>>> They should be in
>>>>>>>>>>
>>>>>>>> ${NIFI_SRC_DIR}/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>>>>
>>>>>>>>>>> The two files of interest are
>>>>>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue.txt and
>>>>>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue-output.txt
>>>>>>>>>>>
>>>>>>>>>>> Thanks!
>>>>>>>>>>> -Mark
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On Nov 4, 2015, at 8:53 AM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.916
>>>>>>>>>> sec <<< FAILURE! - in
>>>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> testDropSwappedFlowFiles(org.apache.nifi.controller.TestStandardFlowFileQueue)
>>>>>>>>>> Time elapsed: 21.825 sec <<< ERROR!
>>>>>>>>>>>> org.junit.runners.model.TestTimedOutException: test timed out after
>>>>>>>>>> 20000 milliseconds
>>>>>>>>>>>> at java.lang.Throwable.fillInStackTrace(Native Method)
>>>>>>>>>>>> at java.lang.Throwable.fillInStackTrace(Throwable.java:783)
>>>>>>>>>>>> at java.lang.Throwable.<init>(Throwable.java:250)
>>>>>>>>>>>> at
>>>>>>>>>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:24)
>>>>>>>>>>>> at
>>>>>>>>>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:19)
>>>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>> org.mockito.internal.invocation.InvocationImpl.<init>(InvocationImpl.java:50)
>>>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>> org.mockito.internal.creation.cglib.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:58)
>>>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>> org.apache.nifi.connectable.Connection$$EnhancerByMockitoWithCGLIB$$8aa704ad.getDestination(<generated>)
>>>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>> org.apache.nifi.controller.StandardFlowFileQueue.put(StandardFlowFileQueue.java:315)
>>>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue.testDropSwappedFlowFiles(TestStandardFlowFileQueue.java:169)
>>>>>>>>>>>>
>>>>>>>>>>>>> On Nov 4, 2015, at 7:51 AM, Brandon DeVries <br...@jhu.edu> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Jeff,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Can you see what tests had failures? Also, if you just want to
>>>>>>>> verify
>>>>>>>>>> that
>>>>>>>>>>>>> your system can do the build, you could do something like "mvn clean
>>>>>>>>>>>>> install -DskipTests". Let us know what you see. Thanks.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Brandon
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 8:46 AM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Well, the build got much further with the Oracle JDK but still
>>>>>>>> failed;
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>
>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>
>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>> [INFO] Total time: 07:47 min (Wall Clock)
>>>>>>>>>>>>>> [INFO] Finished at: 2015-11-03T17:07:40-06:00
>>>>>>>>>>>>>> [INFO] Final Memory: 183M/564M
>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>
>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>>>>>>>> (default-test) on
>>>>>>>>>>>>>> project nifi-framework-core: There are test failures.
>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>> [ERROR] Please refer to
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>>>>>>> for the individual test results.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:54 PM, Cerulean Blue <j....@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Oh, I also adjusted the memory!
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:50 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Jeff - can you please send another note telling Tony that it turns
>>>>>>>>>> out
>>>>>>>>>>>>>>>> it was memory settings :-)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> He is making fun of me off-list. He should totally do that
>>>>>>>> on-list!
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Glad you're in business now and sorry for my terrible
>>>>>>>> misdirection.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>> Huzzah
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I removed openjdk and installed the Oracle jdk and it now works.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks for the help!!
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> it is entirely possible that you only have the jre installed.
>>>>>>>>>> 'yum
>>>>>>>>>>>>>>>>>>> whatprovides "*/bin/javac"' may tell you packages which you can
>>>>>>>>>>>>>> install
>>>>>>>>>>>>>>>>>>> which include a compiler.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> find / -name javac did not return anything
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I had JAVA_HOME set to
>>>>>>>>>>>>>>>>>>>>
>>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Jeff,
>>>>>>>>>>>>>>>>>>>>> Were you able to run that find command?
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>>>> [INFO] Total time: 8.091 s
>>>>>>>>>>>>>>>>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
>>>>>>>>>>>>>>>>>>>>>> [INFO] Final Memory: 76M/365M
>>>>>>>>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>> ->
>>>>>>>>>>>>>> [Help 1]
>>>>>>>>>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>>>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run
>>>>>>>>>> Maven
>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>>> -e switch.
>>>>>>>>>>>>>>>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full
>>>>>>>> debug
>>>>>>>>>>>>>> logging.
>>>>>>>>>>>>>>>>>>>>>> [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/MojoFailureException
>>>>>>>>>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>>>>>>>>>> [ERROR] After correcting the problems, you can resume the
>>>>>>>>>> build
>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>>>> [ERROR] mvn <goals> -rf :nifi-api
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Can you go ahead and try just plain ol'
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> I am curious if there is a memory/settings issue that is
>>>>>>>>>>>>>> manifesting
>>>>>>>>>>>>>>>>>>>>>>> as an exception during compilation but that it isn't
>>>>>>>>>> actually a
>>>>>>>>>>>>>>>>>>>>>>> compilation problem at all...
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j.007ba7@gmail.com
>>>>>>>>>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>> The only other message I see is
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac'
>>>>>>>>>> from
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>>> environment.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> No worries, it can wait.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <joe.witt@gmail.com
>>>>>>>>>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to
>>>>>>>>>> pull
>>>>>>>>>>>>>> down
>>>>>>>>>>>>>>>>>>>>>>>>> centos. Is there anymore that can be found with those
>>>>>>>>>> stack
>>>>>>>>>>>>>>>>>> traces .
>>>>>>>>>>>>>>>>>>>>>>>>> They're not saying much. Your java and maven versions
>>>>>>>> seem
>>>>>>>>>>>>>> quite
>>>>>>>>>>>>>>>>>>>> good
>>>>>>>>>>>>>>>>>>>>>>>>> so need to dig further.
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <
>>>>>>>> j.007ba7@gmail.com
>>>>>>>>>>>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> [root@localhost nifi]# java -version
>>>>>>>>>>>>>>>>>>>>>>>>>> openjdk version "1.8.0_65"
>>>>>>>>>>>>>>>>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>>>>>>>>>>>>>>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> [root@localhost nifi]# mvn -version
>>>>>>>>>>>>>>>>>>>>>>>>>> which: no javac in
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>>>>>>>>>>>>>>>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set.
>>>>>>>>>>>>>>>>>>>>>>>>>> Apache Maven 3.3.3
>>>>>>>>>> (7994120775791599e205a5524ec3e0dfe41d4a06;
>>>>>>>>>>>>>>>>>>>>>> 2015-04-22T06:57:37-05:00)
>>>>>>>>>>>>>>>>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3
>>>>>>>>>>>>>>>>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>>>>>>>>>>>>>>>>>>>>>>>>> Java home:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>>>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>>>>>>>>>>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64",
>>>>>>>>>> arch:
>>>>>>>>>>>>>>>>>>>>>> "amd64", family: "unix"
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <
>>>>>>>> joe.witt@gmail.com
>>>>>>>>>>>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do
>>>>>>>>>> you
>>>>>>>>>>>>>> get
>>>>>>>>>>>>>>>>>>>> back?
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <
>>>>>>>>>> j.007ba7@gmail.com>
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>> I’m getting the below on a VM. It does build
>>>>>>>>>> successfully
>>>>>>>>>>>>>> on my
>>>>>>>>>>>>>>>>>>>>>> Mac, though.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install
>>>>>>>>>>>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>> ->
>>>>>>>>>>>>>> [Help 1]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException:
>>>>>>>>>>>>>> Failed
>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>>>> execute goal
>>>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>>>>>>>>>>>>>>>>>>>>> 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:1142)
>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>>>>>>>>>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Caused by:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>> org.apache.maven.plugin.compiler.CompilationFailureException:
>>>>>>>>>>>>>>>>>>>> Compilation
>>>>>>>>>>>>>>>>>>>>>> failure
>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>>>>>>>>>>>>>>>>>>>>> ... 11 more
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
>
Re: nifi fails build on CentOS 7
Posted by Jeff <j....@gmail.com>.
I created a nifi user on my VM, moved the /root/nifi folder to / and changed the owner of /nifi to nifi:nifi recursively
I executed mvn -e -X -T 2.0C clean install as the nifi user
Below is the error;
Downloaded: https://repo1.maven.org/maven2/com/yammer/metrics/metrics-ganglia/2.2.0/metrics-ganglia-2.2.0.jar (12 KB at 3.8 KB/sec)
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-clean-plugin:2.5:clean (default-clean) on project nifi-hdfs-processors: Failed to clean project: Failed to delete /nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/testPutFileWrongPermissions -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-clean-plugin:2.5:clean (default-clean) on project nifi-hdfs-processors: Failed to clean project: Failed to delete /nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/testPutFileWrongPermissions
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
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:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to clean project: Failed to delete /nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/testPutFileWrongPermissions
at org.apache.maven.plugin.clean.CleanMojo.execute(CleanMojo.java:215)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 11 more
Caused by: java.io.IOException: Failed to delete /nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/testPutFileWrongPermissions
at org.apache.maven.plugin.clean.Cleaner.delete(Cleaner.java:249)
at org.apache.maven.plugin.clean.Cleaner.delete(Cleaner.java:191)
at org.apache.maven.plugin.clean.Cleaner.delete(Cleaner.java:158)
at org.apache.maven.plugin.clean.Cleaner.delete(Cleaner.java:117)
at org.apache.maven.plugin.clean.CleanMojo.execute(CleanMojo.java:193)
... 13 more
[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 <goals> -rf :nifi-hdfs-processors
[DEBUG] incrementalBuildHelper#afterRebuildExecution
[INFO]
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ nifi-standard-prioritizers ---
[DEBUG] Configuring mojo org.apache.maven.plugins:maven-resources-plugin:2.7:testResources from plugin realm ClassRealm[plugin>org.apache.maven.plugins:maven-resources-plugin:2.7, parent: sun.misc.Launcher$AppClassLoader@70dea4e]
Downloaded: https://repo1.maven.org/maven2/com/yammer/metrics/metrics-core/2.2.0/metrics-core-2.2.0.jar (81 KB at 26.7 KB/sec)
> On Dec 7, 2015, at 4:05 PM, Joe Witt <jo...@gmail.com> wrote:
>
> we now understand the TestPutHDFS issue.
> https://issues.apache.org/jira/browse/NIFI-1267
>
> The test assumes that a user would not be able to write to a file
> unless it has write perms. However, root can do that. So users
> building as root would see this.
>
> Thanks
> Joe
>
> On Mon, Dec 7, 2015 at 4:45 PM, Joe Witt <jo...@gmail.com> wrote:
>> jeff - out of curiosity can you confirm you're running as root on that
>> VM when you build?
>>
>> On Mon, Dec 7, 2015 at 4:42 PM, Jeff <j....@gmail.com> wrote:
>>> Hi Joe,
>>>
>>> You are welcome. Below is what I’m seeing
>>>
>>> -------------------------------------------------------------------------------
>>> Test set: org.apache.nifi.processors.hadoop.PutHDFSTest
>>> -------------------------------------------------------------------------------
>>> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.949 sec <<< FAILURE! - in org.apache.nifi.processors.hadoop.PutHDFSTest
>>> testPutFileWithException(org.apache.nifi.processors.hadoop.PutHDFSTest) Time elapsed: 0.532 sec <<< FAILURE!
>>> java.lang.AssertionError: null
>>> at org.junit.Assert.fail(Assert.java:86)
>>> at org.junit.Assert.assertTrue(Assert.java:41)
>>> at org.junit.Assert.assertFalse(Assert.java:64)
>>> at org.junit.Assert.assertFalse(Assert.java:74)
>>> at org.apache.nifi.processors.hadoop.PutHDFSTest.testPutFileWithException(PutHDFSTest.java:230)
>>>
>>>> On Dec 7, 2015, at 3:36 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>
>>>> thanks for reporting this Jeff and your timing could not have been better!
>>>>
>>>> It's happening for Gilman as well.
>>>>
>>>> Joe
>>>>
>>>> On Mon, Dec 7, 2015 at 4:31 PM, Jeff <j....@gmail.com> wrote:
>>>>> Yes, CentOS 7
>>>>>
>>>>> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.703 sec - in org.apache.nifi.processors.hadoop.TestListHDFS
>>>>>
>>>>> Results :
>>>>>
>>>>> Failed tests:
>>>>> PutHDFSTest.testPutFileWithException:230 null
>>>>>
>>>>>
>>>>>
>>>>> Tests run: 21, Failures: 1, Errors: 0, Skipped: 0
>>>>>
>>>>>
>>>>>
>>>>>> On Dec 7, 2015, at 3:28 PM, Matt Gilman <ma...@gmail.com> wrote:
>>>>>>
>>>>>> Jeff,
>>>>>>
>>>>>> Are you still running on CentOS 7? Can you provide more details about the
>>>>>> unit test is failing? Thanks!
>>>>>>
>>>>>> Matt
>>>>>>
>>>>>> On Mon, Dec 7, 2015 at 4:24 PM, Jeff <j....@gmail.com> wrote:
>>>>>>
>>>>>>> I just cloned Nifi but I’m still seeing these errors when I do mvn -e -X
>>>>>>> -T 2.0C clean install
>>>>>>>
>>>>>>> [ERROR] Failed to execute goal
>>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
>>>>>>> project nifi-hdfs-processors: There are test failures.
>>>>>>> [ERROR]
>>>>>>> [ERROR] Please refer to
>>>>>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>>>>>> for the individual test results.
>>>>>>> [ERROR] -> [Help 1]
>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>>>>>>> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>>>>> (default-test) on project nifi-hdfs-processors: There are test failures.
>>>>>>>
>>>>>>> Please refer to
>>>>>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>>>>>> for the individual test results.
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>> 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:1142)
>>>>>>> at
>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
>>>>>>> failures.
>>>>>>>
>>>>>>> Please refer to
>>>>>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>>>>>> for the individual test results.
>>>>>>> at
>>>>>>> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
>>>>>>> at
>>>>>>> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
>>>>>>> at
>>>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
>>>>>>> at
>>>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>>>>>>> at
>>>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>> ... 11 more
>>>>>>> [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/MojoFailureException
>>>>>>> [ERROR]
>>>>>>> [ERROR] After correcting the problems, you can resume the build with the
>>>>>>> command
>>>>>>> [ERROR] mvn <goals> -rf :nifi-hdfs-processors
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> On Nov 10, 2015, at 12:33 PM, Aldrin Piri <al...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> Seems there is in fact an issue with the test cited prior. I received
>>>>>>> the
>>>>>>>> following on my Travis CI build on a branch which has the latest of
>>>>>>> master
>>>>>>>> merged into it. Unfortunately, it seems that the environment is not the
>>>>>>>> same as before.
>>>>>>>>
>>>>>>>> In this case, Travis CI is running with Ubuntu 12.04 LTS [1]. For the
>>>>>>>> particular build [2], Oracle JDK 7 built without issue, but Oracle JDK 8
>>>>>>>> exhibited the same problem [3] as reported by Jeff.
>>>>>>>>
>>>>>>>> NIFI-1145 was created to track this issue [4]
>>>>>>>>
>>>>>>>> [1]
>>>>>>>>
>>>>>>> http://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
>>>>>>>> [2] https://travis-ci.org/apiri/incubator-nifi/builds/90353191
>>>>>>>> [3] https://s3.amazonaws.com/archive.travis-ci.org/jobs/90353192/log.txt
>>>>>>>> [4] https://issues.apache.org/jira/browse/NIFI-1145
>>>>>>>>
>>>>>>>> On Thu, Nov 5, 2015 at 5:17 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I built a new VM CentOS7
>>>>>>>>>
>>>>>>>>> I get the below most of the time though last night it did succeeded.
>>>>>>>>>
>>>>>>>>> [INFO] nifi-framework-core ................................ FAILURE
>>>>>>> [02:41
>>>>>>>>> min]
>>>>>>>>>
>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>> [INFO]
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>> [INFO] Total time: 08:51 min (Wall Clock)
>>>>>>>>> [INFO] Finished at: 2015-11-05T16:09:51-06:00
>>>>>>>>> [INFO] Final Memory: 183M/514M
>>>>>>>>> [INFO]
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test)
>>>>>>> on
>>>>>>>>> project nifi-framework-core: There are test failures.
>>>>>>>>> [ERROR]
>>>>>>>>> [ERROR] Please refer to
>>>>>>>>>
>>>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>> for the individual test results.
>>>>>>>>> [ERROR] -> [Help 1]
>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>>>>> execute
>>>>>>>>> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>>>>>>> (default-test) on project nifi-framework-core: There are test failures.
>>>>>>>>>
>>>>>>>>> Please refer to
>>>>>>>>>
>>>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>> for the individual test results.
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>> 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:1142)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
>>>>>>>>> failures.
>>>>>>>>>
>>>>>>>>> Please refer to
>>>>>>>>>
>>>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>> for the individual test results.
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>> ... 11 more
>>>>>>>>> [ERROR]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On Nov 4, 2015, at 9:01 AM, Mark Payne <ma...@hotmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Jeff,
>>>>>>>>>>
>>>>>>>>>> I just checked out a fresh build from master, running on CentOS 7 and
>>>>>>>>> was able to build without any problems.
>>>>>>>>>> So I don't think it is specifically a problem with CentOS 7. Can you
>>>>>>>>> provide the output of the unit tests?
>>>>>>>>>>
>>>>>>>>>> They should be in
>>>>>>>>>
>>>>>>> ${NIFI_SRC_DIR}/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>>>
>>>>>>>>>> The two files of interest are
>>>>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue.txt and
>>>>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue-output.txt
>>>>>>>>>>
>>>>>>>>>> Thanks!
>>>>>>>>>> -Mark
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> On Nov 4, 2015, at 8:53 AM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.916
>>>>>>>>> sec <<< FAILURE! - in
>>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> testDropSwappedFlowFiles(org.apache.nifi.controller.TestStandardFlowFileQueue)
>>>>>>>>> Time elapsed: 21.825 sec <<< ERROR!
>>>>>>>>>>> org.junit.runners.model.TestTimedOutException: test timed out after
>>>>>>>>> 20000 milliseconds
>>>>>>>>>>> at java.lang.Throwable.fillInStackTrace(Native Method)
>>>>>>>>>>> at java.lang.Throwable.fillInStackTrace(Throwable.java:783)
>>>>>>>>>>> at java.lang.Throwable.<init>(Throwable.java:250)
>>>>>>>>>>> at
>>>>>>>>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:24)
>>>>>>>>>>> at
>>>>>>>>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:19)
>>>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.mockito.internal.invocation.InvocationImpl.<init>(InvocationImpl.java:50)
>>>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.mockito.internal.creation.cglib.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:58)
>>>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.nifi.connectable.Connection$$EnhancerByMockitoWithCGLIB$$8aa704ad.getDestination(<generated>)
>>>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.nifi.controller.StandardFlowFileQueue.put(StandardFlowFileQueue.java:315)
>>>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue.testDropSwappedFlowFiles(TestStandardFlowFileQueue.java:169)
>>>>>>>>>>>
>>>>>>>>>>>> On Nov 4, 2015, at 7:51 AM, Brandon DeVries <br...@jhu.edu> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Jeff,
>>>>>>>>>>>>
>>>>>>>>>>>> Can you see what tests had failures? Also, if you just want to
>>>>>>> verify
>>>>>>>>> that
>>>>>>>>>>>> your system can do the build, you could do something like "mvn clean
>>>>>>>>>>>> install -DskipTests". Let us know what you see. Thanks.
>>>>>>>>>>>>
>>>>>>>>>>>> Brandon
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Nov 4, 2015 at 8:46 AM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Well, the build got much further with the Oracle JDK but still
>>>>>>> failed;
>>>>>>>>>>>>>
>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>> [INFO] Total time: 07:47 min (Wall Clock)
>>>>>>>>>>>>> [INFO] Finished at: 2015-11-03T17:07:40-06:00
>>>>>>>>>>>>> [INFO] Final Memory: 183M/564M
>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>>>>>>> (default-test) on
>>>>>>>>>>>>> project nifi-framework-core: There are test failures.
>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>> [ERROR] Please refer to
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>>>>>> for the individual test results.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Nov 3, 2015, at 6:54 PM, Cerulean Blue <j....@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Oh, I also adjusted the memory!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:50 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Jeff - can you please send another note telling Tony that it turns
>>>>>>>>> out
>>>>>>>>>>>>>>> it was memory settings :-)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> He is making fun of me off-list. He should totally do that
>>>>>>> on-list!
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Glad you're in business now and sorry for my terrible
>>>>>>> misdirection.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> Huzzah
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com>
>>>>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I removed openjdk and installed the Oracle jdk and it now works.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks for the help!!
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com>
>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> it is entirely possible that you only have the jre installed.
>>>>>>>>> 'yum
>>>>>>>>>>>>>>>>>> whatprovides "*/bin/javac"' may tell you packages which you can
>>>>>>>>>>>>> install
>>>>>>>>>>>>>>>>>> which include a compiler.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> find / -name javac did not return anything
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I had JAVA_HOME set to
>>>>>>>>>>>>>>>>>>>
>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Jeff,
>>>>>>>>>>>>>>>>>>>> Were you able to run that find command?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>>> [INFO] Total time: 8.091 s
>>>>>>>>>>>>>>>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
>>>>>>>>>>>>>>>>>>>>> [INFO] Final Memory: 76M/365M
>>>>>>>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>> ->
>>>>>>>>>>>>> [Help 1]
>>>>>>>>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run
>>>>>>>>> Maven
>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>> -e switch.
>>>>>>>>>>>>>>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full
>>>>>>> debug
>>>>>>>>>>>>> logging.
>>>>>>>>>>>>>>>>>>>>> [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/MojoFailureException
>>>>>>>>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>>>>>>>>> [ERROR] After correcting the problems, you can resume the
>>>>>>>>> build
>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>>> [ERROR] mvn <goals> -rf :nifi-api
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Can you go ahead and try just plain ol'
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> I am curious if there is a memory/settings issue that is
>>>>>>>>>>>>> manifesting
>>>>>>>>>>>>>>>>>>>>>> as an exception during compilation but that it isn't
>>>>>>>>> actually a
>>>>>>>>>>>>>>>>>>>>>> compilation problem at all...
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j.007ba7@gmail.com
>>>>>>>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>> The only other message I see is
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac'
>>>>>>>>> from
>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>> environment.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> No worries, it can wait.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <joe.witt@gmail.com
>>>>>>>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to
>>>>>>>>> pull
>>>>>>>>>>>>> down
>>>>>>>>>>>>>>>>>>>>>>>> centos. Is there anymore that can be found with those
>>>>>>>>> stack
>>>>>>>>>>>>>>>>> traces .
>>>>>>>>>>>>>>>>>>>>>>>> They're not saying much. Your java and maven versions
>>>>>>> seem
>>>>>>>>>>>>> quite
>>>>>>>>>>>>>>>>>>> good
>>>>>>>>>>>>>>>>>>>>>>>> so need to dig further.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <
>>>>>>> j.007ba7@gmail.com
>>>>>>>>>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> [root@localhost nifi]# java -version
>>>>>>>>>>>>>>>>>>>>>>>>> openjdk version "1.8.0_65"
>>>>>>>>>>>>>>>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>>>>>>>>>>>>>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> [root@localhost nifi]# mvn -version
>>>>>>>>>>>>>>>>>>>>>>>>> which: no javac in
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>>>>>>>>>>>>>>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set.
>>>>>>>>>>>>>>>>>>>>>>>>> Apache Maven 3.3.3
>>>>>>>>> (7994120775791599e205a5524ec3e0dfe41d4a06;
>>>>>>>>>>>>>>>>>>>>> 2015-04-22T06:57:37-05:00)
>>>>>>>>>>>>>>>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3
>>>>>>>>>>>>>>>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>>>>>>>>>>>>>>>>>>>>>>>> Java home:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>>>>>>>>>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64",
>>>>>>>>> arch:
>>>>>>>>>>>>>>>>>>>>> "amd64", family: "unix"
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <
>>>>>>> joe.witt@gmail.com
>>>>>>>>>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do
>>>>>>>>> you
>>>>>>>>>>>>> get
>>>>>>>>>>>>>>>>>>> back?
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <
>>>>>>>>> j.007ba7@gmail.com>
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>> I’m getting the below on a VM. It does build
>>>>>>>>> successfully
>>>>>>>>>>>>> on my
>>>>>>>>>>>>>>>>>>>>> Mac, though.
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install
>>>>>>>>>>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>> ->
>>>>>>>>>>>>> [Help 1]
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException:
>>>>>>>>>>>>> Failed
>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>>> execute goal
>>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>>>>>>>>>>>>>>>>>>>> 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:1142)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>>>>>>>>>>>>>>>>>>>> Caused by:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>> org.apache.maven.plugin.compiler.CompilationFailureException:
>>>>>>>>>>>>>>>>>>> Compilation
>>>>>>>>>>>>>>>>>>>>> failure
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>>>>>>>>>>>>>>>>>>>> ... 11 more
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>
Re: nifi fails build on CentOS 7
Posted by Jeff <j....@gmail.com>.
yes, I’m running as root
> On Dec 7, 2015, at 4:05 PM, Joe Witt <jo...@gmail.com> wrote:
>
> we now understand the TestPutHDFS issue.
> https://issues.apache.org/jira/browse/NIFI-1267
>
> The test assumes that a user would not be able to write to a file
> unless it has write perms. However, root can do that. So users
> building as root would see this.
>
> Thanks
> Joe
>
> On Mon, Dec 7, 2015 at 4:45 PM, Joe Witt <jo...@gmail.com> wrote:
>> jeff - out of curiosity can you confirm you're running as root on that
>> VM when you build?
>>
>> On Mon, Dec 7, 2015 at 4:42 PM, Jeff <j....@gmail.com> wrote:
>>> Hi Joe,
>>>
>>> You are welcome. Below is what I’m seeing
>>>
>>> -------------------------------------------------------------------------------
>>> Test set: org.apache.nifi.processors.hadoop.PutHDFSTest
>>> -------------------------------------------------------------------------------
>>> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.949 sec <<< FAILURE! - in org.apache.nifi.processors.hadoop.PutHDFSTest
>>> testPutFileWithException(org.apache.nifi.processors.hadoop.PutHDFSTest) Time elapsed: 0.532 sec <<< FAILURE!
>>> java.lang.AssertionError: null
>>> at org.junit.Assert.fail(Assert.java:86)
>>> at org.junit.Assert.assertTrue(Assert.java:41)
>>> at org.junit.Assert.assertFalse(Assert.java:64)
>>> at org.junit.Assert.assertFalse(Assert.java:74)
>>> at org.apache.nifi.processors.hadoop.PutHDFSTest.testPutFileWithException(PutHDFSTest.java:230)
>>>
>>>> On Dec 7, 2015, at 3:36 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>
>>>> thanks for reporting this Jeff and your timing could not have been better!
>>>>
>>>> It's happening for Gilman as well.
>>>>
>>>> Joe
>>>>
>>>> On Mon, Dec 7, 2015 at 4:31 PM, Jeff <j....@gmail.com> wrote:
>>>>> Yes, CentOS 7
>>>>>
>>>>> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.703 sec - in org.apache.nifi.processors.hadoop.TestListHDFS
>>>>>
>>>>> Results :
>>>>>
>>>>> Failed tests:
>>>>> PutHDFSTest.testPutFileWithException:230 null
>>>>>
>>>>>
>>>>>
>>>>> Tests run: 21, Failures: 1, Errors: 0, Skipped: 0
>>>>>
>>>>>
>>>>>
>>>>>> On Dec 7, 2015, at 3:28 PM, Matt Gilman <ma...@gmail.com> wrote:
>>>>>>
>>>>>> Jeff,
>>>>>>
>>>>>> Are you still running on CentOS 7? Can you provide more details about the
>>>>>> unit test is failing? Thanks!
>>>>>>
>>>>>> Matt
>>>>>>
>>>>>> On Mon, Dec 7, 2015 at 4:24 PM, Jeff <j....@gmail.com> wrote:
>>>>>>
>>>>>>> I just cloned Nifi but I’m still seeing these errors when I do mvn -e -X
>>>>>>> -T 2.0C clean install
>>>>>>>
>>>>>>> [ERROR] Failed to execute goal
>>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
>>>>>>> project nifi-hdfs-processors: There are test failures.
>>>>>>> [ERROR]
>>>>>>> [ERROR] Please refer to
>>>>>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>>>>>> for the individual test results.
>>>>>>> [ERROR] -> [Help 1]
>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>>>>>>> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>>>>> (default-test) on project nifi-hdfs-processors: There are test failures.
>>>>>>>
>>>>>>> Please refer to
>>>>>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>>>>>> for the individual test results.
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>> 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:1142)
>>>>>>> at
>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
>>>>>>> failures.
>>>>>>>
>>>>>>> Please refer to
>>>>>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>>>>>> for the individual test results.
>>>>>>> at
>>>>>>> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
>>>>>>> at
>>>>>>> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
>>>>>>> at
>>>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
>>>>>>> at
>>>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>>>>>>> at
>>>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>> ... 11 more
>>>>>>> [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/MojoFailureException
>>>>>>> [ERROR]
>>>>>>> [ERROR] After correcting the problems, you can resume the build with the
>>>>>>> command
>>>>>>> [ERROR] mvn <goals> -rf :nifi-hdfs-processors
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> On Nov 10, 2015, at 12:33 PM, Aldrin Piri <al...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> Seems there is in fact an issue with the test cited prior. I received
>>>>>>> the
>>>>>>>> following on my Travis CI build on a branch which has the latest of
>>>>>>> master
>>>>>>>> merged into it. Unfortunately, it seems that the environment is not the
>>>>>>>> same as before.
>>>>>>>>
>>>>>>>> In this case, Travis CI is running with Ubuntu 12.04 LTS [1]. For the
>>>>>>>> particular build [2], Oracle JDK 7 built without issue, but Oracle JDK 8
>>>>>>>> exhibited the same problem [3] as reported by Jeff.
>>>>>>>>
>>>>>>>> NIFI-1145 was created to track this issue [4]
>>>>>>>>
>>>>>>>> [1]
>>>>>>>>
>>>>>>> http://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
>>>>>>>> [2] https://travis-ci.org/apiri/incubator-nifi/builds/90353191
>>>>>>>> [3] https://s3.amazonaws.com/archive.travis-ci.org/jobs/90353192/log.txt
>>>>>>>> [4] https://issues.apache.org/jira/browse/NIFI-1145
>>>>>>>>
>>>>>>>> On Thu, Nov 5, 2015 at 5:17 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I built a new VM CentOS7
>>>>>>>>>
>>>>>>>>> I get the below most of the time though last night it did succeeded.
>>>>>>>>>
>>>>>>>>> [INFO] nifi-framework-core ................................ FAILURE
>>>>>>> [02:41
>>>>>>>>> min]
>>>>>>>>>
>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>> [INFO]
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>> [INFO] Total time: 08:51 min (Wall Clock)
>>>>>>>>> [INFO] Finished at: 2015-11-05T16:09:51-06:00
>>>>>>>>> [INFO] Final Memory: 183M/514M
>>>>>>>>> [INFO]
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test)
>>>>>>> on
>>>>>>>>> project nifi-framework-core: There are test failures.
>>>>>>>>> [ERROR]
>>>>>>>>> [ERROR] Please refer to
>>>>>>>>>
>>>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>> for the individual test results.
>>>>>>>>> [ERROR] -> [Help 1]
>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>>>>> execute
>>>>>>>>> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>>>>>>> (default-test) on project nifi-framework-core: There are test failures.
>>>>>>>>>
>>>>>>>>> Please refer to
>>>>>>>>>
>>>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>> for the individual test results.
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>> 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:1142)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
>>>>>>>>> failures.
>>>>>>>>>
>>>>>>>>> Please refer to
>>>>>>>>>
>>>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>> for the individual test results.
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>> ... 11 more
>>>>>>>>> [ERROR]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On Nov 4, 2015, at 9:01 AM, Mark Payne <ma...@hotmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Jeff,
>>>>>>>>>>
>>>>>>>>>> I just checked out a fresh build from master, running on CentOS 7 and
>>>>>>>>> was able to build without any problems.
>>>>>>>>>> So I don't think it is specifically a problem with CentOS 7. Can you
>>>>>>>>> provide the output of the unit tests?
>>>>>>>>>>
>>>>>>>>>> They should be in
>>>>>>>>>
>>>>>>> ${NIFI_SRC_DIR}/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>>>
>>>>>>>>>> The two files of interest are
>>>>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue.txt and
>>>>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue-output.txt
>>>>>>>>>>
>>>>>>>>>> Thanks!
>>>>>>>>>> -Mark
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> On Nov 4, 2015, at 8:53 AM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.916
>>>>>>>>> sec <<< FAILURE! - in
>>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> testDropSwappedFlowFiles(org.apache.nifi.controller.TestStandardFlowFileQueue)
>>>>>>>>> Time elapsed: 21.825 sec <<< ERROR!
>>>>>>>>>>> org.junit.runners.model.TestTimedOutException: test timed out after
>>>>>>>>> 20000 milliseconds
>>>>>>>>>>> at java.lang.Throwable.fillInStackTrace(Native Method)
>>>>>>>>>>> at java.lang.Throwable.fillInStackTrace(Throwable.java:783)
>>>>>>>>>>> at java.lang.Throwable.<init>(Throwable.java:250)
>>>>>>>>>>> at
>>>>>>>>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:24)
>>>>>>>>>>> at
>>>>>>>>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:19)
>>>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.mockito.internal.invocation.InvocationImpl.<init>(InvocationImpl.java:50)
>>>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.mockito.internal.creation.cglib.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:58)
>>>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.nifi.connectable.Connection$$EnhancerByMockitoWithCGLIB$$8aa704ad.getDestination(<generated>)
>>>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.nifi.controller.StandardFlowFileQueue.put(StandardFlowFileQueue.java:315)
>>>>>>>>>>> at
>>>>>>>>>
>>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue.testDropSwappedFlowFiles(TestStandardFlowFileQueue.java:169)
>>>>>>>>>>>
>>>>>>>>>>>> On Nov 4, 2015, at 7:51 AM, Brandon DeVries <br...@jhu.edu> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Jeff,
>>>>>>>>>>>>
>>>>>>>>>>>> Can you see what tests had failures? Also, if you just want to
>>>>>>> verify
>>>>>>>>> that
>>>>>>>>>>>> your system can do the build, you could do something like "mvn clean
>>>>>>>>>>>> install -DskipTests". Let us know what you see. Thanks.
>>>>>>>>>>>>
>>>>>>>>>>>> Brandon
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Nov 4, 2015 at 8:46 AM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Well, the build got much further with the Oracle JDK but still
>>>>>>> failed;
>>>>>>>>>>>>>
>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>> [INFO] Total time: 07:47 min (Wall Clock)
>>>>>>>>>>>>> [INFO] Finished at: 2015-11-03T17:07:40-06:00
>>>>>>>>>>>>> [INFO] Final Memory: 183M/564M
>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>>>>>>> (default-test) on
>>>>>>>>>>>>> project nifi-framework-core: There are test failures.
>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>> [ERROR] Please refer to
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>>>>>> for the individual test results.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Nov 3, 2015, at 6:54 PM, Cerulean Blue <j....@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Oh, I also adjusted the memory!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:50 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Jeff - can you please send another note telling Tony that it turns
>>>>>>>>> out
>>>>>>>>>>>>>>> it was memory settings :-)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> He is making fun of me off-list. He should totally do that
>>>>>>> on-list!
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Glad you're in business now and sorry for my terrible
>>>>>>> misdirection.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> Huzzah
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com>
>>>>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I removed openjdk and installed the Oracle jdk and it now works.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks for the help!!
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com>
>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> it is entirely possible that you only have the jre installed.
>>>>>>>>> 'yum
>>>>>>>>>>>>>>>>>> whatprovides "*/bin/javac"' may tell you packages which you can
>>>>>>>>>>>>> install
>>>>>>>>>>>>>>>>>> which include a compiler.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> find / -name javac did not return anything
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I had JAVA_HOME set to
>>>>>>>>>>>>>>>>>>>
>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Jeff,
>>>>>>>>>>>>>>>>>>>> Were you able to run that find command?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>>> [INFO] Total time: 8.091 s
>>>>>>>>>>>>>>>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
>>>>>>>>>>>>>>>>>>>>> [INFO] Final Memory: 76M/365M
>>>>>>>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>> ->
>>>>>>>>>>>>> [Help 1]
>>>>>>>>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run
>>>>>>>>> Maven
>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>> -e switch.
>>>>>>>>>>>>>>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full
>>>>>>> debug
>>>>>>>>>>>>> logging.
>>>>>>>>>>>>>>>>>>>>> [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/MojoFailureException
>>>>>>>>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>>>>>>>>> [ERROR] After correcting the problems, you can resume the
>>>>>>>>> build
>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>>> [ERROR] mvn <goals> -rf :nifi-api
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Can you go ahead and try just plain ol'
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> I am curious if there is a memory/settings issue that is
>>>>>>>>>>>>> manifesting
>>>>>>>>>>>>>>>>>>>>>> as an exception during compilation but that it isn't
>>>>>>>>> actually a
>>>>>>>>>>>>>>>>>>>>>> compilation problem at all...
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j.007ba7@gmail.com
>>>>>>>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>> The only other message I see is
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac'
>>>>>>>>> from
>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>> environment.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> No worries, it can wait.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <joe.witt@gmail.com
>>>>>>>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to
>>>>>>>>> pull
>>>>>>>>>>>>> down
>>>>>>>>>>>>>>>>>>>>>>>> centos. Is there anymore that can be found with those
>>>>>>>>> stack
>>>>>>>>>>>>>>>>> traces .
>>>>>>>>>>>>>>>>>>>>>>>> They're not saying much. Your java and maven versions
>>>>>>> seem
>>>>>>>>>>>>> quite
>>>>>>>>>>>>>>>>>>> good
>>>>>>>>>>>>>>>>>>>>>>>> so need to dig further.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <
>>>>>>> j.007ba7@gmail.com
>>>>>>>>>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> [root@localhost nifi]# java -version
>>>>>>>>>>>>>>>>>>>>>>>>> openjdk version "1.8.0_65"
>>>>>>>>>>>>>>>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>>>>>>>>>>>>>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> [root@localhost nifi]# mvn -version
>>>>>>>>>>>>>>>>>>>>>>>>> which: no javac in
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>>>>>>>>>>>>>>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set.
>>>>>>>>>>>>>>>>>>>>>>>>> Apache Maven 3.3.3
>>>>>>>>> (7994120775791599e205a5524ec3e0dfe41d4a06;
>>>>>>>>>>>>>>>>>>>>> 2015-04-22T06:57:37-05:00)
>>>>>>>>>>>>>>>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3
>>>>>>>>>>>>>>>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>>>>>>>>>>>>>>>>>>>>>>>> Java home:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>>>>>>>>>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64",
>>>>>>>>> arch:
>>>>>>>>>>>>>>>>>>>>> "amd64", family: "unix"
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <
>>>>>>> joe.witt@gmail.com
>>>>>>>>>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do
>>>>>>>>> you
>>>>>>>>>>>>> get
>>>>>>>>>>>>>>>>>>> back?
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <
>>>>>>>>> j.007ba7@gmail.com>
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>> I’m getting the below on a VM. It does build
>>>>>>>>> successfully
>>>>>>>>>>>>> on my
>>>>>>>>>>>>>>>>>>>>> Mac, though.
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install
>>>>>>>>>>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>> ->
>>>>>>>>>>>>> [Help 1]
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException:
>>>>>>>>>>>>> Failed
>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>>> execute goal
>>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>>>>>>>>>>>>>>>>>>>> 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:1142)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>>>>>>>>>>>>>>>>>>>> Caused by:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>> org.apache.maven.plugin.compiler.CompilationFailureException:
>>>>>>>>>>>>>>>>>>> Compilation
>>>>>>>>>>>>>>>>>>>>> failure
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>>>>>>>>>>>>>>>>>>>> ... 11 more
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>
Re: nifi fails build on CentOS 7
Posted by Joe Witt <jo...@gmail.com>.
we now understand the TestPutHDFS issue.
https://issues.apache.org/jira/browse/NIFI-1267
The test assumes that a user would not be able to write to a file
unless it has write perms. However, root can do that. So users
building as root would see this.
Thanks
Joe
On Mon, Dec 7, 2015 at 4:45 PM, Joe Witt <jo...@gmail.com> wrote:
> jeff - out of curiosity can you confirm you're running as root on that
> VM when you build?
>
> On Mon, Dec 7, 2015 at 4:42 PM, Jeff <j....@gmail.com> wrote:
>> Hi Joe,
>>
>> You are welcome. Below is what I’m seeing
>>
>> -------------------------------------------------------------------------------
>> Test set: org.apache.nifi.processors.hadoop.PutHDFSTest
>> -------------------------------------------------------------------------------
>> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.949 sec <<< FAILURE! - in org.apache.nifi.processors.hadoop.PutHDFSTest
>> testPutFileWithException(org.apache.nifi.processors.hadoop.PutHDFSTest) Time elapsed: 0.532 sec <<< FAILURE!
>> java.lang.AssertionError: null
>> at org.junit.Assert.fail(Assert.java:86)
>> at org.junit.Assert.assertTrue(Assert.java:41)
>> at org.junit.Assert.assertFalse(Assert.java:64)
>> at org.junit.Assert.assertFalse(Assert.java:74)
>> at org.apache.nifi.processors.hadoop.PutHDFSTest.testPutFileWithException(PutHDFSTest.java:230)
>>
>>> On Dec 7, 2015, at 3:36 PM, Joe Witt <jo...@gmail.com> wrote:
>>>
>>> thanks for reporting this Jeff and your timing could not have been better!
>>>
>>> It's happening for Gilman as well.
>>>
>>> Joe
>>>
>>> On Mon, Dec 7, 2015 at 4:31 PM, Jeff <j....@gmail.com> wrote:
>>>> Yes, CentOS 7
>>>>
>>>> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.703 sec - in org.apache.nifi.processors.hadoop.TestListHDFS
>>>>
>>>> Results :
>>>>
>>>> Failed tests:
>>>> PutHDFSTest.testPutFileWithException:230 null
>>>>
>>>>
>>>>
>>>> Tests run: 21, Failures: 1, Errors: 0, Skipped: 0
>>>>
>>>>
>>>>
>>>>> On Dec 7, 2015, at 3:28 PM, Matt Gilman <ma...@gmail.com> wrote:
>>>>>
>>>>> Jeff,
>>>>>
>>>>> Are you still running on CentOS 7? Can you provide more details about the
>>>>> unit test is failing? Thanks!
>>>>>
>>>>> Matt
>>>>>
>>>>> On Mon, Dec 7, 2015 at 4:24 PM, Jeff <j....@gmail.com> wrote:
>>>>>
>>>>>> I just cloned Nifi but I’m still seeing these errors when I do mvn -e -X
>>>>>> -T 2.0C clean install
>>>>>>
>>>>>> [ERROR] Failed to execute goal
>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
>>>>>> project nifi-hdfs-processors: There are test failures.
>>>>>> [ERROR]
>>>>>> [ERROR] Please refer to
>>>>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>>>>> for the individual test results.
>>>>>> [ERROR] -> [Help 1]
>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>>>>>> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>>>> (default-test) on project nifi-hdfs-processors: There are test failures.
>>>>>>
>>>>>> Please refer to
>>>>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>>>>> for the individual test results.
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>> 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:1142)
>>>>>> at
>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
>>>>>> failures.
>>>>>>
>>>>>> Please refer to
>>>>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>>>>> for the individual test results.
>>>>>> at
>>>>>> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
>>>>>> at
>>>>>> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
>>>>>> at
>>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
>>>>>> at
>>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>>>>>> at
>>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>> ... 11 more
>>>>>> [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/MojoFailureException
>>>>>> [ERROR]
>>>>>> [ERROR] After correcting the problems, you can resume the build with the
>>>>>> command
>>>>>> [ERROR] mvn <goals> -rf :nifi-hdfs-processors
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On Nov 10, 2015, at 12:33 PM, Aldrin Piri <al...@gmail.com> wrote:
>>>>>>>
>>>>>>> Seems there is in fact an issue with the test cited prior. I received
>>>>>> the
>>>>>>> following on my Travis CI build on a branch which has the latest of
>>>>>> master
>>>>>>> merged into it. Unfortunately, it seems that the environment is not the
>>>>>>> same as before.
>>>>>>>
>>>>>>> In this case, Travis CI is running with Ubuntu 12.04 LTS [1]. For the
>>>>>>> particular build [2], Oracle JDK 7 built without issue, but Oracle JDK 8
>>>>>>> exhibited the same problem [3] as reported by Jeff.
>>>>>>>
>>>>>>> NIFI-1145 was created to track this issue [4]
>>>>>>>
>>>>>>> [1]
>>>>>>>
>>>>>> http://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
>>>>>>> [2] https://travis-ci.org/apiri/incubator-nifi/builds/90353191
>>>>>>> [3] https://s3.amazonaws.com/archive.travis-ci.org/jobs/90353192/log.txt
>>>>>>> [4] https://issues.apache.org/jira/browse/NIFI-1145
>>>>>>>
>>>>>>> On Thu, Nov 5, 2015 at 5:17 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> I built a new VM CentOS7
>>>>>>>>
>>>>>>>> I get the below most of the time though last night it did succeeded.
>>>>>>>>
>>>>>>>> [INFO] nifi-framework-core ................................ FAILURE
>>>>>> [02:41
>>>>>>>> min]
>>>>>>>>
>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>> [INFO]
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>> [INFO] Total time: 08:51 min (Wall Clock)
>>>>>>>> [INFO] Finished at: 2015-11-05T16:09:51-06:00
>>>>>>>> [INFO] Final Memory: 183M/514M
>>>>>>>> [INFO]
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test)
>>>>>> on
>>>>>>>> project nifi-framework-core: There are test failures.
>>>>>>>> [ERROR]
>>>>>>>> [ERROR] Please refer to
>>>>>>>>
>>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>> for the individual test results.
>>>>>>>> [ERROR] -> [Help 1]
>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>>>> execute
>>>>>>>> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>>>>>> (default-test) on project nifi-framework-core: There are test failures.
>>>>>>>>
>>>>>>>> Please refer to
>>>>>>>>
>>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>> for the individual test results.
>>>>>>>> at
>>>>>>>>
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>> at
>>>>>>>>
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>> at
>>>>>>>>
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>> at
>>>>>>>>
>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>> at
>>>>>>>>
>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>> at
>>>>>>>>
>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>> 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:1142)
>>>>>>>> at
>>>>>>>>
>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
>>>>>>>> failures.
>>>>>>>>
>>>>>>>> Please refer to
>>>>>>>>
>>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>> for the individual test results.
>>>>>>>> at
>>>>>>>>
>>>>>> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
>>>>>>>> at
>>>>>>>>
>>>>>> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
>>>>>>>> at
>>>>>>>>
>>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
>>>>>>>> at
>>>>>>>>
>>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>>>>>>>> at
>>>>>>>>
>>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>> at
>>>>>>>>
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>> ... 11 more
>>>>>>>> [ERROR]
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Nov 4, 2015, at 9:01 AM, Mark Payne <ma...@hotmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Jeff,
>>>>>>>>>
>>>>>>>>> I just checked out a fresh build from master, running on CentOS 7 and
>>>>>>>> was able to build without any problems.
>>>>>>>>> So I don't think it is specifically a problem with CentOS 7. Can you
>>>>>>>> provide the output of the unit tests?
>>>>>>>>>
>>>>>>>>> They should be in
>>>>>>>>
>>>>>> ${NIFI_SRC_DIR}/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>>
>>>>>>>>> The two files of interest are
>>>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue.txt and
>>>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue-output.txt
>>>>>>>>>
>>>>>>>>> Thanks!
>>>>>>>>> -Mark
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On Nov 4, 2015, at 8:53 AM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.916
>>>>>>>> sec <<< FAILURE! - in
>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue
>>>>>>>>>>
>>>>>>>>
>>>>>> testDropSwappedFlowFiles(org.apache.nifi.controller.TestStandardFlowFileQueue)
>>>>>>>> Time elapsed: 21.825 sec <<< ERROR!
>>>>>>>>>> org.junit.runners.model.TestTimedOutException: test timed out after
>>>>>>>> 20000 milliseconds
>>>>>>>>>> at java.lang.Throwable.fillInStackTrace(Native Method)
>>>>>>>>>> at java.lang.Throwable.fillInStackTrace(Throwable.java:783)
>>>>>>>>>> at java.lang.Throwable.<init>(Throwable.java:250)
>>>>>>>>>> at
>>>>>>>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:24)
>>>>>>>>>> at
>>>>>>>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:19)
>>>>>>>>>> at
>>>>>>>>
>>>>>> org.mockito.internal.invocation.InvocationImpl.<init>(InvocationImpl.java:50)
>>>>>>>>>> at
>>>>>>>>
>>>>>> org.mockito.internal.creation.cglib.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:58)
>>>>>>>>>> at
>>>>>>>>
>>>>>> org.apache.nifi.connectable.Connection$$EnhancerByMockitoWithCGLIB$$8aa704ad.getDestination(<generated>)
>>>>>>>>>> at
>>>>>>>>
>>>>>> org.apache.nifi.controller.StandardFlowFileQueue.put(StandardFlowFileQueue.java:315)
>>>>>>>>>> at
>>>>>>>>
>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue.testDropSwappedFlowFiles(TestStandardFlowFileQueue.java:169)
>>>>>>>>>>
>>>>>>>>>>> On Nov 4, 2015, at 7:51 AM, Brandon DeVries <br...@jhu.edu> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Jeff,
>>>>>>>>>>>
>>>>>>>>>>> Can you see what tests had failures? Also, if you just want to
>>>>>> verify
>>>>>>>> that
>>>>>>>>>>> your system can do the build, you could do something like "mvn clean
>>>>>>>>>>> install -DskipTests". Let us know what you see. Thanks.
>>>>>>>>>>>
>>>>>>>>>>> Brandon
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Nov 4, 2015 at 8:46 AM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Well, the build got much further with the Oracle JDK but still
>>>>>> failed;
>>>>>>>>>>>>
>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>> [INFO] Total time: 07:47 min (Wall Clock)
>>>>>>>>>>>> [INFO] Finished at: 2015-11-03T17:07:40-06:00
>>>>>>>>>>>> [INFO] Final Memory: 183M/564M
>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>>>>>> (default-test) on
>>>>>>>>>>>> project nifi-framework-core: There are test failures.
>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>> [ERROR] Please refer to
>>>>>>>>>>>>
>>>>>>>>
>>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>>>>> for the individual test results.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> On Nov 3, 2015, at 6:54 PM, Cerulean Blue <j....@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Oh, I also adjusted the memory!
>>>>>>>>>>>>>
>>>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Nov 3, 2015, at 6:50 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Jeff - can you please send another note telling Tony that it turns
>>>>>>>> out
>>>>>>>>>>>>>> it was memory settings :-)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> He is making fun of me off-list. He should totally do that
>>>>>> on-list!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Glad you're in business now and sorry for my terrible
>>>>>> misdirection.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>>>>>>> Huzzah
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com>
>>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I removed openjdk and installed the Oracle jdk and it now works.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks for the help!!
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com>
>>>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> it is entirely possible that you only have the jre installed.
>>>>>>>> 'yum
>>>>>>>>>>>>>>>>> whatprovides "*/bin/javac"' may tell you packages which you can
>>>>>>>>>>>> install
>>>>>>>>>>>>>>>>> which include a compiler.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> find / -name javac did not return anything
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I had JAVA_HOME set to
>>>>>>>>>>>>>>>>>>
>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Jeff,
>>>>>>>>>>>>>>>>>>> Were you able to run that find command?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>> [INFO] Total time: 8.091 s
>>>>>>>>>>>>>>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
>>>>>>>>>>>>>>>>>>>> [INFO] Final Memory: 76M/365M
>>>>>>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>> ->
>>>>>>>>>>>> [Help 1]
>>>>>>>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run
>>>>>>>> Maven
>>>>>>>>>>>> with
>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>> -e switch.
>>>>>>>>>>>>>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full
>>>>>> debug
>>>>>>>>>>>> logging.
>>>>>>>>>>>>>>>>>>>> [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/MojoFailureException
>>>>>>>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>>>>>>>> [ERROR] After correcting the problems, you can resume the
>>>>>>>> build
>>>>>>>>>>>> with
>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>> [ERROR] mvn <goals> -rf :nifi-api
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Can you go ahead and try just plain ol'
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I am curious if there is a memory/settings issue that is
>>>>>>>>>>>> manifesting
>>>>>>>>>>>>>>>>>>>>> as an exception during compilation but that it isn't
>>>>>>>> actually a
>>>>>>>>>>>>>>>>>>>>> compilation problem at all...
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j.007ba7@gmail.com
>>>>>>>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>> The only other message I see is
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac'
>>>>>>>> from
>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>> environment.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> No worries, it can wait.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <joe.witt@gmail.com
>>>>>>>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to
>>>>>>>> pull
>>>>>>>>>>>> down
>>>>>>>>>>>>>>>>>>>>>>> centos. Is there anymore that can be found with those
>>>>>>>> stack
>>>>>>>>>>>>>>>> traces .
>>>>>>>>>>>>>>>>>>>>>>> They're not saying much. Your java and maven versions
>>>>>> seem
>>>>>>>>>>>> quite
>>>>>>>>>>>>>>>>>> good
>>>>>>>>>>>>>>>>>>>>>>> so need to dig further.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <
>>>>>> j.007ba7@gmail.com
>>>>>>>>>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> [root@localhost nifi]# java -version
>>>>>>>>>>>>>>>>>>>>>>>> openjdk version "1.8.0_65"
>>>>>>>>>>>>>>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>>>>>>>>>>>>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> [root@localhost nifi]# mvn -version
>>>>>>>>>>>>>>>>>>>>>>>> which: no javac in
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>
>>>>>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>>>>>>>>>>>>>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set.
>>>>>>>>>>>>>>>>>>>>>>>> Apache Maven 3.3.3
>>>>>>>> (7994120775791599e205a5524ec3e0dfe41d4a06;
>>>>>>>>>>>>>>>>>>>> 2015-04-22T06:57:37-05:00)
>>>>>>>>>>>>>>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3
>>>>>>>>>>>>>>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>>>>>>>>>>>>>>>>>>>>>>> Java home:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>>>>>>>>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64",
>>>>>>>> arch:
>>>>>>>>>>>>>>>>>>>> "amd64", family: "unix"
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <
>>>>>> joe.witt@gmail.com
>>>>>>>>>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do
>>>>>>>> you
>>>>>>>>>>>> get
>>>>>>>>>>>>>>>>>> back?
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <
>>>>>>>> j.007ba7@gmail.com>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>> I’m getting the below on a VM. It does build
>>>>>>>> successfully
>>>>>>>>>>>> on my
>>>>>>>>>>>>>>>>>>>> Mac, though.
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install
>>>>>>>>>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>> ->
>>>>>>>>>>>> [Help 1]
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException:
>>>>>>>>>>>> Failed
>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>> execute goal
>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>
>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>
>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>
>>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>>>>>>>>>>>>>>>>>>> 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:1142)
>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>
>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>>>>>>>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>>>>>>>>>>>>>>>>>>> Caused by:
>>>>>>>>>>>>>>>>>>>>
>>>>>> org.apache.maven.plugin.compiler.CompilationFailureException:
>>>>>>>>>>>>>>>>>> Compilation
>>>>>>>>>>>>>>>>>>>> failure
>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>
>>>>>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>
>>>>>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>
>>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>>>>>>>>>>>>>>>>>>> ... 11 more
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>
>>
Re: nifi fails build on CentOS 7
Posted by Joe Witt <jo...@gmail.com>.
jeff - out of curiosity can you confirm you're running as root on that
VM when you build?
On Mon, Dec 7, 2015 at 4:42 PM, Jeff <j....@gmail.com> wrote:
> Hi Joe,
>
> You are welcome. Below is what I’m seeing
>
> -------------------------------------------------------------------------------
> Test set: org.apache.nifi.processors.hadoop.PutHDFSTest
> -------------------------------------------------------------------------------
> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.949 sec <<< FAILURE! - in org.apache.nifi.processors.hadoop.PutHDFSTest
> testPutFileWithException(org.apache.nifi.processors.hadoop.PutHDFSTest) Time elapsed: 0.532 sec <<< FAILURE!
> java.lang.AssertionError: null
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at org.junit.Assert.assertFalse(Assert.java:74)
> at org.apache.nifi.processors.hadoop.PutHDFSTest.testPutFileWithException(PutHDFSTest.java:230)
>
>> On Dec 7, 2015, at 3:36 PM, Joe Witt <jo...@gmail.com> wrote:
>>
>> thanks for reporting this Jeff and your timing could not have been better!
>>
>> It's happening for Gilman as well.
>>
>> Joe
>>
>> On Mon, Dec 7, 2015 at 4:31 PM, Jeff <j....@gmail.com> wrote:
>>> Yes, CentOS 7
>>>
>>> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.703 sec - in org.apache.nifi.processors.hadoop.TestListHDFS
>>>
>>> Results :
>>>
>>> Failed tests:
>>> PutHDFSTest.testPutFileWithException:230 null
>>>
>>>
>>>
>>> Tests run: 21, Failures: 1, Errors: 0, Skipped: 0
>>>
>>>
>>>
>>>> On Dec 7, 2015, at 3:28 PM, Matt Gilman <ma...@gmail.com> wrote:
>>>>
>>>> Jeff,
>>>>
>>>> Are you still running on CentOS 7? Can you provide more details about the
>>>> unit test is failing? Thanks!
>>>>
>>>> Matt
>>>>
>>>> On Mon, Dec 7, 2015 at 4:24 PM, Jeff <j....@gmail.com> wrote:
>>>>
>>>>> I just cloned Nifi but I’m still seeing these errors when I do mvn -e -X
>>>>> -T 2.0C clean install
>>>>>
>>>>> [ERROR] Failed to execute goal
>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
>>>>> project nifi-hdfs-processors: There are test failures.
>>>>> [ERROR]
>>>>> [ERROR] Please refer to
>>>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>>>> for the individual test results.
>>>>> [ERROR] -> [Help 1]
>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>>>>> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>>> (default-test) on project nifi-hdfs-processors: There are test failures.
>>>>>
>>>>> Please refer to
>>>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>>>> for the individual test results.
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>> 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:1142)
>>>>> at
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
>>>>> failures.
>>>>>
>>>>> Please refer to
>>>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>>>> for the individual test results.
>>>>> at
>>>>> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
>>>>> at
>>>>> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
>>>>> at
>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
>>>>> at
>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>>>>> at
>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>> ... 11 more
>>>>> [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/MojoFailureException
>>>>> [ERROR]
>>>>> [ERROR] After correcting the problems, you can resume the build with the
>>>>> command
>>>>> [ERROR] mvn <goals> -rf :nifi-hdfs-processors
>>>>>
>>>>>
>>>>>
>>>>>> On Nov 10, 2015, at 12:33 PM, Aldrin Piri <al...@gmail.com> wrote:
>>>>>>
>>>>>> Seems there is in fact an issue with the test cited prior. I received
>>>>> the
>>>>>> following on my Travis CI build on a branch which has the latest of
>>>>> master
>>>>>> merged into it. Unfortunately, it seems that the environment is not the
>>>>>> same as before.
>>>>>>
>>>>>> In this case, Travis CI is running with Ubuntu 12.04 LTS [1]. For the
>>>>>> particular build [2], Oracle JDK 7 built without issue, but Oracle JDK 8
>>>>>> exhibited the same problem [3] as reported by Jeff.
>>>>>>
>>>>>> NIFI-1145 was created to track this issue [4]
>>>>>>
>>>>>> [1]
>>>>>>
>>>>> http://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
>>>>>> [2] https://travis-ci.org/apiri/incubator-nifi/builds/90353191
>>>>>> [3] https://s3.amazonaws.com/archive.travis-ci.org/jobs/90353192/log.txt
>>>>>> [4] https://issues.apache.org/jira/browse/NIFI-1145
>>>>>>
>>>>>> On Thu, Nov 5, 2015 at 5:17 PM, Jeff <j....@gmail.com> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I built a new VM CentOS7
>>>>>>>
>>>>>>> I get the below most of the time though last night it did succeeded.
>>>>>>>
>>>>>>> [INFO] nifi-framework-core ................................ FAILURE
>>>>> [02:41
>>>>>>> min]
>>>>>>>
>>>>>>> [INFO] BUILD FAILURE
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>> [INFO] Total time: 08:51 min (Wall Clock)
>>>>>>> [INFO] Finished at: 2015-11-05T16:09:51-06:00
>>>>>>> [INFO] Final Memory: 183M/514M
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>> [ERROR] Failed to execute goal
>>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test)
>>>>> on
>>>>>>> project nifi-framework-core: There are test failures.
>>>>>>> [ERROR]
>>>>>>> [ERROR] Please refer to
>>>>>>>
>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>> for the individual test results.
>>>>>>> [ERROR] -> [Help 1]
>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>>> execute
>>>>>>> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>>>>> (default-test) on project nifi-framework-core: There are test failures.
>>>>>>>
>>>>>>> Please refer to
>>>>>>>
>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>> for the individual test results.
>>>>>>> at
>>>>>>>
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>> at
>>>>>>>
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>> at
>>>>>>>
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>> at
>>>>>>>
>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>> at
>>>>>>>
>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>> at
>>>>>>>
>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>> 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:1142)
>>>>>>> at
>>>>>>>
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
>>>>>>> failures.
>>>>>>>
>>>>>>> Please refer to
>>>>>>>
>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>> for the individual test results.
>>>>>>> at
>>>>>>>
>>>>> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
>>>>>>> at
>>>>>>>
>>>>> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
>>>>>>> at
>>>>>>>
>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
>>>>>>> at
>>>>>>>
>>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>>>>>>> at
>>>>>>>
>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>> at
>>>>>>>
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>> ... 11 more
>>>>>>> [ERROR]
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> On Nov 4, 2015, at 9:01 AM, Mark Payne <ma...@hotmail.com> wrote:
>>>>>>>>
>>>>>>>> Jeff,
>>>>>>>>
>>>>>>>> I just checked out a fresh build from master, running on CentOS 7 and
>>>>>>> was able to build without any problems.
>>>>>>>> So I don't think it is specifically a problem with CentOS 7. Can you
>>>>>>> provide the output of the unit tests?
>>>>>>>>
>>>>>>>> They should be in
>>>>>>>
>>>>> ${NIFI_SRC_DIR}/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>
>>>>>>>> The two files of interest are
>>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue.txt and
>>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue-output.txt
>>>>>>>>
>>>>>>>> Thanks!
>>>>>>>> -Mark
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Nov 4, 2015, at 8:53 AM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.916
>>>>>>> sec <<< FAILURE! - in
>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue
>>>>>>>>>
>>>>>>>
>>>>> testDropSwappedFlowFiles(org.apache.nifi.controller.TestStandardFlowFileQueue)
>>>>>>> Time elapsed: 21.825 sec <<< ERROR!
>>>>>>>>> org.junit.runners.model.TestTimedOutException: test timed out after
>>>>>>> 20000 milliseconds
>>>>>>>>> at java.lang.Throwable.fillInStackTrace(Native Method)
>>>>>>>>> at java.lang.Throwable.fillInStackTrace(Throwable.java:783)
>>>>>>>>> at java.lang.Throwable.<init>(Throwable.java:250)
>>>>>>>>> at
>>>>>>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:24)
>>>>>>>>> at
>>>>>>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:19)
>>>>>>>>> at
>>>>>>>
>>>>> org.mockito.internal.invocation.InvocationImpl.<init>(InvocationImpl.java:50)
>>>>>>>>> at
>>>>>>>
>>>>> org.mockito.internal.creation.cglib.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:58)
>>>>>>>>> at
>>>>>>>
>>>>> org.apache.nifi.connectable.Connection$$EnhancerByMockitoWithCGLIB$$8aa704ad.getDestination(<generated>)
>>>>>>>>> at
>>>>>>>
>>>>> org.apache.nifi.controller.StandardFlowFileQueue.put(StandardFlowFileQueue.java:315)
>>>>>>>>> at
>>>>>>>
>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue.testDropSwappedFlowFiles(TestStandardFlowFileQueue.java:169)
>>>>>>>>>
>>>>>>>>>> On Nov 4, 2015, at 7:51 AM, Brandon DeVries <br...@jhu.edu> wrote:
>>>>>>>>>>
>>>>>>>>>> Jeff,
>>>>>>>>>>
>>>>>>>>>> Can you see what tests had failures? Also, if you just want to
>>>>> verify
>>>>>>> that
>>>>>>>>>> your system can do the build, you could do something like "mvn clean
>>>>>>>>>> install -DskipTests". Let us know what you see. Thanks.
>>>>>>>>>>
>>>>>>>>>> Brandon
>>>>>>>>>>
>>>>>>>>>> On Wed, Nov 4, 2015 at 8:46 AM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Well, the build got much further with the Oracle JDK but still
>>>>> failed;
>>>>>>>>>>>
>>>>>>>>>>> [INFO]
>>>>>>>>>>>
>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>> [INFO]
>>>>>>>>>>>
>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>> [INFO] Total time: 07:47 min (Wall Clock)
>>>>>>>>>>> [INFO] Finished at: 2015-11-03T17:07:40-06:00
>>>>>>>>>>> [INFO] Final Memory: 183M/564M
>>>>>>>>>>> [INFO]
>>>>>>>>>>>
>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>>>>> (default-test) on
>>>>>>>>>>> project nifi-framework-core: There are test failures.
>>>>>>>>>>> [ERROR]
>>>>>>>>>>> [ERROR] Please refer to
>>>>>>>>>>>
>>>>>>>
>>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>>>> for the individual test results.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On Nov 3, 2015, at 6:54 PM, Cerulean Blue <j....@gmail.com>
>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Oh, I also adjusted the memory!
>>>>>>>>>>>>
>>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>>
>>>>>>>>>>>>> On Nov 3, 2015, at 6:50 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Jeff - can you please send another note telling Tony that it turns
>>>>>>> out
>>>>>>>>>>>>> it was memory settings :-)
>>>>>>>>>>>>>
>>>>>>>>>>>>> He is making fun of me off-list. He should totally do that
>>>>> on-list!
>>>>>>>>>>>>>
>>>>>>>>>>>>> Glad you're in business now and sorry for my terrible
>>>>> misdirection.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com>
>>>>>>> wrote:
>>>>>>>>>>>>>> Huzzah
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com>
>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I removed openjdk and installed the Oracle jdk and it now works.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks for the help!!
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com>
>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> it is entirely possible that you only have the jre installed.
>>>>>>> 'yum
>>>>>>>>>>>>>>>> whatprovides "*/bin/javac"' may tell you packages which you can
>>>>>>>>>>> install
>>>>>>>>>>>>>>>> which include a compiler.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com>
>>>>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> find / -name javac did not return anything
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I had JAVA_HOME set to
>>>>>>>>>>>>>>>>>
>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com>
>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Jeff,
>>>>>>>>>>>>>>>>>> Were you able to run that find command?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com>
>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>> [INFO] Total time: 8.091 s
>>>>>>>>>>>>>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
>>>>>>>>>>>>>>>>>>> [INFO] Final Memory: 76M/365M
>>>>>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>> ->
>>>>>>>>>>> [Help 1]
>>>>>>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run
>>>>>>> Maven
>>>>>>>>>>> with
>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>> -e switch.
>>>>>>>>>>>>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full
>>>>> debug
>>>>>>>>>>> logging.
>>>>>>>>>>>>>>>>>>> [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/MojoFailureException
>>>>>>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>>>>>>> [ERROR] After correcting the problems, you can resume the
>>>>>>> build
>>>>>>>>>>> with
>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>> [ERROR] mvn <goals> -rf :nifi-api
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com>
>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Can you go ahead and try just plain ol'
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I am curious if there is a memory/settings issue that is
>>>>>>>>>>> manifesting
>>>>>>>>>>>>>>>>>>>> as an exception during compilation but that it isn't
>>>>>>> actually a
>>>>>>>>>>>>>>>>>>>> compilation problem at all...
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j.007ba7@gmail.com
>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>> The only other message I see is
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac'
>>>>>>> from
>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>> environment.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> No worries, it can wait.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <joe.witt@gmail.com
>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to
>>>>>>> pull
>>>>>>>>>>> down
>>>>>>>>>>>>>>>>>>>>>> centos. Is there anymore that can be found with those
>>>>>>> stack
>>>>>>>>>>>>>>> traces .
>>>>>>>>>>>>>>>>>>>>>> They're not saying much. Your java and maven versions
>>>>> seem
>>>>>>>>>>> quite
>>>>>>>>>>>>>>>>> good
>>>>>>>>>>>>>>>>>>>>>> so need to dig further.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <
>>>>> j.007ba7@gmail.com
>>>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> [root@localhost nifi]# java -version
>>>>>>>>>>>>>>>>>>>>>>> openjdk version "1.8.0_65"
>>>>>>>>>>>>>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>>>>>>>>>>>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> [root@localhost nifi]# mvn -version
>>>>>>>>>>>>>>>>>>>>>>> which: no javac in
>>>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>>>>>>>>>>>>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set.
>>>>>>>>>>>>>>>>>>>>>>> Apache Maven 3.3.3
>>>>>>> (7994120775791599e205a5524ec3e0dfe41d4a06;
>>>>>>>>>>>>>>>>>>> 2015-04-22T06:57:37-05:00)
>>>>>>>>>>>>>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3
>>>>>>>>>>>>>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>>>>>>>>>>>>>>>>>>>>>> Java home:
>>>>>>>>>>>>>>>>>>>
>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>>>>>>>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64",
>>>>>>> arch:
>>>>>>>>>>>>>>>>>>> "amd64", family: "unix"
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <
>>>>> joe.witt@gmail.com
>>>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do
>>>>>>> you
>>>>>>>>>>> get
>>>>>>>>>>>>>>>>> back?
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <
>>>>>>> j.007ba7@gmail.com>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>> I’m getting the below on a VM. It does build
>>>>>>> successfully
>>>>>>>>>>> on my
>>>>>>>>>>>>>>>>>>> Mac, though.
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install
>>>>>>>>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>> ->
>>>>>>>>>>> [Help 1]
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>> org.apache.maven.lifecycle.LifecycleExecutionException:
>>>>>>>>>>> Failed
>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>> execute goal
>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>>>>>>>>>>>>>>>>>> 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:1142)
>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>>>>>>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>>>>>>>>>>>>>>>>>> Caused by:
>>>>>>>>>>>>>>>>>>>
>>>>> org.apache.maven.plugin.compiler.CompilationFailureException:
>>>>>>>>>>>>>>>>> Compilation
>>>>>>>>>>>>>>>>>>> failure
>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>>>>>>>>>>>>>>>>>> ... 11 more
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>
>
Re: nifi fails build on CentOS 7
Posted by Jeff <j....@gmail.com>.
Hi Joe,
You are welcome. Below is what I’m seeing
-------------------------------------------------------------------------------
Test set: org.apache.nifi.processors.hadoop.PutHDFSTest
-------------------------------------------------------------------------------
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.949 sec <<< FAILURE! - in org.apache.nifi.processors.hadoop.PutHDFSTest
testPutFileWithException(org.apache.nifi.processors.hadoop.PutHDFSTest) Time elapsed: 0.532 sec <<< FAILURE!
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertFalse(Assert.java:64)
at org.junit.Assert.assertFalse(Assert.java:74)
at org.apache.nifi.processors.hadoop.PutHDFSTest.testPutFileWithException(PutHDFSTest.java:230)
> On Dec 7, 2015, at 3:36 PM, Joe Witt <jo...@gmail.com> wrote:
>
> thanks for reporting this Jeff and your timing could not have been better!
>
> It's happening for Gilman as well.
>
> Joe
>
> On Mon, Dec 7, 2015 at 4:31 PM, Jeff <j....@gmail.com> wrote:
>> Yes, CentOS 7
>>
>> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.703 sec - in org.apache.nifi.processors.hadoop.TestListHDFS
>>
>> Results :
>>
>> Failed tests:
>> PutHDFSTest.testPutFileWithException:230 null
>>
>>
>>
>> Tests run: 21, Failures: 1, Errors: 0, Skipped: 0
>>
>>
>>
>>> On Dec 7, 2015, at 3:28 PM, Matt Gilman <ma...@gmail.com> wrote:
>>>
>>> Jeff,
>>>
>>> Are you still running on CentOS 7? Can you provide more details about the
>>> unit test is failing? Thanks!
>>>
>>> Matt
>>>
>>> On Mon, Dec 7, 2015 at 4:24 PM, Jeff <j....@gmail.com> wrote:
>>>
>>>> I just cloned Nifi but I’m still seeing these errors when I do mvn -e -X
>>>> -T 2.0C clean install
>>>>
>>>> [ERROR] Failed to execute goal
>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
>>>> project nifi-hdfs-processors: There are test failures.
>>>> [ERROR]
>>>> [ERROR] Please refer to
>>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>>> for the individual test results.
>>>> [ERROR] -> [Help 1]
>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>>>> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>> (default-test) on project nifi-hdfs-processors: There are test failures.
>>>>
>>>> Please refer to
>>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>>> for the individual test results.
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>> at
>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>> at
>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>> 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:1142)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>> at java.lang.Thread.run(Thread.java:745)
>>>> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
>>>> failures.
>>>>
>>>> Please refer to
>>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>>> for the individual test results.
>>>> at
>>>> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
>>>> at
>>>> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
>>>> at
>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
>>>> at
>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>>>> at
>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>> ... 11 more
>>>> [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/MojoFailureException
>>>> [ERROR]
>>>> [ERROR] After correcting the problems, you can resume the build with the
>>>> command
>>>> [ERROR] mvn <goals> -rf :nifi-hdfs-processors
>>>>
>>>>
>>>>
>>>>> On Nov 10, 2015, at 12:33 PM, Aldrin Piri <al...@gmail.com> wrote:
>>>>>
>>>>> Seems there is in fact an issue with the test cited prior. I received
>>>> the
>>>>> following on my Travis CI build on a branch which has the latest of
>>>> master
>>>>> merged into it. Unfortunately, it seems that the environment is not the
>>>>> same as before.
>>>>>
>>>>> In this case, Travis CI is running with Ubuntu 12.04 LTS [1]. For the
>>>>> particular build [2], Oracle JDK 7 built without issue, but Oracle JDK 8
>>>>> exhibited the same problem [3] as reported by Jeff.
>>>>>
>>>>> NIFI-1145 was created to track this issue [4]
>>>>>
>>>>> [1]
>>>>>
>>>> http://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
>>>>> [2] https://travis-ci.org/apiri/incubator-nifi/builds/90353191
>>>>> [3] https://s3.amazonaws.com/archive.travis-ci.org/jobs/90353192/log.txt
>>>>> [4] https://issues.apache.org/jira/browse/NIFI-1145
>>>>>
>>>>> On Thu, Nov 5, 2015 at 5:17 PM, Jeff <j....@gmail.com> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> I built a new VM CentOS7
>>>>>>
>>>>>> I get the below most of the time though last night it did succeeded.
>>>>>>
>>>>>> [INFO] nifi-framework-core ................................ FAILURE
>>>> [02:41
>>>>>> min]
>>>>>>
>>>>>> [INFO] BUILD FAILURE
>>>>>> [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>> [INFO] Total time: 08:51 min (Wall Clock)
>>>>>> [INFO] Finished at: 2015-11-05T16:09:51-06:00
>>>>>> [INFO] Final Memory: 183M/514M
>>>>>> [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>> [ERROR] Failed to execute goal
>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test)
>>>> on
>>>>>> project nifi-framework-core: There are test failures.
>>>>>> [ERROR]
>>>>>> [ERROR] Please refer to
>>>>>>
>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>> for the individual test results.
>>>>>> [ERROR] -> [Help 1]
>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>> execute
>>>>>> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>>>> (default-test) on project nifi-framework-core: There are test failures.
>>>>>>
>>>>>> Please refer to
>>>>>>
>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>> for the individual test results.
>>>>>> at
>>>>>>
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>> at
>>>>>>
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>> at
>>>>>>
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>> at
>>>>>>
>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>> at
>>>>>>
>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>> at
>>>>>>
>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>> 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:1142)
>>>>>> at
>>>>>>
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
>>>>>> failures.
>>>>>>
>>>>>> Please refer to
>>>>>>
>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>> for the individual test results.
>>>>>> at
>>>>>>
>>>> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
>>>>>> at
>>>>>>
>>>> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
>>>>>> at
>>>>>>
>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
>>>>>> at
>>>>>>
>>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>>>>>> at
>>>>>>
>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>> at
>>>>>>
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>> ... 11 more
>>>>>> [ERROR]
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On Nov 4, 2015, at 9:01 AM, Mark Payne <ma...@hotmail.com> wrote:
>>>>>>>
>>>>>>> Jeff,
>>>>>>>
>>>>>>> I just checked out a fresh build from master, running on CentOS 7 and
>>>>>> was able to build without any problems.
>>>>>>> So I don't think it is specifically a problem with CentOS 7. Can you
>>>>>> provide the output of the unit tests?
>>>>>>>
>>>>>>> They should be in
>>>>>>
>>>> ${NIFI_SRC_DIR}/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>
>>>>>>> The two files of interest are
>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue.txt and
>>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue-output.txt
>>>>>>>
>>>>>>> Thanks!
>>>>>>> -Mark
>>>>>>>
>>>>>>>
>>>>>>>> On Nov 4, 2015, at 8:53 AM, Jeff <j....@gmail.com> wrote:
>>>>>>>>
>>>>>>>> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.916
>>>>>> sec <<< FAILURE! - in
>>>> org.apache.nifi.controller.TestStandardFlowFileQueue
>>>>>>>>
>>>>>>
>>>> testDropSwappedFlowFiles(org.apache.nifi.controller.TestStandardFlowFileQueue)
>>>>>> Time elapsed: 21.825 sec <<< ERROR!
>>>>>>>> org.junit.runners.model.TestTimedOutException: test timed out after
>>>>>> 20000 milliseconds
>>>>>>>> at java.lang.Throwable.fillInStackTrace(Native Method)
>>>>>>>> at java.lang.Throwable.fillInStackTrace(Throwable.java:783)
>>>>>>>> at java.lang.Throwable.<init>(Throwable.java:250)
>>>>>>>> at
>>>>>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:24)
>>>>>>>> at
>>>>>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:19)
>>>>>>>> at
>>>>>>
>>>> org.mockito.internal.invocation.InvocationImpl.<init>(InvocationImpl.java:50)
>>>>>>>> at
>>>>>>
>>>> org.mockito.internal.creation.cglib.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:58)
>>>>>>>> at
>>>>>>
>>>> org.apache.nifi.connectable.Connection$$EnhancerByMockitoWithCGLIB$$8aa704ad.getDestination(<generated>)
>>>>>>>> at
>>>>>>
>>>> org.apache.nifi.controller.StandardFlowFileQueue.put(StandardFlowFileQueue.java:315)
>>>>>>>> at
>>>>>>
>>>> org.apache.nifi.controller.TestStandardFlowFileQueue.testDropSwappedFlowFiles(TestStandardFlowFileQueue.java:169)
>>>>>>>>
>>>>>>>>> On Nov 4, 2015, at 7:51 AM, Brandon DeVries <br...@jhu.edu> wrote:
>>>>>>>>>
>>>>>>>>> Jeff,
>>>>>>>>>
>>>>>>>>> Can you see what tests had failures? Also, if you just want to
>>>> verify
>>>>>> that
>>>>>>>>> your system can do the build, you could do something like "mvn clean
>>>>>>>>> install -DskipTests". Let us know what you see. Thanks.
>>>>>>>>>
>>>>>>>>> Brandon
>>>>>>>>>
>>>>>>>>> On Wed, Nov 4, 2015 at 8:46 AM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Well, the build got much further with the Oracle JDK but still
>>>> failed;
>>>>>>>>>>
>>>>>>>>>> [INFO]
>>>>>>>>>>
>>>>>> ------------------------------------------------------------------------
>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>> [INFO]
>>>>>>>>>>
>>>>>> ------------------------------------------------------------------------
>>>>>>>>>> [INFO] Total time: 07:47 min (Wall Clock)
>>>>>>>>>> [INFO] Finished at: 2015-11-03T17:07:40-06:00
>>>>>>>>>> [INFO] Final Memory: 183M/564M
>>>>>>>>>> [INFO]
>>>>>>>>>>
>>>>>> ------------------------------------------------------------------------
>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>>>> (default-test) on
>>>>>>>>>> project nifi-framework-core: There are test failures.
>>>>>>>>>> [ERROR]
>>>>>>>>>> [ERROR] Please refer to
>>>>>>>>>>
>>>>>>
>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>>> for the individual test results.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> On Nov 3, 2015, at 6:54 PM, Cerulean Blue <j....@gmail.com>
>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Oh, I also adjusted the memory!
>>>>>>>>>>>
>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>
>>>>>>>>>>>> On Nov 3, 2015, at 6:50 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Jeff - can you please send another note telling Tony that it turns
>>>>>> out
>>>>>>>>>>>> it was memory settings :-)
>>>>>>>>>>>>
>>>>>>>>>>>> He is making fun of me off-list. He should totally do that
>>>> on-list!
>>>>>>>>>>>>
>>>>>>>>>>>> Glad you're in business now and sorry for my terrible
>>>> misdirection.
>>>>>>>>>>>>
>>>>>>>>>>>> Joe
>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com>
>>>>>> wrote:
>>>>>>>>>>>>> Huzzah
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com>
>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I removed openjdk and installed the Oracle jdk and it now works.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks for the help!!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com>
>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> it is entirely possible that you only have the jre installed.
>>>>>> 'yum
>>>>>>>>>>>>>>> whatprovides "*/bin/javac"' may tell you packages which you can
>>>>>>>>>> install
>>>>>>>>>>>>>>> which include a compiler.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com>
>>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> find / -name javac did not return anything
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I had JAVA_HOME set to
>>>>>>>>>>>>>>>>
>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com>
>>>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Jeff,
>>>>>>>>>>>>>>>>> Were you able to run that find command?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com>
>>>>>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>> [INFO] Total time: 8.091 s
>>>>>>>>>>>>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
>>>>>>>>>>>>>>>>>> [INFO] Final Memory: 76M/365M
>>>>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>> ->
>>>>>>>>>> [Help 1]
>>>>>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run
>>>>>> Maven
>>>>>>>>>> with
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>> -e switch.
>>>>>>>>>>>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full
>>>> debug
>>>>>>>>>> logging.
>>>>>>>>>>>>>>>>>> [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/MojoFailureException
>>>>>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>>>>>> [ERROR] After correcting the problems, you can resume the
>>>>>> build
>>>>>>>>>> with
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>> [ERROR] mvn <goals> -rf :nifi-api
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com>
>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Can you go ahead and try just plain ol'
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I am curious if there is a memory/settings issue that is
>>>>>>>>>> manifesting
>>>>>>>>>>>>>>>>>>> as an exception during compilation but that it isn't
>>>>>> actually a
>>>>>>>>>>>>>>>>>>> compilation problem at all...
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j.007ba7@gmail.com
>>>>>
>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>> The only other message I see is
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac'
>>>>>> from
>>>>>>>>>> the
>>>>>>>>>>>>>>>>>> environment.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> No worries, it can wait.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <joe.witt@gmail.com
>>>>>
>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to
>>>>>> pull
>>>>>>>>>> down
>>>>>>>>>>>>>>>>>>>>> centos. Is there anymore that can be found with those
>>>>>> stack
>>>>>>>>>>>>>> traces .
>>>>>>>>>>>>>>>>>>>>> They're not saying much. Your java and maven versions
>>>> seem
>>>>>>>>>> quite
>>>>>>>>>>>>>>>> good
>>>>>>>>>>>>>>>>>>>>> so need to dig further.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <
>>>> j.007ba7@gmail.com
>>>>>>>
>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> [root@localhost nifi]# java -version
>>>>>>>>>>>>>>>>>>>>>> openjdk version "1.8.0_65"
>>>>>>>>>>>>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>>>>>>>>>>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> [root@localhost nifi]# mvn -version
>>>>>>>>>>>>>>>>>>>>>> which: no javac in
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>>>>>>>>>>>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set.
>>>>>>>>>>>>>>>>>>>>>> Apache Maven 3.3.3
>>>>>> (7994120775791599e205a5524ec3e0dfe41d4a06;
>>>>>>>>>>>>>>>>>> 2015-04-22T06:57:37-05:00)
>>>>>>>>>>>>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3
>>>>>>>>>>>>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>>>>>>>>>>>>>>>>>>>>> Java home:
>>>>>>>>>>>>>>>>>>
>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>>>>>>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64",
>>>>>> arch:
>>>>>>>>>>>>>>>>>> "amd64", family: "unix"
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <
>>>> joe.witt@gmail.com
>>>>>>>
>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do
>>>>>> you
>>>>>>>>>> get
>>>>>>>>>>>>>>>> back?
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <
>>>>>> j.007ba7@gmail.com>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>> I’m getting the below on a VM. It does build
>>>>>> successfully
>>>>>>>>>> on my
>>>>>>>>>>>>>>>>>> Mac, though.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install
>>>>>>>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>> ->
>>>>>>>>>> [Help 1]
>>>>>>>>>>>>>>>>>>>>>>>>
>>>> org.apache.maven.lifecycle.LifecycleExecutionException:
>>>>>>>>>> Failed
>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>> execute goal
>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>>>>>>>>>>>>>>>>> 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:1142)
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>>>>>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>>>>>>>>>>>>>>>>> Caused by:
>>>>>>>>>>>>>>>>>>
>>>> org.apache.maven.plugin.compiler.CompilationFailureException:
>>>>>>>>>>>>>>>> Compilation
>>>>>>>>>>>>>>>>>> failure
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>>>>>>>>>>>>>>>>> ... 11 more
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>
Re: nifi fails build on CentOS 7
Posted by Joe Witt <jo...@gmail.com>.
thanks for reporting this Jeff and your timing could not have been better!
It's happening for Gilman as well.
Joe
On Mon, Dec 7, 2015 at 4:31 PM, Jeff <j....@gmail.com> wrote:
> Yes, CentOS 7
>
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.703 sec - in org.apache.nifi.processors.hadoop.TestListHDFS
>
> Results :
>
> Failed tests:
> PutHDFSTest.testPutFileWithException:230 null
>
>
>
> Tests run: 21, Failures: 1, Errors: 0, Skipped: 0
>
>
>
>> On Dec 7, 2015, at 3:28 PM, Matt Gilman <ma...@gmail.com> wrote:
>>
>> Jeff,
>>
>> Are you still running on CentOS 7? Can you provide more details about the
>> unit test is failing? Thanks!
>>
>> Matt
>>
>> On Mon, Dec 7, 2015 at 4:24 PM, Jeff <j....@gmail.com> wrote:
>>
>>> I just cloned Nifi but I’m still seeing these errors when I do mvn -e -X
>>> -T 2.0C clean install
>>>
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
>>> project nifi-hdfs-processors: There are test failures.
>>> [ERROR]
>>> [ERROR] Please refer to
>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>> for the individual test results.
>>> [ERROR] -> [Help 1]
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>>> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>> (default-test) on project nifi-hdfs-processors: There are test failures.
>>>
>>> Please refer to
>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>> for the individual test results.
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>> at
>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>> at
>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>> 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:1142)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>> at java.lang.Thread.run(Thread.java:745)
>>> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
>>> failures.
>>>
>>> Please refer to
>>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>>> for the individual test results.
>>> at
>>> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
>>> at
>>> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
>>> at
>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
>>> at
>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>>> at
>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>> ... 11 more
>>> [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/MojoFailureException
>>> [ERROR]
>>> [ERROR] After correcting the problems, you can resume the build with the
>>> command
>>> [ERROR] mvn <goals> -rf :nifi-hdfs-processors
>>>
>>>
>>>
>>>> On Nov 10, 2015, at 12:33 PM, Aldrin Piri <al...@gmail.com> wrote:
>>>>
>>>> Seems there is in fact an issue with the test cited prior. I received
>>> the
>>>> following on my Travis CI build on a branch which has the latest of
>>> master
>>>> merged into it. Unfortunately, it seems that the environment is not the
>>>> same as before.
>>>>
>>>> In this case, Travis CI is running with Ubuntu 12.04 LTS [1]. For the
>>>> particular build [2], Oracle JDK 7 built without issue, but Oracle JDK 8
>>>> exhibited the same problem [3] as reported by Jeff.
>>>>
>>>> NIFI-1145 was created to track this issue [4]
>>>>
>>>> [1]
>>>>
>>> http://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
>>>> [2] https://travis-ci.org/apiri/incubator-nifi/builds/90353191
>>>> [3] https://s3.amazonaws.com/archive.travis-ci.org/jobs/90353192/log.txt
>>>> [4] https://issues.apache.org/jira/browse/NIFI-1145
>>>>
>>>> On Thu, Nov 5, 2015 at 5:17 PM, Jeff <j....@gmail.com> wrote:
>>>>
>>>>>
>>>>>
>>>>> I built a new VM CentOS7
>>>>>
>>>>> I get the below most of the time though last night it did succeeded.
>>>>>
>>>>> [INFO] nifi-framework-core ................................ FAILURE
>>> [02:41
>>>>> min]
>>>>>
>>>>> [INFO] BUILD FAILURE
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [INFO] Total time: 08:51 min (Wall Clock)
>>>>> [INFO] Finished at: 2015-11-05T16:09:51-06:00
>>>>> [INFO] Final Memory: 183M/514M
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [ERROR] Failed to execute goal
>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test)
>>> on
>>>>> project nifi-framework-core: There are test failures.
>>>>> [ERROR]
>>>>> [ERROR] Please refer to
>>>>>
>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>> for the individual test results.
>>>>> [ERROR] -> [Help 1]
>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>> execute
>>>>> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>>> (default-test) on project nifi-framework-core: There are test failures.
>>>>>
>>>>> Please refer to
>>>>>
>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>> for the individual test results.
>>>>> at
>>>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>> at
>>>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>> at
>>>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>> at
>>>>>
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>> at
>>>>>
>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>> at
>>>>>
>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>> 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:1142)
>>>>> at
>>>>>
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
>>>>> failures.
>>>>>
>>>>> Please refer to
>>>>>
>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>> for the individual test results.
>>>>> at
>>>>>
>>> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
>>>>> at
>>>>>
>>> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
>>>>> at
>>>>>
>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
>>>>> at
>>>>>
>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>>>>> at
>>>>>
>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>> at
>>>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>> ... 11 more
>>>>> [ERROR]
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> On Nov 4, 2015, at 9:01 AM, Mark Payne <ma...@hotmail.com> wrote:
>>>>>>
>>>>>> Jeff,
>>>>>>
>>>>>> I just checked out a fresh build from master, running on CentOS 7 and
>>>>> was able to build without any problems.
>>>>>> So I don't think it is specifically a problem with CentOS 7. Can you
>>>>> provide the output of the unit tests?
>>>>>>
>>>>>> They should be in
>>>>>
>>> ${NIFI_SRC_DIR}/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>
>>>>>> The two files of interest are
>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue.txt and
>>>>> org.apache.nifi.controller.TestStandardFlowFileQueue-output.txt
>>>>>>
>>>>>> Thanks!
>>>>>> -Mark
>>>>>>
>>>>>>
>>>>>>> On Nov 4, 2015, at 8:53 AM, Jeff <j....@gmail.com> wrote:
>>>>>>>
>>>>>>> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.916
>>>>> sec <<< FAILURE! - in
>>> org.apache.nifi.controller.TestStandardFlowFileQueue
>>>>>>>
>>>>>
>>> testDropSwappedFlowFiles(org.apache.nifi.controller.TestStandardFlowFileQueue)
>>>>> Time elapsed: 21.825 sec <<< ERROR!
>>>>>>> org.junit.runners.model.TestTimedOutException: test timed out after
>>>>> 20000 milliseconds
>>>>>>> at java.lang.Throwable.fillInStackTrace(Native Method)
>>>>>>> at java.lang.Throwable.fillInStackTrace(Throwable.java:783)
>>>>>>> at java.lang.Throwable.<init>(Throwable.java:250)
>>>>>>> at
>>>>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:24)
>>>>>>> at
>>>>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:19)
>>>>>>> at
>>>>>
>>> org.mockito.internal.invocation.InvocationImpl.<init>(InvocationImpl.java:50)
>>>>>>> at
>>>>>
>>> org.mockito.internal.creation.cglib.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:58)
>>>>>>> at
>>>>>
>>> org.apache.nifi.connectable.Connection$$EnhancerByMockitoWithCGLIB$$8aa704ad.getDestination(<generated>)
>>>>>>> at
>>>>>
>>> org.apache.nifi.controller.StandardFlowFileQueue.put(StandardFlowFileQueue.java:315)
>>>>>>> at
>>>>>
>>> org.apache.nifi.controller.TestStandardFlowFileQueue.testDropSwappedFlowFiles(TestStandardFlowFileQueue.java:169)
>>>>>>>
>>>>>>>> On Nov 4, 2015, at 7:51 AM, Brandon DeVries <br...@jhu.edu> wrote:
>>>>>>>>
>>>>>>>> Jeff,
>>>>>>>>
>>>>>>>> Can you see what tests had failures? Also, if you just want to
>>> verify
>>>>> that
>>>>>>>> your system can do the build, you could do something like "mvn clean
>>>>>>>> install -DskipTests". Let us know what you see. Thanks.
>>>>>>>>
>>>>>>>> Brandon
>>>>>>>>
>>>>>>>> On Wed, Nov 4, 2015 at 8:46 AM, Jeff <j....@gmail.com> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Well, the build got much further with the Oracle JDK but still
>>> failed;
>>>>>>>>>
>>>>>>>>> [INFO]
>>>>>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>> [INFO]
>>>>>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>>>>> [INFO] Total time: 07:47 min (Wall Clock)
>>>>>>>>> [INFO] Finished at: 2015-11-03T17:07:40-06:00
>>>>>>>>> [INFO] Final Memory: 183M/564M
>>>>>>>>> [INFO]
>>>>>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>>> (default-test) on
>>>>>>>>> project nifi-framework-core: There are test failures.
>>>>>>>>> [ERROR]
>>>>>>>>> [ERROR] Please refer to
>>>>>>>>>
>>>>>
>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>>> for the individual test results.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On Nov 3, 2015, at 6:54 PM, Cerulean Blue <j....@gmail.com>
>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Oh, I also adjusted the memory!
>>>>>>>>>>
>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>
>>>>>>>>>>> On Nov 3, 2015, at 6:50 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Jeff - can you please send another note telling Tony that it turns
>>>>> out
>>>>>>>>>>> it was memory settings :-)
>>>>>>>>>>>
>>>>>>>>>>> He is making fun of me off-list. He should totally do that
>>> on-list!
>>>>>>>>>>>
>>>>>>>>>>> Glad you're in business now and sorry for my terrible
>>> misdirection.
>>>>>>>>>>>
>>>>>>>>>>> Joe
>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com>
>>>>> wrote:
>>>>>>>>>>>> Huzzah
>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com>
>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I removed openjdk and installed the Oracle jdk and it now works.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks for the help!!
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com>
>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> it is entirely possible that you only have the jre installed.
>>>>> 'yum
>>>>>>>>>>>>>> whatprovides "*/bin/javac"' may tell you packages which you can
>>>>>>>>> install
>>>>>>>>>>>>>> which include a compiler.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com>
>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> find / -name javac did not return anything
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I had JAVA_HOME set to
>>>>>>>>>>>>>>>
>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com>
>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Jeff,
>>>>>>>>>>>>>>>> Were you able to run that find command?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com>
>>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>
>>>>>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>>>>> [INFO] Total time: 8.091 s
>>>>>>>>>>>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
>>>>>>>>>>>>>>>>> [INFO] Final Memory: 76M/365M
>>>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>
>>>>>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>> ->
>>>>>>>>> [Help 1]
>>>>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run
>>>>> Maven
>>>>>>>>> with
>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>> -e switch.
>>>>>>>>>>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full
>>> debug
>>>>>>>>> logging.
>>>>>>>>>>>>>>>>> [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/MojoFailureException
>>>>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>>>>> [ERROR] After correcting the problems, you can resume the
>>>>> build
>>>>>>>>> with
>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>> [ERROR] mvn <goals> -rf :nifi-api
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com>
>>>>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Can you go ahead and try just plain ol'
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I am curious if there is a memory/settings issue that is
>>>>>>>>> manifesting
>>>>>>>>>>>>>>>>>> as an exception during compilation but that it isn't
>>>>> actually a
>>>>>>>>>>>>>>>>>> compilation problem at all...
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j.007ba7@gmail.com
>>>>
>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>> The only other message I see is
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac'
>>>>> from
>>>>>>>>> the
>>>>>>>>>>>>>>>>> environment.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> No worries, it can wait.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <joe.witt@gmail.com
>>>>
>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to
>>>>> pull
>>>>>>>>> down
>>>>>>>>>>>>>>>>>>>> centos. Is there anymore that can be found with those
>>>>> stack
>>>>>>>>>>>>> traces .
>>>>>>>>>>>>>>>>>>>> They're not saying much. Your java and maven versions
>>> seem
>>>>>>>>> quite
>>>>>>>>>>>>>>> good
>>>>>>>>>>>>>>>>>>>> so need to dig further.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <
>>> j.007ba7@gmail.com
>>>>>>
>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> [root@localhost nifi]# java -version
>>>>>>>>>>>>>>>>>>>>> openjdk version "1.8.0_65"
>>>>>>>>>>>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>>>>>>>>>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> [root@localhost nifi]# mvn -version
>>>>>>>>>>>>>>>>>>>>> which: no javac in
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>>>>>>>>>>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set.
>>>>>>>>>>>>>>>>>>>>> Apache Maven 3.3.3
>>>>> (7994120775791599e205a5524ec3e0dfe41d4a06;
>>>>>>>>>>>>>>>>> 2015-04-22T06:57:37-05:00)
>>>>>>>>>>>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3
>>>>>>>>>>>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>>>>>>>>>>>>>>>>>>>> Java home:
>>>>>>>>>>>>>>>>>
>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>>>>>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64",
>>>>> arch:
>>>>>>>>>>>>>>>>> "amd64", family: "unix"
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <
>>> joe.witt@gmail.com
>>>>>>
>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do
>>>>> you
>>>>>>>>> get
>>>>>>>>>>>>>>> back?
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <
>>>>> j.007ba7@gmail.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>> I’m getting the below on a VM. It does build
>>>>> successfully
>>>>>>>>> on my
>>>>>>>>>>>>>>>>> Mac, though.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install
>>>>>>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>> ->
>>>>>>>>> [Help 1]
>>>>>>>>>>>>>>>>>>>>>>>
>>> org.apache.maven.lifecycle.LifecycleExecutionException:
>>>>>>>>> Failed
>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>> execute goal
>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>>>>>>>>>>>>>>>> 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:1142)
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>>>>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>>>>>>>>>>>>>>>> Caused by:
>>>>>>>>>>>>>>>>>
>>> org.apache.maven.plugin.compiler.CompilationFailureException:
>>>>>>>>>>>>>>> Compilation
>>>>>>>>>>>>>>>>> failure
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>>>>>>>>>>>>>>>> ... 11 more
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>
>>>
>
Re: nifi fails build on CentOS 7
Posted by Jeff <j....@gmail.com>.
Yes, CentOS 7
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.703 sec - in org.apache.nifi.processors.hadoop.TestListHDFS
Results :
Failed tests:
PutHDFSTest.testPutFileWithException:230 null
Tests run: 21, Failures: 1, Errors: 0, Skipped: 0
> On Dec 7, 2015, at 3:28 PM, Matt Gilman <ma...@gmail.com> wrote:
>
> Jeff,
>
> Are you still running on CentOS 7? Can you provide more details about the
> unit test is failing? Thanks!
>
> Matt
>
> On Mon, Dec 7, 2015 at 4:24 PM, Jeff <j....@gmail.com> wrote:
>
>> I just cloned Nifi but I’m still seeing these errors when I do mvn -e -X
>> -T 2.0C clean install
>>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
>> project nifi-hdfs-processors: There are test failures.
>> [ERROR]
>> [ERROR] Please refer to
>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>> for the individual test results.
>> [ERROR] -> [Help 1]
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>> (default-test) on project nifi-hdfs-processors: There are test failures.
>>
>> Please refer to
>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>> for the individual test results.
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>> at
>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>> at
>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>> 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:1142)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:745)
>> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
>> failures.
>>
>> Please refer to
>> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
>> for the individual test results.
>> at
>> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
>> at
>> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
>> at
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
>> at
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>> at
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>> ... 11 more
>> [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/MojoFailureException
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>> [ERROR] mvn <goals> -rf :nifi-hdfs-processors
>>
>>
>>
>>> On Nov 10, 2015, at 12:33 PM, Aldrin Piri <al...@gmail.com> wrote:
>>>
>>> Seems there is in fact an issue with the test cited prior. I received
>> the
>>> following on my Travis CI build on a branch which has the latest of
>> master
>>> merged into it. Unfortunately, it seems that the environment is not the
>>> same as before.
>>>
>>> In this case, Travis CI is running with Ubuntu 12.04 LTS [1]. For the
>>> particular build [2], Oracle JDK 7 built without issue, but Oracle JDK 8
>>> exhibited the same problem [3] as reported by Jeff.
>>>
>>> NIFI-1145 was created to track this issue [4]
>>>
>>> [1]
>>>
>> http://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
>>> [2] https://travis-ci.org/apiri/incubator-nifi/builds/90353191
>>> [3] https://s3.amazonaws.com/archive.travis-ci.org/jobs/90353192/log.txt
>>> [4] https://issues.apache.org/jira/browse/NIFI-1145
>>>
>>> On Thu, Nov 5, 2015 at 5:17 PM, Jeff <j....@gmail.com> wrote:
>>>
>>>>
>>>>
>>>> I built a new VM CentOS7
>>>>
>>>> I get the below most of the time though last night it did succeeded.
>>>>
>>>> [INFO] nifi-framework-core ................................ FAILURE
>> [02:41
>>>> min]
>>>>
>>>> [INFO] BUILD FAILURE
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Total time: 08:51 min (Wall Clock)
>>>> [INFO] Finished at: 2015-11-05T16:09:51-06:00
>>>> [INFO] Final Memory: 183M/514M
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [ERROR] Failed to execute goal
>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test)
>> on
>>>> project nifi-framework-core: There are test failures.
>>>> [ERROR]
>>>> [ERROR] Please refer to
>>>>
>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>> for the individual test results.
>>>> [ERROR] -> [Help 1]
>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>> execute
>>>> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>> (default-test) on project nifi-framework-core: There are test failures.
>>>>
>>>> Please refer to
>>>>
>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>> for the individual test results.
>>>> at
>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>> at
>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>> at
>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>> at
>>>>
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>> at
>>>>
>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>> at
>>>>
>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>> 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:1142)
>>>> at
>>>>
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>> at java.lang.Thread.run(Thread.java:745)
>>>> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
>>>> failures.
>>>>
>>>> Please refer to
>>>>
>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>> for the individual test results.
>>>> at
>>>>
>> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
>>>> at
>>>>
>> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
>>>> at
>>>>
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
>>>> at
>>>>
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>>>> at
>>>>
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>> at
>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>> ... 11 more
>>>> [ERROR]
>>>>
>>>>
>>>>
>>>>
>>>>> On Nov 4, 2015, at 9:01 AM, Mark Payne <ma...@hotmail.com> wrote:
>>>>>
>>>>> Jeff,
>>>>>
>>>>> I just checked out a fresh build from master, running on CentOS 7 and
>>>> was able to build without any problems.
>>>>> So I don't think it is specifically a problem with CentOS 7. Can you
>>>> provide the output of the unit tests?
>>>>>
>>>>> They should be in
>>>>
>> ${NIFI_SRC_DIR}/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>
>>>>> The two files of interest are
>>>> org.apache.nifi.controller.TestStandardFlowFileQueue.txt and
>>>> org.apache.nifi.controller.TestStandardFlowFileQueue-output.txt
>>>>>
>>>>> Thanks!
>>>>> -Mark
>>>>>
>>>>>
>>>>>> On Nov 4, 2015, at 8:53 AM, Jeff <j....@gmail.com> wrote:
>>>>>>
>>>>>> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.916
>>>> sec <<< FAILURE! - in
>> org.apache.nifi.controller.TestStandardFlowFileQueue
>>>>>>
>>>>
>> testDropSwappedFlowFiles(org.apache.nifi.controller.TestStandardFlowFileQueue)
>>>> Time elapsed: 21.825 sec <<< ERROR!
>>>>>> org.junit.runners.model.TestTimedOutException: test timed out after
>>>> 20000 milliseconds
>>>>>> at java.lang.Throwable.fillInStackTrace(Native Method)
>>>>>> at java.lang.Throwable.fillInStackTrace(Throwable.java:783)
>>>>>> at java.lang.Throwable.<init>(Throwable.java:250)
>>>>>> at
>>>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:24)
>>>>>> at
>>>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:19)
>>>>>> at
>>>>
>> org.mockito.internal.invocation.InvocationImpl.<init>(InvocationImpl.java:50)
>>>>>> at
>>>>
>> org.mockito.internal.creation.cglib.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:58)
>>>>>> at
>>>>
>> org.apache.nifi.connectable.Connection$$EnhancerByMockitoWithCGLIB$$8aa704ad.getDestination(<generated>)
>>>>>> at
>>>>
>> org.apache.nifi.controller.StandardFlowFileQueue.put(StandardFlowFileQueue.java:315)
>>>>>> at
>>>>
>> org.apache.nifi.controller.TestStandardFlowFileQueue.testDropSwappedFlowFiles(TestStandardFlowFileQueue.java:169)
>>>>>>
>>>>>>> On Nov 4, 2015, at 7:51 AM, Brandon DeVries <br...@jhu.edu> wrote:
>>>>>>>
>>>>>>> Jeff,
>>>>>>>
>>>>>>> Can you see what tests had failures? Also, if you just want to
>> verify
>>>> that
>>>>>>> your system can do the build, you could do something like "mvn clean
>>>>>>> install -DskipTests". Let us know what you see. Thanks.
>>>>>>>
>>>>>>> Brandon
>>>>>>>
>>>>>>> On Wed, Nov 4, 2015 at 8:46 AM, Jeff <j....@gmail.com> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> Well, the build got much further with the Oracle JDK but still
>> failed;
>>>>>>>>
>>>>>>>> [INFO]
>>>>>>>>
>>>> ------------------------------------------------------------------------
>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>> [INFO]
>>>>>>>>
>>>> ------------------------------------------------------------------------
>>>>>>>> [INFO] Total time: 07:47 min (Wall Clock)
>>>>>>>> [INFO] Finished at: 2015-11-03T17:07:40-06:00
>>>>>>>> [INFO] Final Memory: 183M/564M
>>>>>>>> [INFO]
>>>>>>>>
>>>> ------------------------------------------------------------------------
>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>>>> (default-test) on
>>>>>>>> project nifi-framework-core: There are test failures.
>>>>>>>> [ERROR]
>>>>>>>> [ERROR] Please refer to
>>>>>>>>
>>>>
>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>>>> for the individual test results.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Nov 3, 2015, at 6:54 PM, Cerulean Blue <j....@gmail.com>
>>>> wrote:
>>>>>>>>>
>>>>>>>>> Oh, I also adjusted the memory!
>>>>>>>>>
>>>>>>>>> Sent from my iPhone
>>>>>>>>>
>>>>>>>>>> On Nov 3, 2015, at 6:50 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Jeff - can you please send another note telling Tony that it turns
>>>> out
>>>>>>>>>> it was memory settings :-)
>>>>>>>>>>
>>>>>>>>>> He is making fun of me off-list. He should totally do that
>> on-list!
>>>>>>>>>>
>>>>>>>>>> Glad you're in business now and sorry for my terrible
>> misdirection.
>>>>>>>>>>
>>>>>>>>>> Joe
>>>>>>>>>>
>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com>
>>>> wrote:
>>>>>>>>>>> Huzzah
>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com>
>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> I removed openjdk and installed the Oracle jdk and it now works.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks for the help!!
>>>>>>>>>>>>
>>>>>>>>>>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com>
>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> it is entirely possible that you only have the jre installed.
>>>> 'yum
>>>>>>>>>>>>> whatprovides "*/bin/javac"' may tell you packages which you can
>>>>>>>> install
>>>>>>>>>>>>> which include a compiler.
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com>
>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> find / -name javac did not return anything
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I had JAVA_HOME set to
>>>>>>>>>>>>>>
>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com>
>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Jeff,
>>>>>>>>>>>>>>> Were you able to run that find command?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com>
>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>
>>>>>>>>
>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>>>> [INFO] Total time: 8.091 s
>>>>>>>>>>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
>>>>>>>>>>>>>>>> [INFO] Final Memory: 76M/365M
>>>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>
>>>>>>>>
>>>> ------------------------------------------------------------------------
>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>> ->
>>>>>>>> [Help 1]
>>>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run
>>>> Maven
>>>>>>>> with
>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> -e switch.
>>>>>>>>>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full
>> debug
>>>>>>>> logging.
>>>>>>>>>>>>>>>> [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/MojoFailureException
>>>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>>>> [ERROR] After correcting the problems, you can resume the
>>>> build
>>>>>>>> with
>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>> [ERROR] mvn <goals> -rf :nifi-api
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com>
>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Can you go ahead and try just plain ol'
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I am curious if there is a memory/settings issue that is
>>>>>>>> manifesting
>>>>>>>>>>>>>>>>> as an exception during compilation but that it isn't
>>>> actually a
>>>>>>>>>>>>>>>>> compilation problem at all...
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j.007ba7@gmail.com
>>>
>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>> The only other message I see is
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac'
>>>> from
>>>>>>>> the
>>>>>>>>>>>>>>>> environment.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> No worries, it can wait.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <joe.witt@gmail.com
>>>
>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to
>>>> pull
>>>>>>>> down
>>>>>>>>>>>>>>>>>>> centos. Is there anymore that can be found with those
>>>> stack
>>>>>>>>>>>> traces .
>>>>>>>>>>>>>>>>>>> They're not saying much. Your java and maven versions
>> seem
>>>>>>>> quite
>>>>>>>>>>>>>> good
>>>>>>>>>>>>>>>>>>> so need to dig further.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <
>> j.007ba7@gmail.com
>>>>>
>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> [root@localhost nifi]# java -version
>>>>>>>>>>>>>>>>>>>> openjdk version "1.8.0_65"
>>>>>>>>>>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>>>>>>>>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> [root@localhost nifi]# mvn -version
>>>>>>>>>>>>>>>>>>>> which: no javac in
>>>>>>>>>>>>
>>>>>>>>
>>>>
>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>>>>>>>>>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set.
>>>>>>>>>>>>>>>>>>>> Apache Maven 3.3.3
>>>> (7994120775791599e205a5524ec3e0dfe41d4a06;
>>>>>>>>>>>>>>>> 2015-04-22T06:57:37-05:00)
>>>>>>>>>>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3
>>>>>>>>>>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>>>>>>>>>>>>>>>>>>> Java home:
>>>>>>>>>>>>>>>>
>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>>>>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64",
>>>> arch:
>>>>>>>>>>>>>>>> "amd64", family: "unix"
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <
>> joe.witt@gmail.com
>>>>>
>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do
>>>> you
>>>>>>>> get
>>>>>>>>>>>>>> back?
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <
>>>> j.007ba7@gmail.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>> I’m getting the below on a VM. It does build
>>>> successfully
>>>>>>>> on my
>>>>>>>>>>>>>>>> Mac, though.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install
>>>>>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>> ->
>>>>>>>> [Help 1]
>>>>>>>>>>>>>>>>>>>>>>
>> org.apache.maven.lifecycle.LifecycleExecutionException:
>>>>>>>> Failed
>>>>>>>>>>>> to
>>>>>>>>>>>>>>>> execute goal
>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>
>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>
>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>
>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>
>>>>
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>
>>>>
>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>
>>>>
>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>>>>>>>>>>>>>>> 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:1142)
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>
>>>>
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>>>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>>>>>>>>>>>>>>> Caused by:
>>>>>>>>>>>>>>>>
>> org.apache.maven.plugin.compiler.CompilationFailureException:
>>>>>>>>>>>>>> Compilation
>>>>>>>>>>>>>>>> failure
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>
>>>>
>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>
>>>>
>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>
>>>>
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>
>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>>>>>>>>>>>>>>> ... 11 more
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>
>>
Re: nifi fails build on CentOS 7
Posted by Matt Gilman <ma...@gmail.com>.
Jeff,
Are you still running on CentOS 7? Can you provide more details about the
unit test is failing? Thanks!
Matt
On Mon, Dec 7, 2015 at 4:24 PM, Jeff <j....@gmail.com> wrote:
> I just cloned Nifi but I’m still seeing these errors when I do mvn -e -X
> -T 2.0C clean install
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
> project nifi-hdfs-processors: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
> for the individual test results.
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
> (default-test) on project nifi-hdfs-processors: There are test failures.
>
> Please refer to
> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
> for the individual test results.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
> 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:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
> failures.
>
> Please refer to
> /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports
> for the individual test results.
> at
> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
> at
> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 11 more
> [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/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :nifi-hdfs-processors
>
>
>
> > On Nov 10, 2015, at 12:33 PM, Aldrin Piri <al...@gmail.com> wrote:
> >
> > Seems there is in fact an issue with the test cited prior. I received
> the
> > following on my Travis CI build on a branch which has the latest of
> master
> > merged into it. Unfortunately, it seems that the environment is not the
> > same as before.
> >
> > In this case, Travis CI is running with Ubuntu 12.04 LTS [1]. For the
> > particular build [2], Oracle JDK 7 built without issue, but Oracle JDK 8
> > exhibited the same problem [3] as reported by Jeff.
> >
> > NIFI-1145 was created to track this issue [4]
> >
> > [1]
> >
> http://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
> > [2] https://travis-ci.org/apiri/incubator-nifi/builds/90353191
> > [3] https://s3.amazonaws.com/archive.travis-ci.org/jobs/90353192/log.txt
> > [4] https://issues.apache.org/jira/browse/NIFI-1145
> >
> > On Thu, Nov 5, 2015 at 5:17 PM, Jeff <j....@gmail.com> wrote:
> >
> >>
> >>
> >> I built a new VM CentOS7
> >>
> >> I get the below most of the time though last night it did succeeded.
> >>
> >> [INFO] nifi-framework-core ................................ FAILURE
> [02:41
> >> min]
> >>
> >> [INFO] BUILD FAILURE
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] Total time: 08:51 min (Wall Clock)
> >> [INFO] Finished at: 2015-11-05T16:09:51-06:00
> >> [INFO] Final Memory: 183M/514M
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [ERROR] Failed to execute goal
> >> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test)
> on
> >> project nifi-framework-core: There are test failures.
> >> [ERROR]
> >> [ERROR] Please refer to
> >>
> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
> >> for the individual test results.
> >> [ERROR] -> [Help 1]
> >> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute
> >> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
> >> (default-test) on project nifi-framework-core: There are test failures.
> >>
> >> Please refer to
> >>
> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
> >> for the individual test results.
> >> at
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> >> at
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> >> at
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> >> at
> >>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> >> at
> >>
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
> >> at
> >>
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
> >> 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:1142)
> >> at
> >>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> >> at java.lang.Thread.run(Thread.java:745)
> >> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
> >> failures.
> >>
> >> Please refer to
> >>
> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
> >> for the individual test results.
> >> at
> >>
> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
> >> at
> >>
> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
> >> at
> >>
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
> >> at
> >>
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
> >> at
> >>
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> >> at
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> >> ... 11 more
> >> [ERROR]
> >>
> >>
> >>
> >>
> >>> On Nov 4, 2015, at 9:01 AM, Mark Payne <ma...@hotmail.com> wrote:
> >>>
> >>> Jeff,
> >>>
> >>> I just checked out a fresh build from master, running on CentOS 7 and
> >> was able to build without any problems.
> >>> So I don't think it is specifically a problem with CentOS 7. Can you
> >> provide the output of the unit tests?
> >>>
> >>> They should be in
> >>
> ${NIFI_SRC_DIR}/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
> >>>
> >>> The two files of interest are
> >> org.apache.nifi.controller.TestStandardFlowFileQueue.txt and
> >> org.apache.nifi.controller.TestStandardFlowFileQueue-output.txt
> >>>
> >>> Thanks!
> >>> -Mark
> >>>
> >>>
> >>>> On Nov 4, 2015, at 8:53 AM, Jeff <j....@gmail.com> wrote:
> >>>>
> >>>> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.916
> >> sec <<< FAILURE! - in
> org.apache.nifi.controller.TestStandardFlowFileQueue
> >>>>
> >>
> testDropSwappedFlowFiles(org.apache.nifi.controller.TestStandardFlowFileQueue)
> >> Time elapsed: 21.825 sec <<< ERROR!
> >>>> org.junit.runners.model.TestTimedOutException: test timed out after
> >> 20000 milliseconds
> >>>> at java.lang.Throwable.fillInStackTrace(Native Method)
> >>>> at java.lang.Throwable.fillInStackTrace(Throwable.java:783)
> >>>> at java.lang.Throwable.<init>(Throwable.java:250)
> >>>> at
> >> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:24)
> >>>> at
> >> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:19)
> >>>> at
> >>
> org.mockito.internal.invocation.InvocationImpl.<init>(InvocationImpl.java:50)
> >>>> at
> >>
> org.mockito.internal.creation.cglib.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:58)
> >>>> at
> >>
> org.apache.nifi.connectable.Connection$$EnhancerByMockitoWithCGLIB$$8aa704ad.getDestination(<generated>)
> >>>> at
> >>
> org.apache.nifi.controller.StandardFlowFileQueue.put(StandardFlowFileQueue.java:315)
> >>>> at
> >>
> org.apache.nifi.controller.TestStandardFlowFileQueue.testDropSwappedFlowFiles(TestStandardFlowFileQueue.java:169)
> >>>>
> >>>>> On Nov 4, 2015, at 7:51 AM, Brandon DeVries <br...@jhu.edu> wrote:
> >>>>>
> >>>>> Jeff,
> >>>>>
> >>>>> Can you see what tests had failures? Also, if you just want to
> verify
> >> that
> >>>>> your system can do the build, you could do something like "mvn clean
> >>>>> install -DskipTests". Let us know what you see. Thanks.
> >>>>>
> >>>>> Brandon
> >>>>>
> >>>>> On Wed, Nov 4, 2015 at 8:46 AM, Jeff <j....@gmail.com> wrote:
> >>>>>
> >>>>>>
> >>>>>> Well, the build got much further with the Oracle JDK but still
> failed;
> >>>>>>
> >>>>>> [INFO]
> >>>>>>
> >> ------------------------------------------------------------------------
> >>>>>> [INFO] BUILD FAILURE
> >>>>>> [INFO]
> >>>>>>
> >> ------------------------------------------------------------------------
> >>>>>> [INFO] Total time: 07:47 min (Wall Clock)
> >>>>>> [INFO] Finished at: 2015-11-03T17:07:40-06:00
> >>>>>> [INFO] Final Memory: 183M/564M
> >>>>>> [INFO]
> >>>>>>
> >> ------------------------------------------------------------------------
> >>>>>> [ERROR] Failed to execute goal
> >>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test
> >> (default-test) on
> >>>>>> project nifi-framework-core: There are test failures.
> >>>>>> [ERROR]
> >>>>>> [ERROR] Please refer to
> >>>>>>
> >>
> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
> >>>>>> for the individual test results.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> On Nov 3, 2015, at 6:54 PM, Cerulean Blue <j....@gmail.com>
> >> wrote:
> >>>>>>>
> >>>>>>> Oh, I also adjusted the memory!
> >>>>>>>
> >>>>>>> Sent from my iPhone
> >>>>>>>
> >>>>>>>> On Nov 3, 2015, at 6:50 PM, Joe Witt <jo...@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>> Jeff - can you please send another note telling Tony that it turns
> >> out
> >>>>>>>> it was memory settings :-)
> >>>>>>>>
> >>>>>>>> He is making fun of me off-list. He should totally do that
> on-list!
> >>>>>>>>
> >>>>>>>> Glad you're in business now and sorry for my terrible
> misdirection.
> >>>>>>>>
> >>>>>>>> Joe
> >>>>>>>>
> >>>>>>>>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com>
> >> wrote:
> >>>>>>>>> Huzzah
> >>>>>>>>>
> >>>>>>>>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com>
> wrote:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> I removed openjdk and installed the Oracle jdk and it now works.
> >>>>>>>>>>
> >>>>>>>>>> Thanks for the help!!
> >>>>>>>>>>
> >>>>>>>>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com>
> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> it is entirely possible that you only have the jre installed.
> >> 'yum
> >>>>>>>>>>> whatprovides "*/bin/javac"' may tell you packages which you can
> >>>>>> install
> >>>>>>>>>>> which include a compiler.
> >>>>>>>>>>>
> >>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com>
> >> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> find / -name javac did not return anything
> >>>>>>>>>>>>
> >>>>>>>>>>>> I had JAVA_HOME set to
> >>>>>>>>>>>>
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com>
> >> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Jeff,
> >>>>>>>>>>>>> Were you able to run that find command?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com>
> >> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> [INFO] BUILD FAILURE
> >>>>>>>>>>>>>> [INFO]
> >>>>>>>>>>
> >>>>>>
> >> ------------------------------------------------------------------------
> >>>>>>>>>>>>>> [INFO] Total time: 8.091 s
> >>>>>>>>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
> >>>>>>>>>>>>>> [INFO] Final Memory: 76M/365M
> >>>>>>>>>>>>>> [INFO]
> >>>>>>>>>>
> >>>>>>
> >> ------------------------------------------------------------------------
> >>>>>>>>>>>>>> [ERROR] Failed to execute goal
> >>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
> ->
> >>>>>> [Help 1]
> >>>>>>>>>>>>>> [ERROR]
> >>>>>>>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run
> >> Maven
> >>>>>> with
> >>>>>>>>>> the
> >>>>>>>>>>>>>> -e switch.
> >>>>>>>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full
> debug
> >>>>>> logging.
> >>>>>>>>>>>>>> [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/MojoFailureException
> >>>>>>>>>>>>>> [ERROR]
> >>>>>>>>>>>>>> [ERROR] After correcting the problems, you can resume the
> >> build
> >>>>>> with
> >>>>>>>>>> the
> >>>>>>>>>>>>>> command
> >>>>>>>>>>>>>> [ERROR] mvn <goals> -rf :nifi-api
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com>
> >> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Can you go ahead and try just plain ol'
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> mvn clean install
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> I am curious if there is a memory/settings issue that is
> >>>>>> manifesting
> >>>>>>>>>>>>>>> as an exception during compilation but that it isn't
> >> actually a
> >>>>>>>>>>>>>>> compilation problem at all...
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j.007ba7@gmail.com
> >
> >>>>>> wrote:
> >>>>>>>>>>>>>>>> The only other message I see is
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac'
> >> from
> >>>>>> the
> >>>>>>>>>>>>>> environment.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> No worries, it can wait.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <joe.witt@gmail.com
> >
> >>>>>> wrote:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to
> >> pull
> >>>>>> down
> >>>>>>>>>>>>>>>>> centos. Is there anymore that can be found with those
> >> stack
> >>>>>>>>>> traces .
> >>>>>>>>>>>>>>>>> They're not saying much. Your java and maven versions
> seem
> >>>>>> quite
> >>>>>>>>>>>> good
> >>>>>>>>>>>>>>>>> so need to dig further.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <
> j.007ba7@gmail.com
> >>>
> >>>>>> wrote:
> >>>>>>>>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> [root@localhost nifi]# java -version
> >>>>>>>>>>>>>>>>>> openjdk version "1.8.0_65"
> >>>>>>>>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
> >>>>>>>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> [root@localhost nifi]# mvn -version
> >>>>>>>>>>>>>>>>>> which: no javac in
> >>>>>>>>>>
> >>>>>>
> >>
> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
> >>>>>>>>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set.
> >>>>>>>>>>>>>>>>>> Apache Maven 3.3.3
> >> (7994120775791599e205a5524ec3e0dfe41d4a06;
> >>>>>>>>>>>>>> 2015-04-22T06:57:37-05:00)
> >>>>>>>>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3
> >>>>>>>>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
> >>>>>>>>>>>>>>>>>> Java home:
> >>>>>>>>>>>>>>
> >> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
> >>>>>>>>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
> >>>>>>>>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64",
> >> arch:
> >>>>>>>>>>>>>> "amd64", family: "unix"
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <
> joe.witt@gmail.com
> >>>
> >>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Jeff
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do
> >> you
> >>>>>> get
> >>>>>>>>>>>> back?
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Thanks
> >>>>>>>>>>>>>>>>>>> Joe
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <
> >> j.007ba7@gmail.com>
> >>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>> I’m getting the below on a VM. It does build
> >> successfully
> >>>>>> on my
> >>>>>>>>>>>>>> Mac, though.
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install
> >>>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
> >>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
> ->
> >>>>>> [Help 1]
> >>>>>>>>>>>>>>>>>>>>
> org.apache.maven.lifecycle.LifecycleExecutionException:
> >>>>>> Failed
> >>>>>>>>>> to
> >>>>>>>>>>>>>> execute goal
> >>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
> >>>>>>>>>>>>>>>>>>>> at
> >>>>>>>>>>
> >>>>>>
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> >>>>>>>>>>>>>>>>>>>> at
> >>>>>>>>>>
> >>>>>>
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> >>>>>>>>>>>>>>>>>>>> at
> >>>>>>>>>>
> >>>>>>
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> >>>>>>>>>>>>>>>>>>>> at
> >>>>>>>>>>
> >>>>>>
> >>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> >>>>>>>>>>>>>>>>>>>> at
> >>>>>>>>>>
> >>>>>>
> >>
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
> >>>>>>>>>>>>>>>>>>>> at
> >>>>>>>>>>
> >>>>>>
> >>
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
> >>>>>>>>>>>>>>>>>>>> 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:1142)
> >>>>>>>>>>>>>>>>>>>> at
> >>>>>>>>>>
> >>>>>>
> >>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> >>>>>>>>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
> >>>>>>>>>>>>>>>>>>>> Caused by:
> >>>>>>>>>>>>>>
> org.apache.maven.plugin.compiler.CompilationFailureException:
> >>>>>>>>>>>> Compilation
> >>>>>>>>>>>>>> failure
> >>>>>>>>>>>>>>>>>>>> at
> >>>>>>>>>>
> >>>>>>
> >>
> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
> >>>>>>>>>>>>>>>>>>>> at
> >>>>>>>>>>
> >>>>>>
> >>
> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
> >>>>>>>>>>>>>>>>>>>> at
> >>>>>>>>>>
> >>>>>>
> >>
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> >>>>>>>>>>>>>>>>>>>> at
> >>>>>>>>>>
> >>>>>>
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> >>>>>>>>>>>>>>>>>>>> ... 11 more
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>>>>>>>> Jeff
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>
> >>>>>>
> >>>>
> >>>
> >>
> >>
>
>
Re: nifi fails build on CentOS 7
Posted by Jeff <j....@gmail.com>.
I just cloned Nifi but I’m still seeing these errors when I do mvn -e -X -T 2.0C clean install
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on project nifi-hdfs-processors: There are test failures.
[ERROR]
[ERROR] Please refer to /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports for the individual test results.
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on project nifi-hdfs-processors: There are test failures.
Please refer to /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports for the individual test results.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
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:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures.
Please refer to /root/nifi/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/target/surefire-reports for the individual test results.
at org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
at org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 11 more
[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/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :nifi-hdfs-processors
> On Nov 10, 2015, at 12:33 PM, Aldrin Piri <al...@gmail.com> wrote:
>
> Seems there is in fact an issue with the test cited prior. I received the
> following on my Travis CI build on a branch which has the latest of master
> merged into it. Unfortunately, it seems that the environment is not the
> same as before.
>
> In this case, Travis CI is running with Ubuntu 12.04 LTS [1]. For the
> particular build [2], Oracle JDK 7 built without issue, but Oracle JDK 8
> exhibited the same problem [3] as reported by Jeff.
>
> NIFI-1145 was created to track this issue [4]
>
> [1]
> http://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
> [2] https://travis-ci.org/apiri/incubator-nifi/builds/90353191
> [3] https://s3.amazonaws.com/archive.travis-ci.org/jobs/90353192/log.txt
> [4] https://issues.apache.org/jira/browse/NIFI-1145
>
> On Thu, Nov 5, 2015 at 5:17 PM, Jeff <j....@gmail.com> wrote:
>
>>
>>
>> I built a new VM CentOS7
>>
>> I get the below most of the time though last night it did succeeded.
>>
>> [INFO] nifi-framework-core ................................ FAILURE [02:41
>> min]
>>
>> [INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 08:51 min (Wall Clock)
>> [INFO] Finished at: 2015-11-05T16:09:51-06:00
>> [INFO] Final Memory: 183M/514M
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
>> project nifi-framework-core: There are test failures.
>> [ERROR]
>> [ERROR] Please refer to
>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>> for the individual test results.
>> [ERROR] -> [Help 1]
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>> (default-test) on project nifi-framework-core: There are test failures.
>>
>> Please refer to
>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>> for the individual test results.
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>> at
>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>> at
>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>> 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:1142)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:745)
>> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
>> failures.
>>
>> Please refer to
>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>> for the individual test results.
>> at
>> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
>> at
>> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
>> at
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
>> at
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>> at
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>> ... 11 more
>> [ERROR]
>>
>>
>>
>>
>>> On Nov 4, 2015, at 9:01 AM, Mark Payne <ma...@hotmail.com> wrote:
>>>
>>> Jeff,
>>>
>>> I just checked out a fresh build from master, running on CentOS 7 and
>> was able to build without any problems.
>>> So I don't think it is specifically a problem with CentOS 7. Can you
>> provide the output of the unit tests?
>>>
>>> They should be in
>> ${NIFI_SRC_DIR}/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>
>>> The two files of interest are
>> org.apache.nifi.controller.TestStandardFlowFileQueue.txt and
>> org.apache.nifi.controller.TestStandardFlowFileQueue-output.txt
>>>
>>> Thanks!
>>> -Mark
>>>
>>>
>>>> On Nov 4, 2015, at 8:53 AM, Jeff <j....@gmail.com> wrote:
>>>>
>>>> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.916
>> sec <<< FAILURE! - in org.apache.nifi.controller.TestStandardFlowFileQueue
>>>>
>> testDropSwappedFlowFiles(org.apache.nifi.controller.TestStandardFlowFileQueue)
>> Time elapsed: 21.825 sec <<< ERROR!
>>>> org.junit.runners.model.TestTimedOutException: test timed out after
>> 20000 milliseconds
>>>> at java.lang.Throwable.fillInStackTrace(Native Method)
>>>> at java.lang.Throwable.fillInStackTrace(Throwable.java:783)
>>>> at java.lang.Throwable.<init>(Throwable.java:250)
>>>> at
>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:24)
>>>> at
>> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:19)
>>>> at
>> org.mockito.internal.invocation.InvocationImpl.<init>(InvocationImpl.java:50)
>>>> at
>> org.mockito.internal.creation.cglib.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:58)
>>>> at
>> org.apache.nifi.connectable.Connection$$EnhancerByMockitoWithCGLIB$$8aa704ad.getDestination(<generated>)
>>>> at
>> org.apache.nifi.controller.StandardFlowFileQueue.put(StandardFlowFileQueue.java:315)
>>>> at
>> org.apache.nifi.controller.TestStandardFlowFileQueue.testDropSwappedFlowFiles(TestStandardFlowFileQueue.java:169)
>>>>
>>>>> On Nov 4, 2015, at 7:51 AM, Brandon DeVries <br...@jhu.edu> wrote:
>>>>>
>>>>> Jeff,
>>>>>
>>>>> Can you see what tests had failures? Also, if you just want to verify
>> that
>>>>> your system can do the build, you could do something like "mvn clean
>>>>> install -DskipTests". Let us know what you see. Thanks.
>>>>>
>>>>> Brandon
>>>>>
>>>>> On Wed, Nov 4, 2015 at 8:46 AM, Jeff <j....@gmail.com> wrote:
>>>>>
>>>>>>
>>>>>> Well, the build got much further with the Oracle JDK but still failed;
>>>>>>
>>>>>> [INFO]
>>>>>>
>> ------------------------------------------------------------------------
>>>>>> [INFO] BUILD FAILURE
>>>>>> [INFO]
>>>>>>
>> ------------------------------------------------------------------------
>>>>>> [INFO] Total time: 07:47 min (Wall Clock)
>>>>>> [INFO] Finished at: 2015-11-03T17:07:40-06:00
>>>>>> [INFO] Final Memory: 183M/564M
>>>>>> [INFO]
>>>>>>
>> ------------------------------------------------------------------------
>>>>>> [ERROR] Failed to execute goal
>>>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>> (default-test) on
>>>>>> project nifi-framework-core: There are test failures.
>>>>>> [ERROR]
>>>>>> [ERROR] Please refer to
>>>>>>
>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>>>> for the individual test results.
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On Nov 3, 2015, at 6:54 PM, Cerulean Blue <j....@gmail.com>
>> wrote:
>>>>>>>
>>>>>>> Oh, I also adjusted the memory!
>>>>>>>
>>>>>>> Sent from my iPhone
>>>>>>>
>>>>>>>> On Nov 3, 2015, at 6:50 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> Jeff - can you please send another note telling Tony that it turns
>> out
>>>>>>>> it was memory settings :-)
>>>>>>>>
>>>>>>>> He is making fun of me off-list. He should totally do that on-list!
>>>>>>>>
>>>>>>>> Glad you're in business now and sorry for my terrible misdirection.
>>>>>>>>
>>>>>>>> Joe
>>>>>>>>
>>>>>>>>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com>
>> wrote:
>>>>>>>>> Huzzah
>>>>>>>>>
>>>>>>>>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I removed openjdk and installed the Oracle jdk and it now works.
>>>>>>>>>>
>>>>>>>>>> Thanks for the help!!
>>>>>>>>>>
>>>>>>>>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> it is entirely possible that you only have the jre installed.
>> 'yum
>>>>>>>>>>> whatprovides "*/bin/javac"' may tell you packages which you can
>>>>>> install
>>>>>>>>>>> which include a compiler.
>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com>
>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> find / -name javac did not return anything
>>>>>>>>>>>>
>>>>>>>>>>>> I had JAVA_HOME set to
>>>>>>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com>
>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Jeff,
>>>>>>>>>>>>> Were you able to run that find command?
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com>
>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>
>>>>>>
>> ------------------------------------------------------------------------
>>>>>>>>>>>>>> [INFO] Total time: 8.091 s
>>>>>>>>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
>>>>>>>>>>>>>> [INFO] Final Memory: 76M/365M
>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>
>>>>>>
>> ------------------------------------------------------------------------
>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure ->
>>>>>> [Help 1]
>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run
>> Maven
>>>>>> with
>>>>>>>>>> the
>>>>>>>>>>>>>> -e switch.
>>>>>>>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
>>>>>> logging.
>>>>>>>>>>>>>> [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/MojoFailureException
>>>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>>>> [ERROR] After correcting the problems, you can resume the
>> build
>>>>>> with
>>>>>>>>>> the
>>>>>>>>>>>>>> command
>>>>>>>>>>>>>> [ERROR] mvn <goals> -rf :nifi-api
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com>
>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Can you go ahead and try just plain ol'
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I am curious if there is a memory/settings issue that is
>>>>>> manifesting
>>>>>>>>>>>>>>> as an exception during compilation but that it isn't
>> actually a
>>>>>>>>>>>>>>> compilation problem at all...
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j....@gmail.com>
>>>>>> wrote:
>>>>>>>>>>>>>>>> The only other message I see is
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac'
>> from
>>>>>> the
>>>>>>>>>>>>>> environment.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> No worries, it can wait.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com>
>>>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to
>> pull
>>>>>> down
>>>>>>>>>>>>>>>>> centos. Is there anymore that can be found with those
>> stack
>>>>>>>>>> traces .
>>>>>>>>>>>>>>>>> They're not saying much. Your java and maven versions seem
>>>>>> quite
>>>>>>>>>>>> good
>>>>>>>>>>>>>>>>> so need to dig further.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j.007ba7@gmail.com
>>>
>>>>>> wrote:
>>>>>>>>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> [root@localhost nifi]# java -version
>>>>>>>>>>>>>>>>>> openjdk version "1.8.0_65"
>>>>>>>>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>>>>>>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> [root@localhost nifi]# mvn -version
>>>>>>>>>>>>>>>>>> which: no javac in
>>>>>>>>>>
>>>>>>
>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>>>>>>>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set.
>>>>>>>>>>>>>>>>>> Apache Maven 3.3.3
>> (7994120775791599e205a5524ec3e0dfe41d4a06;
>>>>>>>>>>>>>> 2015-04-22T06:57:37-05:00)
>>>>>>>>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3
>>>>>>>>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>>>>>>>>>>>>>>>>> Java home:
>>>>>>>>>>>>>>
>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64",
>> arch:
>>>>>>>>>>>>>> "amd64", family: "unix"
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <joe.witt@gmail.com
>>>
>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do
>> you
>>>>>> get
>>>>>>>>>>>> back?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <
>> j.007ba7@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>> I’m getting the below on a VM. It does build
>> successfully
>>>>>> on my
>>>>>>>>>>>>>> Mac, though.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install
>>>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure ->
>>>>>> [Help 1]
>>>>>>>>>>>>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException:
>>>>>> Failed
>>>>>>>>>> to
>>>>>>>>>>>>>> execute goal
>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>
>>>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>
>>>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>
>>>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>
>>>>>>
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>
>>>>>>
>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>
>>>>>>
>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>>>>>>>>>>>>> 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:1142)
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>
>>>>>>
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>>>>>>>>>>>>> Caused by:
>>>>>>>>>>>>>> org.apache.maven.plugin.compiler.CompilationFailureException:
>>>>>>>>>>>> Compilation
>>>>>>>>>>>>>> failure
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>
>>>>>>
>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>
>>>>>>
>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>
>>>>>>
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>
>>>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>>>>>>>>>>>>> ... 11 more
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>
>>
>>
Re: nifi fails build on CentOS 7
Posted by Aldrin Piri <al...@gmail.com>.
Seems there is in fact an issue with the test cited prior. I received the
following on my Travis CI build on a branch which has the latest of master
merged into it. Unfortunately, it seems that the environment is not the
same as before.
In this case, Travis CI is running with Ubuntu 12.04 LTS [1]. For the
particular build [2], Oracle JDK 7 built without issue, but Oracle JDK 8
exhibited the same problem [3] as reported by Jeff.
NIFI-1145 was created to track this issue [4]
[1]
http://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
[2] https://travis-ci.org/apiri/incubator-nifi/builds/90353191
[3] https://s3.amazonaws.com/archive.travis-ci.org/jobs/90353192/log.txt
[4] https://issues.apache.org/jira/browse/NIFI-1145
On Thu, Nov 5, 2015 at 5:17 PM, Jeff <j....@gmail.com> wrote:
>
>
> I built a new VM CentOS7
>
> I get the below most of the time though last night it did succeeded.
>
> [INFO] nifi-framework-core ................................ FAILURE [02:41
> min]
>
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 08:51 min (Wall Clock)
> [INFO] Finished at: 2015-11-05T16:09:51-06:00
> [INFO] Final Memory: 183M/514M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
> project nifi-framework-core: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
> for the individual test results.
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
> (default-test) on project nifi-framework-core: There are test failures.
>
> Please refer to
> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
> for the individual test results.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
> 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:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
> failures.
>
> Please refer to
> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
> for the individual test results.
> at
> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
> at
> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 11 more
> [ERROR]
>
>
>
>
> > On Nov 4, 2015, at 9:01 AM, Mark Payne <ma...@hotmail.com> wrote:
> >
> > Jeff,
> >
> > I just checked out a fresh build from master, running on CentOS 7 and
> was able to build without any problems.
> > So I don't think it is specifically a problem with CentOS 7. Can you
> provide the output of the unit tests?
> >
> > They should be in
> ${NIFI_SRC_DIR}/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
> >
> > The two files of interest are
> org.apache.nifi.controller.TestStandardFlowFileQueue.txt and
> org.apache.nifi.controller.TestStandardFlowFileQueue-output.txt
> >
> > Thanks!
> > -Mark
> >
> >
> >> On Nov 4, 2015, at 8:53 AM, Jeff <j....@gmail.com> wrote:
> >>
> >> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.916
> sec <<< FAILURE! - in org.apache.nifi.controller.TestStandardFlowFileQueue
> >>
> testDropSwappedFlowFiles(org.apache.nifi.controller.TestStandardFlowFileQueue)
> Time elapsed: 21.825 sec <<< ERROR!
> >> org.junit.runners.model.TestTimedOutException: test timed out after
> 20000 milliseconds
> >> at java.lang.Throwable.fillInStackTrace(Native Method)
> >> at java.lang.Throwable.fillInStackTrace(Throwable.java:783)
> >> at java.lang.Throwable.<init>(Throwable.java:250)
> >> at
> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:24)
> >> at
> org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:19)
> >> at
> org.mockito.internal.invocation.InvocationImpl.<init>(InvocationImpl.java:50)
> >> at
> org.mockito.internal.creation.cglib.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:58)
> >> at
> org.apache.nifi.connectable.Connection$$EnhancerByMockitoWithCGLIB$$8aa704ad.getDestination(<generated>)
> >> at
> org.apache.nifi.controller.StandardFlowFileQueue.put(StandardFlowFileQueue.java:315)
> >> at
> org.apache.nifi.controller.TestStandardFlowFileQueue.testDropSwappedFlowFiles(TestStandardFlowFileQueue.java:169)
> >>
> >>> On Nov 4, 2015, at 7:51 AM, Brandon DeVries <br...@jhu.edu> wrote:
> >>>
> >>> Jeff,
> >>>
> >>> Can you see what tests had failures? Also, if you just want to verify
> that
> >>> your system can do the build, you could do something like "mvn clean
> >>> install -DskipTests". Let us know what you see. Thanks.
> >>>
> >>> Brandon
> >>>
> >>> On Wed, Nov 4, 2015 at 8:46 AM, Jeff <j....@gmail.com> wrote:
> >>>
> >>>>
> >>>> Well, the build got much further with the Oracle JDK but still failed;
> >>>>
> >>>> [INFO]
> >>>>
> ------------------------------------------------------------------------
> >>>> [INFO] BUILD FAILURE
> >>>> [INFO]
> >>>>
> ------------------------------------------------------------------------
> >>>> [INFO] Total time: 07:47 min (Wall Clock)
> >>>> [INFO] Finished at: 2015-11-03T17:07:40-06:00
> >>>> [INFO] Final Memory: 183M/564M
> >>>> [INFO]
> >>>>
> ------------------------------------------------------------------------
> >>>> [ERROR] Failed to execute goal
> >>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test
> (default-test) on
> >>>> project nifi-framework-core: There are test failures.
> >>>> [ERROR]
> >>>> [ERROR] Please refer to
> >>>>
> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
> >>>> for the individual test results.
> >>>>
> >>>>
> >>>>
> >>>>> On Nov 3, 2015, at 6:54 PM, Cerulean Blue <j....@gmail.com>
> wrote:
> >>>>>
> >>>>> Oh, I also adjusted the memory!
> >>>>>
> >>>>> Sent from my iPhone
> >>>>>
> >>>>>> On Nov 3, 2015, at 6:50 PM, Joe Witt <jo...@gmail.com> wrote:
> >>>>>>
> >>>>>> Jeff - can you please send another note telling Tony that it turns
> out
> >>>>>> it was memory settings :-)
> >>>>>>
> >>>>>> He is making fun of me off-list. He should totally do that on-list!
> >>>>>>
> >>>>>> Glad you're in business now and sorry for my terrible misdirection.
> >>>>>>
> >>>>>> Joe
> >>>>>>
> >>>>>>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com>
> wrote:
> >>>>>>> Huzzah
> >>>>>>>
> >>>>>>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> I removed openjdk and installed the Oracle jdk and it now works.
> >>>>>>>>
> >>>>>>>> Thanks for the help!!
> >>>>>>>>
> >>>>>>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com> wrote:
> >>>>>>>>>
> >>>>>>>>> it is entirely possible that you only have the jre installed.
> 'yum
> >>>>>>>>> whatprovides "*/bin/javac"' may tell you packages which you can
> >>>> install
> >>>>>>>>> which include a compiler.
> >>>>>>>>>
> >>>>>>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com>
> wrote:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> find / -name javac did not return anything
> >>>>>>>>>>
> >>>>>>>>>> I had JAVA_HOME set to
> >>>>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com>
> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> Jeff,
> >>>>>>>>>>> Were you able to run that find command?
> >>>>>>>>>>>
> >>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com>
> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> [INFO] BUILD FAILURE
> >>>>>>>>>>>> [INFO]
> >>>>>>>>
> >>>>
> ------------------------------------------------------------------------
> >>>>>>>>>>>> [INFO] Total time: 8.091 s
> >>>>>>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
> >>>>>>>>>>>> [INFO] Final Memory: 76M/365M
> >>>>>>>>>>>> [INFO]
> >>>>>>>>
> >>>>
> ------------------------------------------------------------------------
> >>>>>>>>>>>> [ERROR] Failed to execute goal
> >>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure ->
> >>>> [Help 1]
> >>>>>>>>>>>> [ERROR]
> >>>>>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run
> Maven
> >>>> with
> >>>>>>>> the
> >>>>>>>>>>>> -e switch.
> >>>>>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
> >>>> logging.
> >>>>>>>>>>>> [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/MojoFailureException
> >>>>>>>>>>>> [ERROR]
> >>>>>>>>>>>> [ERROR] After correcting the problems, you can resume the
> build
> >>>> with
> >>>>>>>> the
> >>>>>>>>>>>> command
> >>>>>>>>>>>> [ERROR] mvn <goals> -rf :nifi-api
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com>
> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Can you go ahead and try just plain ol'
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> mvn clean install
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I am curious if there is a memory/settings issue that is
> >>>> manifesting
> >>>>>>>>>>>>> as an exception during compilation but that it isn't
> actually a
> >>>>>>>>>>>>> compilation problem at all...
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j....@gmail.com>
> >>>> wrote:
> >>>>>>>>>>>>>> The only other message I see is
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac'
> from
> >>>> the
> >>>>>>>>>>>> environment.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> No worries, it can wait.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com>
> >>>> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to
> pull
> >>>> down
> >>>>>>>>>>>>>>> centos. Is there anymore that can be found with those
> stack
> >>>>>>>> traces .
> >>>>>>>>>>>>>>> They're not saying much. Your java and maven versions seem
> >>>> quite
> >>>>>>>>>> good
> >>>>>>>>>>>>>>> so need to dig further.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j.007ba7@gmail.com
> >
> >>>> wrote:
> >>>>>>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> [root@localhost nifi]# java -version
> >>>>>>>>>>>>>>>> openjdk version "1.8.0_65"
> >>>>>>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
> >>>>>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> [root@localhost nifi]# mvn -version
> >>>>>>>>>>>>>>>> which: no javac in
> >>>>>>>>
> >>>>
> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
> >>>>>>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set.
> >>>>>>>>>>>>>>>> Apache Maven 3.3.3
> (7994120775791599e205a5524ec3e0dfe41d4a06;
> >>>>>>>>>>>> 2015-04-22T06:57:37-05:00)
> >>>>>>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3
> >>>>>>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
> >>>>>>>>>>>>>>>> Java home:
> >>>>>>>>>>>>
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
> >>>>>>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
> >>>>>>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64",
> arch:
> >>>>>>>>>>>> "amd64", family: "unix"
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <joe.witt@gmail.com
> >
> >>>> wrote:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Jeff
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do
> you
> >>>> get
> >>>>>>>>>> back?
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Thanks
> >>>>>>>>>>>>>>>>> Joe
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <
> j.007ba7@gmail.com>
> >>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>> I’m getting the below on a VM. It does build
> successfully
> >>>> on my
> >>>>>>>>>>>> Mac, though.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install
> >>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
> >>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure ->
> >>>> [Help 1]
> >>>>>>>>>>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException:
> >>>> Failed
> >>>>>>>> to
> >>>>>>>>>>>> execute goal
> >>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
> >>>>>>>>>>>>>>>>>> at
> >>>>>>>>
> >>>>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> >>>>>>>>>>>>>>>>>> at
> >>>>>>>>
> >>>>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> >>>>>>>>>>>>>>>>>> at
> >>>>>>>>
> >>>>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> >>>>>>>>>>>>>>>>>> at
> >>>>>>>>
> >>>>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> >>>>>>>>>>>>>>>>>> at
> >>>>>>>>
> >>>>
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
> >>>>>>>>>>>>>>>>>> at
> >>>>>>>>
> >>>>
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
> >>>>>>>>>>>>>>>>>> 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:1142)
> >>>>>>>>>>>>>>>>>> at
> >>>>>>>>
> >>>>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> >>>>>>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
> >>>>>>>>>>>>>>>>>> Caused by:
> >>>>>>>>>>>> org.apache.maven.plugin.compiler.CompilationFailureException:
> >>>>>>>>>> Compilation
> >>>>>>>>>>>> failure
> >>>>>>>>>>>>>>>>>> at
> >>>>>>>>
> >>>>
> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
> >>>>>>>>>>>>>>>>>> at
> >>>>>>>>
> >>>>
> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
> >>>>>>>>>>>>>>>>>> at
> >>>>>>>>
> >>>>
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> >>>>>>>>>>>>>>>>>> at
> >>>>>>>>
> >>>>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> >>>>>>>>>>>>>>>>>> ... 11 more
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>>>>>> Jeff
> >>>>>>>>
> >>>>>>>>
> >>>>
> >>>>
> >>
> >
>
>
Re: nifi fails build on CentOS 7
Posted by Jeff <j....@gmail.com>.
I built a new VM CentOS7
I get the below most of the time though last night it did succeeded.
[INFO] nifi-framework-core ................................ FAILURE [02:41 min]
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 08:51 min (Wall Clock)
[INFO] Finished at: 2015-11-05T16:09:51-06:00
[INFO] Final Memory: 183M/514M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on project nifi-framework-core: There are test failures.
[ERROR]
[ERROR] Please refer to /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports for the individual test results.
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on project nifi-framework-core: There are test failures.
Please refer to /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports for the individual test results.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
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:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures.
Please refer to /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports for the individual test results.
at org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
at org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:213)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:883)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 11 more
[ERROR]
> On Nov 4, 2015, at 9:01 AM, Mark Payne <ma...@hotmail.com> wrote:
>
> Jeff,
>
> I just checked out a fresh build from master, running on CentOS 7 and was able to build without any problems.
> So I don't think it is specifically a problem with CentOS 7. Can you provide the output of the unit tests?
>
> They should be in ${NIFI_SRC_DIR}/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>
> The two files of interest are org.apache.nifi.controller.TestStandardFlowFileQueue.txt and org.apache.nifi.controller.TestStandardFlowFileQueue-output.txt
>
> Thanks!
> -Mark
>
>
>> On Nov 4, 2015, at 8:53 AM, Jeff <j....@gmail.com> wrote:
>>
>> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.916 sec <<< FAILURE! - in org.apache.nifi.controller.TestStandardFlowFileQueue
>> testDropSwappedFlowFiles(org.apache.nifi.controller.TestStandardFlowFileQueue) Time elapsed: 21.825 sec <<< ERROR!
>> org.junit.runners.model.TestTimedOutException: test timed out after 20000 milliseconds
>> at java.lang.Throwable.fillInStackTrace(Native Method)
>> at java.lang.Throwable.fillInStackTrace(Throwable.java:783)
>> at java.lang.Throwable.<init>(Throwable.java:250)
>> at org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:24)
>> at org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:19)
>> at org.mockito.internal.invocation.InvocationImpl.<init>(InvocationImpl.java:50)
>> at org.mockito.internal.creation.cglib.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:58)
>> at org.apache.nifi.connectable.Connection$$EnhancerByMockitoWithCGLIB$$8aa704ad.getDestination(<generated>)
>> at org.apache.nifi.controller.StandardFlowFileQueue.put(StandardFlowFileQueue.java:315)
>> at org.apache.nifi.controller.TestStandardFlowFileQueue.testDropSwappedFlowFiles(TestStandardFlowFileQueue.java:169)
>>
>>> On Nov 4, 2015, at 7:51 AM, Brandon DeVries <br...@jhu.edu> wrote:
>>>
>>> Jeff,
>>>
>>> Can you see what tests had failures? Also, if you just want to verify that
>>> your system can do the build, you could do something like "mvn clean
>>> install -DskipTests". Let us know what you see. Thanks.
>>>
>>> Brandon
>>>
>>> On Wed, Nov 4, 2015 at 8:46 AM, Jeff <j....@gmail.com> wrote:
>>>
>>>>
>>>> Well, the build got much further with the Oracle JDK but still failed;
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] BUILD FAILURE
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Total time: 07:47 min (Wall Clock)
>>>> [INFO] Finished at: 2015-11-03T17:07:40-06:00
>>>> [INFO] Final Memory: 183M/564M
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [ERROR] Failed to execute goal
>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
>>>> project nifi-framework-core: There are test failures.
>>>> [ERROR]
>>>> [ERROR] Please refer to
>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>> for the individual test results.
>>>>
>>>>
>>>>
>>>>> On Nov 3, 2015, at 6:54 PM, Cerulean Blue <j....@gmail.com> wrote:
>>>>>
>>>>> Oh, I also adjusted the memory!
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>>> On Nov 3, 2015, at 6:50 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>
>>>>>> Jeff - can you please send another note telling Tony that it turns out
>>>>>> it was memory settings :-)
>>>>>>
>>>>>> He is making fun of me off-list. He should totally do that on-list!
>>>>>>
>>>>>> Glad you're in business now and sorry for my terrible misdirection.
>>>>>>
>>>>>> Joe
>>>>>>
>>>>>>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>> Huzzah
>>>>>>>
>>>>>>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> I removed openjdk and installed the Oracle jdk and it now works.
>>>>>>>>
>>>>>>>> Thanks for the help!!
>>>>>>>>
>>>>>>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> it is entirely possible that you only have the jre installed. 'yum
>>>>>>>>> whatprovides "*/bin/javac"' may tell you packages which you can
>>>> install
>>>>>>>>> which include a compiler.
>>>>>>>>>
>>>>>>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> find / -name javac did not return anything
>>>>>>>>>>
>>>>>>>>>> I had JAVA_HOME set to
>>>>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Jeff,
>>>>>>>>>>> Were you able to run that find command?
>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>>> [INFO]
>>>>>>>>
>>>> ------------------------------------------------------------------------
>>>>>>>>>>>> [INFO] Total time: 8.091 s
>>>>>>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
>>>>>>>>>>>> [INFO] Final Memory: 76M/365M
>>>>>>>>>>>> [INFO]
>>>>>>>>
>>>> ------------------------------------------------------------------------
>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure ->
>>>> [Help 1]
>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven
>>>> with
>>>>>>>> the
>>>>>>>>>>>> -e switch.
>>>>>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
>>>> logging.
>>>>>>>>>>>> [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/MojoFailureException
>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>> [ERROR] After correcting the problems, you can resume the build
>>>> with
>>>>>>>> the
>>>>>>>>>>>> command
>>>>>>>>>>>> [ERROR] mvn <goals> -rf :nifi-api
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Can you go ahead and try just plain ol'
>>>>>>>>>>>>>
>>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>>
>>>>>>>>>>>>> I am curious if there is a memory/settings issue that is
>>>> manifesting
>>>>>>>>>>>>> as an exception during compilation but that it isn't actually a
>>>>>>>>>>>>> compilation problem at all...
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j....@gmail.com>
>>>> wrote:
>>>>>>>>>>>>>> The only other message I see is
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac' from
>>>> the
>>>>>>>>>>>> environment.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> No worries, it can wait.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com>
>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to pull
>>>> down
>>>>>>>>>>>>>>> centos. Is there anymore that can be found with those stack
>>>>>>>> traces .
>>>>>>>>>>>>>>> They're not saying much. Your java and maven versions seem
>>>> quite
>>>>>>>>>> good
>>>>>>>>>>>>>>> so need to dig further.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j....@gmail.com>
>>>> wrote:
>>>>>>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [root@localhost nifi]# java -version
>>>>>>>>>>>>>>>> openjdk version "1.8.0_65"
>>>>>>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>>>>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [root@localhost nifi]# mvn -version
>>>>>>>>>>>>>>>> which: no javac in
>>>>>>>>
>>>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>>>>>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set.
>>>>>>>>>>>>>>>> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
>>>>>>>>>>>> 2015-04-22T06:57:37-05:00)
>>>>>>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3
>>>>>>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>>>>>>>>>>>>>>> Java home:
>>>>>>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch:
>>>>>>>>>>>> "amd64", family: "unix"
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <jo...@gmail.com>
>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do you
>>>> get
>>>>>>>>>> back?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>> I’m getting the below on a VM. It does build successfully
>>>> on my
>>>>>>>>>>>> Mac, though.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install
>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure ->
>>>> [Help 1]
>>>>>>>>>>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException:
>>>> Failed
>>>>>>>> to
>>>>>>>>>>>> execute goal
>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>>>>>>>>>>> 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:1142)
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>>>>>>>>>>> Caused by:
>>>>>>>>>>>> org.apache.maven.plugin.compiler.CompilationFailureException:
>>>>>>>>>> Compilation
>>>>>>>>>>>> failure
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>>>>>>>>>>> ... 11 more
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>
>>>>>>>>
>>>>
>>>>
>>
>
Re: nifi fails build on CentOS 7
Posted by Jeff <j....@gmail.com>.
the only items under
.plxarc
classes
generated-sources
generated-test-sources
maven-archiver
maven-shared-archive-resources
maven-status
nifi-framework-core-0.3.1-SNAPSHOT.jar
test-classes
I searched for *FileQueue*.txt but no files found.
I can create a new VM and try again. I do have a few things on this server.
> On Nov 4, 2015, at 9:01 AM, Mark Payne <ma...@hotmail.com> wrote:
>
> Jeff,
>
> I just checked out a fresh build from master, running on CentOS 7 and was able to build without any problems.
> So I don't think it is specifically a problem with CentOS 7. Can you provide the output of the unit tests?
>
> They should be in ${NIFI_SRC_DIR}/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>
> The two files of interest are org.apache.nifi.controller.TestStandardFlowFileQueue.txt and org.apache.nifi.controller.TestStandardFlowFileQueue-output.txt
>
> Thanks!
> -Mark
>
>
>> On Nov 4, 2015, at 8:53 AM, Jeff <j....@gmail.com> wrote:
>>
>> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.916 sec <<< FAILURE! - in org.apache.nifi.controller.TestStandardFlowFileQueue
>> testDropSwappedFlowFiles(org.apache.nifi.controller.TestStandardFlowFileQueue) Time elapsed: 21.825 sec <<< ERROR!
>> org.junit.runners.model.TestTimedOutException: test timed out after 20000 milliseconds
>> at java.lang.Throwable.fillInStackTrace(Native Method)
>> at java.lang.Throwable.fillInStackTrace(Throwable.java:783)
>> at java.lang.Throwable.<init>(Throwable.java:250)
>> at org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:24)
>> at org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:19)
>> at org.mockito.internal.invocation.InvocationImpl.<init>(InvocationImpl.java:50)
>> at org.mockito.internal.creation.cglib.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:58)
>> at org.apache.nifi.connectable.Connection$$EnhancerByMockitoWithCGLIB$$8aa704ad.getDestination(<generated>)
>> at org.apache.nifi.controller.StandardFlowFileQueue.put(StandardFlowFileQueue.java:315)
>> at org.apache.nifi.controller.TestStandardFlowFileQueue.testDropSwappedFlowFiles(TestStandardFlowFileQueue.java:169)
>>
>>> On Nov 4, 2015, at 7:51 AM, Brandon DeVries <br...@jhu.edu> wrote:
>>>
>>> Jeff,
>>>
>>> Can you see what tests had failures? Also, if you just want to verify that
>>> your system can do the build, you could do something like "mvn clean
>>> install -DskipTests". Let us know what you see. Thanks.
>>>
>>> Brandon
>>>
>>> On Wed, Nov 4, 2015 at 8:46 AM, Jeff <j....@gmail.com> wrote:
>>>
>>>>
>>>> Well, the build got much further with the Oracle JDK but still failed;
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] BUILD FAILURE
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Total time: 07:47 min (Wall Clock)
>>>> [INFO] Finished at: 2015-11-03T17:07:40-06:00
>>>> [INFO] Final Memory: 183M/564M
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [ERROR] Failed to execute goal
>>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
>>>> project nifi-framework-core: There are test failures.
>>>> [ERROR]
>>>> [ERROR] Please refer to
>>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>>> for the individual test results.
>>>>
>>>>
>>>>
>>>>> On Nov 3, 2015, at 6:54 PM, Cerulean Blue <j....@gmail.com> wrote:
>>>>>
>>>>> Oh, I also adjusted the memory!
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>>> On Nov 3, 2015, at 6:50 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>
>>>>>> Jeff - can you please send another note telling Tony that it turns out
>>>>>> it was memory settings :-)
>>>>>>
>>>>>> He is making fun of me off-list. He should totally do that on-list!
>>>>>>
>>>>>> Glad you're in business now and sorry for my terrible misdirection.
>>>>>>
>>>>>> Joe
>>>>>>
>>>>>>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>> Huzzah
>>>>>>>
>>>>>>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> I removed openjdk and installed the Oracle jdk and it now works.
>>>>>>>>
>>>>>>>> Thanks for the help!!
>>>>>>>>
>>>>>>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> it is entirely possible that you only have the jre installed. 'yum
>>>>>>>>> whatprovides "*/bin/javac"' may tell you packages which you can
>>>> install
>>>>>>>>> which include a compiler.
>>>>>>>>>
>>>>>>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> find / -name javac did not return anything
>>>>>>>>>>
>>>>>>>>>> I had JAVA_HOME set to
>>>>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Jeff,
>>>>>>>>>>> Were you able to run that find command?
>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>>> [INFO]
>>>>>>>>
>>>> ------------------------------------------------------------------------
>>>>>>>>>>>> [INFO] Total time: 8.091 s
>>>>>>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
>>>>>>>>>>>> [INFO] Final Memory: 76M/365M
>>>>>>>>>>>> [INFO]
>>>>>>>>
>>>> ------------------------------------------------------------------------
>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure ->
>>>> [Help 1]
>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven
>>>> with
>>>>>>>> the
>>>>>>>>>>>> -e switch.
>>>>>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
>>>> logging.
>>>>>>>>>>>> [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/MojoFailureException
>>>>>>>>>>>> [ERROR]
>>>>>>>>>>>> [ERROR] After correcting the problems, you can resume the build
>>>> with
>>>>>>>> the
>>>>>>>>>>>> command
>>>>>>>>>>>> [ERROR] mvn <goals> -rf :nifi-api
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Can you go ahead and try just plain ol'
>>>>>>>>>>>>>
>>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>>
>>>>>>>>>>>>> I am curious if there is a memory/settings issue that is
>>>> manifesting
>>>>>>>>>>>>> as an exception during compilation but that it isn't actually a
>>>>>>>>>>>>> compilation problem at all...
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j....@gmail.com>
>>>> wrote:
>>>>>>>>>>>>>> The only other message I see is
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac' from
>>>> the
>>>>>>>>>>>> environment.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> No worries, it can wait.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com>
>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to pull
>>>> down
>>>>>>>>>>>>>>> centos. Is there anymore that can be found with those stack
>>>>>>>> traces .
>>>>>>>>>>>>>>> They're not saying much. Your java and maven versions seem
>>>> quite
>>>>>>>>>> good
>>>>>>>>>>>>>>> so need to dig further.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j....@gmail.com>
>>>> wrote:
>>>>>>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [root@localhost nifi]# java -version
>>>>>>>>>>>>>>>> openjdk version "1.8.0_65"
>>>>>>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>>>>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [root@localhost nifi]# mvn -version
>>>>>>>>>>>>>>>> which: no javac in
>>>>>>>>
>>>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>>>>>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set.
>>>>>>>>>>>>>>>> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
>>>>>>>>>>>> 2015-04-22T06:57:37-05:00)
>>>>>>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3
>>>>>>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>>>>>>>>>>>>>>> Java home:
>>>>>>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch:
>>>>>>>>>>>> "amd64", family: "unix"
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <jo...@gmail.com>
>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do you
>>>> get
>>>>>>>>>> back?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>> I’m getting the below on a VM. It does build successfully
>>>> on my
>>>>>>>>>>>> Mac, though.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install
>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure ->
>>>> [Help 1]
>>>>>>>>>>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException:
>>>> Failed
>>>>>>>> to
>>>>>>>>>>>> execute goal
>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>>>>>>>>>>> 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:1142)
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>>>>>>>>>>> Caused by:
>>>>>>>>>>>> org.apache.maven.plugin.compiler.CompilationFailureException:
>>>>>>>>>> Compilation
>>>>>>>>>>>> failure
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>>>>>>>>>>> at
>>>>>>>>
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>>>>>>>>>>> ... 11 more
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>> Jeff
>>>>>>>>
>>>>>>>>
>>>>
>>>>
>>
>
Re: nifi fails build on CentOS 7
Posted by Mark Payne <ma...@hotmail.com>.
Jeff,
I just checked out a fresh build from master, running on CentOS 7 and was able to build without any problems.
So I don't think it is specifically a problem with CentOS 7. Can you provide the output of the unit tests?
They should be in ${NIFI_SRC_DIR}/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
The two files of interest are org.apache.nifi.controller.TestStandardFlowFileQueue.txt and org.apache.nifi.controller.TestStandardFlowFileQueue-output.txt
Thanks!
-Mark
> On Nov 4, 2015, at 8:53 AM, Jeff <j....@gmail.com> wrote:
>
> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.916 sec <<< FAILURE! - in org.apache.nifi.controller.TestStandardFlowFileQueue
> testDropSwappedFlowFiles(org.apache.nifi.controller.TestStandardFlowFileQueue) Time elapsed: 21.825 sec <<< ERROR!
> org.junit.runners.model.TestTimedOutException: test timed out after 20000 milliseconds
> at java.lang.Throwable.fillInStackTrace(Native Method)
> at java.lang.Throwable.fillInStackTrace(Throwable.java:783)
> at java.lang.Throwable.<init>(Throwable.java:250)
> at org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:24)
> at org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:19)
> at org.mockito.internal.invocation.InvocationImpl.<init>(InvocationImpl.java:50)
> at org.mockito.internal.creation.cglib.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:58)
> at org.apache.nifi.connectable.Connection$$EnhancerByMockitoWithCGLIB$$8aa704ad.getDestination(<generated>)
> at org.apache.nifi.controller.StandardFlowFileQueue.put(StandardFlowFileQueue.java:315)
> at org.apache.nifi.controller.TestStandardFlowFileQueue.testDropSwappedFlowFiles(TestStandardFlowFileQueue.java:169)
>
>> On Nov 4, 2015, at 7:51 AM, Brandon DeVries <br...@jhu.edu> wrote:
>>
>> Jeff,
>>
>> Can you see what tests had failures? Also, if you just want to verify that
>> your system can do the build, you could do something like "mvn clean
>> install -DskipTests". Let us know what you see. Thanks.
>>
>> Brandon
>>
>> On Wed, Nov 4, 2015 at 8:46 AM, Jeff <j....@gmail.com> wrote:
>>
>>>
>>> Well, the build got much further with the Oracle JDK but still failed;
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Total time: 07:47 min (Wall Clock)
>>> [INFO] Finished at: 2015-11-03T17:07:40-06:00
>>> [INFO] Final Memory: 183M/564M
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
>>> project nifi-framework-core: There are test failures.
>>> [ERROR]
>>> [ERROR] Please refer to
>>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>>> for the individual test results.
>>>
>>>
>>>
>>>> On Nov 3, 2015, at 6:54 PM, Cerulean Blue <j....@gmail.com> wrote:
>>>>
>>>> Oh, I also adjusted the memory!
>>>>
>>>> Sent from my iPhone
>>>>
>>>>> On Nov 3, 2015, at 6:50 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>
>>>>> Jeff - can you please send another note telling Tony that it turns out
>>>>> it was memory settings :-)
>>>>>
>>>>> He is making fun of me off-list. He should totally do that on-list!
>>>>>
>>>>> Glad you're in business now and sorry for my terrible misdirection.
>>>>>
>>>>> Joe
>>>>>
>>>>>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>> Huzzah
>>>>>>
>>>>>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>
>>>>>>>
>>>>>>> I removed openjdk and installed the Oracle jdk and it now works.
>>>>>>>
>>>>>>> Thanks for the help!!
>>>>>>>
>>>>>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> it is entirely possible that you only have the jre installed. 'yum
>>>>>>>> whatprovides "*/bin/javac"' may tell you packages which you can
>>> install
>>>>>>>> which include a compiler.
>>>>>>>>
>>>>>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> find / -name javac did not return anything
>>>>>>>>>
>>>>>>>>> I had JAVA_HOME set to
>>>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Jeff,
>>>>>>>>>> Were you able to run that find command?
>>>>>>>>>>
>>>>>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>> [INFO]
>>>>>>>
>>> ------------------------------------------------------------------------
>>>>>>>>>>> [INFO] Total time: 8.091 s
>>>>>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
>>>>>>>>>>> [INFO] Final Memory: 76M/365M
>>>>>>>>>>> [INFO]
>>>>>>>
>>> ------------------------------------------------------------------------
>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure ->
>>> [Help 1]
>>>>>>>>>>> [ERROR]
>>>>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven
>>> with
>>>>>>> the
>>>>>>>>>>> -e switch.
>>>>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
>>> logging.
>>>>>>>>>>> [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/MojoFailureException
>>>>>>>>>>> [ERROR]
>>>>>>>>>>> [ERROR] After correcting the problems, you can resume the build
>>> with
>>>>>>> the
>>>>>>>>>>> command
>>>>>>>>>>> [ERROR] mvn <goals> -rf :nifi-api
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Can you go ahead and try just plain ol'
>>>>>>>>>>>>
>>>>>>>>>>>> mvn clean install
>>>>>>>>>>>>
>>>>>>>>>>>> I am curious if there is a memory/settings issue that is
>>> manifesting
>>>>>>>>>>>> as an exception during compilation but that it isn't actually a
>>>>>>>>>>>> compilation problem at all...
>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j....@gmail.com>
>>> wrote:
>>>>>>>>>>>>> The only other message I see is
>>>>>>>>>>>>>
>>>>>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac' from
>>> the
>>>>>>>>>>> environment.
>>>>>>>>>>>>>
>>>>>>>>>>>>> No worries, it can wait.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com>
>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to pull
>>> down
>>>>>>>>>>>>>> centos. Is there anymore that can be found with those stack
>>>>>>> traces .
>>>>>>>>>>>>>> They're not saying much. Your java and maven versions seem
>>> quite
>>>>>>>>> good
>>>>>>>>>>>>>> so need to dig further.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j....@gmail.com>
>>> wrote:
>>>>>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [root@localhost nifi]# java -version
>>>>>>>>>>>>>>> openjdk version "1.8.0_65"
>>>>>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>>>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [root@localhost nifi]# mvn -version
>>>>>>>>>>>>>>> which: no javac in
>>>>>>>
>>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>>>>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set.
>>>>>>>>>>>>>>> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
>>>>>>>>>>> 2015-04-22T06:57:37-05:00)
>>>>>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3
>>>>>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>>>>>>>>>>>>>> Java home:
>>>>>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch:
>>>>>>>>>>> "amd64", family: "unix"
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <jo...@gmail.com>
>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do you
>>> get
>>>>>>>>> back?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com>
>>>>>>> wrote:
>>>>>>>>>>>>>>>>> I’m getting the below on a VM. It does build successfully
>>> on my
>>>>>>>>>>> Mac, though.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install
>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure ->
>>> [Help 1]
>>>>>>>>>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException:
>>> Failed
>>>>>>> to
>>>>>>>>>>> execute goal
>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>>>>>>>>>>> at
>>>>>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>>>>>>>>>> at
>>>>>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>>>>>>>>>> at
>>>>>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>>>>>>>>>> at
>>>>>>>
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>>>>>>>>>> at
>>>>>>>
>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>>>>>>>>>> at
>>>>>>>
>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>>>>>>>>>> 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:1142)
>>>>>>>>>>>>>>>>> at
>>>>>>>
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>>>>>>>>>> Caused by:
>>>>>>>>>>> org.apache.maven.plugin.compiler.CompilationFailureException:
>>>>>>>>> Compilation
>>>>>>>>>>> failure
>>>>>>>>>>>>>>>>> at
>>>>>>>
>>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>>>>>>>>>>>>>> at
>>>>>>>
>>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>>>>>>>>>>>>>> at
>>>>>>>
>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>>>>>>>>>> at
>>>>>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>>>>>>>>>> ... 11 more
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>> Jeff
>>>>>>>
>>>>>>>
>>>
>>>
>
Re: nifi fails build on CentOS 7
Posted by Jeff <j....@gmail.com>.
Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 28.916 sec <<< FAILURE! - in org.apache.nifi.controller.TestStandardFlowFileQueue
testDropSwappedFlowFiles(org.apache.nifi.controller.TestStandardFlowFileQueue) Time elapsed: 21.825 sec <<< ERROR!
org.junit.runners.model.TestTimedOutException: test timed out after 20000 milliseconds
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Throwable.java:783)
at java.lang.Throwable.<init>(Throwable.java:250)
at org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:24)
at org.mockito.internal.debugging.LocationImpl.<init>(LocationImpl.java:19)
at org.mockito.internal.invocation.InvocationImpl.<init>(InvocationImpl.java:50)
at org.mockito.internal.creation.cglib.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:58)
at org.apache.nifi.connectable.Connection$$EnhancerByMockitoWithCGLIB$$8aa704ad.getDestination(<generated>)
at org.apache.nifi.controller.StandardFlowFileQueue.put(StandardFlowFileQueue.java:315)
at org.apache.nifi.controller.TestStandardFlowFileQueue.testDropSwappedFlowFiles(TestStandardFlowFileQueue.java:169)
> On Nov 4, 2015, at 7:51 AM, Brandon DeVries <br...@jhu.edu> wrote:
>
> Jeff,
>
> Can you see what tests had failures? Also, if you just want to verify that
> your system can do the build, you could do something like "mvn clean
> install -DskipTests". Let us know what you see. Thanks.
>
> Brandon
>
> On Wed, Nov 4, 2015 at 8:46 AM, Jeff <j....@gmail.com> wrote:
>
>>
>> Well, the build got much further with the Oracle JDK but still failed;
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 07:47 min (Wall Clock)
>> [INFO] Finished at: 2015-11-03T17:07:40-06:00
>> [INFO] Final Memory: 183M/564M
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
>> project nifi-framework-core: There are test failures.
>> [ERROR]
>> [ERROR] Please refer to
>> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
>> for the individual test results.
>>
>>
>>
>>> On Nov 3, 2015, at 6:54 PM, Cerulean Blue <j....@gmail.com> wrote:
>>>
>>> Oh, I also adjusted the memory!
>>>
>>> Sent from my iPhone
>>>
>>>> On Nov 3, 2015, at 6:50 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>
>>>> Jeff - can you please send another note telling Tony that it turns out
>>>> it was memory settings :-)
>>>>
>>>> He is making fun of me off-list. He should totally do that on-list!
>>>>
>>>> Glad you're in business now and sorry for my terrible misdirection.
>>>>
>>>> Joe
>>>>
>>>>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com> wrote:
>>>>> Huzzah
>>>>>
>>>>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>> I removed openjdk and installed the Oracle jdk and it now works.
>>>>>>
>>>>>> Thanks for the help!!
>>>>>>
>>>>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>>
>>>>>>> it is entirely possible that you only have the jre installed. 'yum
>>>>>>> whatprovides "*/bin/javac"' may tell you packages which you can
>> install
>>>>>>> which include a compiler.
>>>>>>>
>>>>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> find / -name javac did not return anything
>>>>>>>>
>>>>>>>> I had JAVA_HOME set to
>>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Jeff,
>>>>>>>>> Were you able to run that find command?
>>>>>>>>>
>>>>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>> [INFO]
>>>>>>
>> ------------------------------------------------------------------------
>>>>>>>>>> [INFO] Total time: 8.091 s
>>>>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
>>>>>>>>>> [INFO] Final Memory: 76M/365M
>>>>>>>>>> [INFO]
>>>>>>
>> ------------------------------------------------------------------------
>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure ->
>> [Help 1]
>>>>>>>>>> [ERROR]
>>>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven
>> with
>>>>>> the
>>>>>>>>>> -e switch.
>>>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
>> logging.
>>>>>>>>>> [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/MojoFailureException
>>>>>>>>>> [ERROR]
>>>>>>>>>> [ERROR] After correcting the problems, you can resume the build
>> with
>>>>>> the
>>>>>>>>>> command
>>>>>>>>>> [ERROR] mvn <goals> -rf :nifi-api
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Can you go ahead and try just plain ol'
>>>>>>>>>>>
>>>>>>>>>>> mvn clean install
>>>>>>>>>>>
>>>>>>>>>>> I am curious if there is a memory/settings issue that is
>> manifesting
>>>>>>>>>>> as an exception during compilation but that it isn't actually a
>>>>>>>>>>> compilation problem at all...
>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j....@gmail.com>
>> wrote:
>>>>>>>>>>>> The only other message I see is
>>>>>>>>>>>>
>>>>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac' from
>> the
>>>>>>>>>> environment.
>>>>>>>>>>>>
>>>>>>>>>>>> No worries, it can wait.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>
>>>>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com>
>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to pull
>> down
>>>>>>>>>>>>> centos. Is there anymore that can be found with those stack
>>>>>> traces .
>>>>>>>>>>>>> They're not saying much. Your java and maven versions seem
>> quite
>>>>>>>> good
>>>>>>>>>>>>> so need to dig further.
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j....@gmail.com>
>> wrote:
>>>>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [root@localhost nifi]# java -version
>>>>>>>>>>>>>> openjdk version "1.8.0_65"
>>>>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [root@localhost nifi]# mvn -version
>>>>>>>>>>>>>> which: no javac in
>>>>>>
>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>>>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set.
>>>>>>>>>>>>>> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
>>>>>>>>>> 2015-04-22T06:57:37-05:00)
>>>>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3
>>>>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>>>>>>>>>>>>> Java home:
>>>>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch:
>>>>>>>>>> "amd64", family: "unix"
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <jo...@gmail.com>
>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do you
>> get
>>>>>>>> back?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com>
>>>>>> wrote:
>>>>>>>>>>>>>>>> I’m getting the below on a VM. It does build successfully
>> on my
>>>>>>>>>> Mac, though.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install
>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure ->
>> [Help 1]
>>>>>>>>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException:
>> Failed
>>>>>> to
>>>>>>>>>> execute goal
>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>>>>>>>>>> at
>>>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>>>>>>>>> at
>>>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>>>>>>>>> at
>>>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>>>>>>>>> at
>>>>>>
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>>>>>>>>> at
>>>>>>
>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>>>>>>>>> at
>>>>>>
>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>>>>>>>>> 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:1142)
>>>>>>>>>>>>>>>> at
>>>>>>
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>>>>>>>>> Caused by:
>>>>>>>>>> org.apache.maven.plugin.compiler.CompilationFailureException:
>>>>>>>> Compilation
>>>>>>>>>> failure
>>>>>>>>>>>>>>>> at
>>>>>>
>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>>>>>>>>>>>>> at
>>>>>>
>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>>>>>>>>>>>>> at
>>>>>>
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>>>>>>>>> at
>>>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>>>>>>>>> ... 11 more
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>> Jeff
>>>>>>
>>>>>>
>>
>>
Re: nifi fails build on CentOS 7
Posted by Jeff <j....@gmail.com>.
Yes, the build succeeded using;
mvn clean install -DskipTests
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 07:27 min
[INFO] Finished at: 2015-11-04T02:02:57-06:00
[INFO] Final Memory: 197M/566M
[INFO] ------------------------------------------------------------------------
> On Nov 4, 2015, at 7:51 AM, Brandon DeVries <br...@jhu.edu> wrote:
>
> mvn clean
> install -DskipTests
Re: nifi fails build on CentOS 7
Posted by Brandon DeVries <br...@jhu.edu>.
Jeff,
Can you see what tests had failures? Also, if you just want to verify that
your system can do the build, you could do something like "mvn clean
install -DskipTests". Let us know what you see. Thanks.
Brandon
On Wed, Nov 4, 2015 at 8:46 AM, Jeff <j....@gmail.com> wrote:
>
> Well, the build got much further with the Oracle JDK but still failed;
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 07:47 min (Wall Clock)
> [INFO] Finished at: 2015-11-03T17:07:40-06:00
> [INFO] Final Memory: 183M/564M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
> project nifi-framework-core: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports
> for the individual test results.
>
>
>
> > On Nov 3, 2015, at 6:54 PM, Cerulean Blue <j....@gmail.com> wrote:
> >
> > Oh, I also adjusted the memory!
> >
> > Sent from my iPhone
> >
> >> On Nov 3, 2015, at 6:50 PM, Joe Witt <jo...@gmail.com> wrote:
> >>
> >> Jeff - can you please send another note telling Tony that it turns out
> >> it was memory settings :-)
> >>
> >> He is making fun of me off-list. He should totally do that on-list!
> >>
> >> Glad you're in business now and sorry for my terrible misdirection.
> >>
> >> Joe
> >>
> >>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com> wrote:
> >>> Huzzah
> >>>
> >>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com> wrote:
> >>>>
> >>>>
> >>>> I removed openjdk and installed the Oracle jdk and it now works.
> >>>>
> >>>> Thanks for the help!!
> >>>>
> >>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com> wrote:
> >>>>>
> >>>>> it is entirely possible that you only have the jre installed. 'yum
> >>>>> whatprovides "*/bin/javac"' may tell you packages which you can
> install
> >>>>> which include a compiler.
> >>>>>
> >>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com> wrote:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> find / -name javac did not return anything
> >>>>>>
> >>>>>> I had JAVA_HOME set to
> >>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com> wrote:
> >>>>>>>
> >>>>>>> Jeff,
> >>>>>>> Were you able to run that find command?
> >>>>>>>
> >>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> [INFO] BUILD FAILURE
> >>>>>>>> [INFO]
> >>>>
> ------------------------------------------------------------------------
> >>>>>>>> [INFO] Total time: 8.091 s
> >>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
> >>>>>>>> [INFO] Final Memory: 76M/365M
> >>>>>>>> [INFO]
> >>>>
> ------------------------------------------------------------------------
> >>>>>>>> [ERROR] Failed to execute goal
> >>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >>>>>>>> (default-compile) on project nifi-api: Compilation failure ->
> [Help 1]
> >>>>>>>> [ERROR]
> >>>>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven
> with
> >>>> the
> >>>>>>>> -e switch.
> >>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
> logging.
> >>>>>>>> [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/MojoFailureException
> >>>>>>>> [ERROR]
> >>>>>>>> [ERROR] After correcting the problems, you can resume the build
> with
> >>>> the
> >>>>>>>> command
> >>>>>>>> [ERROR] mvn <goals> -rf :nifi-api
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com> wrote:
> >>>>>>>>>
> >>>>>>>>> Can you go ahead and try just plain ol'
> >>>>>>>>>
> >>>>>>>>> mvn clean install
> >>>>>>>>>
> >>>>>>>>> I am curious if there is a memory/settings issue that is
> manifesting
> >>>>>>>>> as an exception during compilation but that it isn't actually a
> >>>>>>>>> compilation problem at all...
> >>>>>>>>>
> >>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j....@gmail.com>
> wrote:
> >>>>>>>>>> The only other message I see is
> >>>>>>>>>>
> >>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac' from
> the
> >>>>>>>> environment.
> >>>>>>>>>>
> >>>>>>>>>> No worries, it can wait.
> >>>>>>>>>>
> >>>>>>>>>> Thanks,
> >>>>>>>>>>
> >>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com>
> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to pull
> down
> >>>>>>>>>>> centos. Is there anymore that can be found with those stack
> >>>> traces .
> >>>>>>>>>>> They're not saying much. Your java and maven versions seem
> quite
> >>>>>> good
> >>>>>>>>>>> so need to dig further.
> >>>>>>>>>>>
> >>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j....@gmail.com>
> wrote:
> >>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
> >>>>>>>>>>>>
> >>>>>>>>>>>> [root@localhost nifi]# java -version
> >>>>>>>>>>>> openjdk version "1.8.0_65"
> >>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
> >>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> [root@localhost nifi]# mvn -version
> >>>>>>>>>>>> which: no javac in
> >>>>
> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
> >>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set.
> >>>>>>>>>>>> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
> >>>>>>>> 2015-04-22T06:57:37-05:00)
> >>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3
> >>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
> >>>>>>>>>>>> Java home:
> >>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
> >>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
> >>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch:
> >>>>>>>> "amd64", family: "unix"
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <jo...@gmail.com>
> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Jeff
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do you
> get
> >>>>>> back?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Thanks
> >>>>>>>>>>>>> Joe
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com>
> >>>> wrote:
> >>>>>>>>>>>>>> I’m getting the below on a VM. It does build successfully
> on my
> >>>>>>>> Mac, though.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install
> >>>>>>>>>>>>>> [ERROR] Failed to execute goal
> >>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >>>>>>>> (default-compile) on project nifi-api: Compilation failure ->
> [Help 1]
> >>>>>>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException:
> Failed
> >>>> to
> >>>>>>>> execute goal
> >>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >>>>>>>> (default-compile) on project nifi-api: Compilation failure
> >>>>>>>>>>>>>> at
> >>>>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> >>>>>>>>>>>>>> at
> >>>>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> >>>>>>>>>>>>>> at
> >>>>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> >>>>>>>>>>>>>> at
> >>>>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> >>>>>>>>>>>>>> at
> >>>>
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
> >>>>>>>>>>>>>> at
> >>>>
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
> >>>>>>>>>>>>>> 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:1142)
> >>>>>>>>>>>>>> at
> >>>>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> >>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
> >>>>>>>>>>>>>> Caused by:
> >>>>>>>> org.apache.maven.plugin.compiler.CompilationFailureException:
> >>>>>> Compilation
> >>>>>>>> failure
> >>>>>>>>>>>>>> at
> >>>>
> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
> >>>>>>>>>>>>>> at
> >>>>
> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
> >>>>>>>>>>>>>> at
> >>>>
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> >>>>>>>>>>>>>> at
> >>>>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> >>>>>>>>>>>>>> ... 11 more
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>> Jeff
> >>>>
> >>>>
>
>
Re: nifi fails build on CentOS 7
Posted by Jeff <j....@gmail.com>.
Well, the build got much further with the Oracle JDK but still failed;
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 07:47 min (Wall Clock)
[INFO] Finished at: 2015-11-03T17:07:40-06:00
[INFO] Final Memory: 183M/564M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on project nifi-framework-core: There are test failures.
[ERROR]
[ERROR] Please refer to /root/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/target/surefire-reports for the individual test results.
> On Nov 3, 2015, at 6:54 PM, Cerulean Blue <j....@gmail.com> wrote:
>
> Oh, I also adjusted the memory!
>
> Sent from my iPhone
>
>> On Nov 3, 2015, at 6:50 PM, Joe Witt <jo...@gmail.com> wrote:
>>
>> Jeff - can you please send another note telling Tony that it turns out
>> it was memory settings :-)
>>
>> He is making fun of me off-list. He should totally do that on-list!
>>
>> Glad you're in business now and sorry for my terrible misdirection.
>>
>> Joe
>>
>>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com> wrote:
>>> Huzzah
>>>
>>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com> wrote:
>>>>
>>>>
>>>> I removed openjdk and installed the Oracle jdk and it now works.
>>>>
>>>> Thanks for the help!!
>>>>
>>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>
>>>>> it is entirely possible that you only have the jre installed. 'yum
>>>>> whatprovides "*/bin/javac"' may tell you packages which you can install
>>>>> which include a compiler.
>>>>>
>>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> find / -name javac did not return anything
>>>>>>
>>>>>> I had JAVA_HOME set to
>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>>
>>>>>>> Jeff,
>>>>>>> Were you able to run that find command?
>>>>>>>
>>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>>>>> [INFO] Total time: 8.091 s
>>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
>>>>>>>> [INFO] Final Memory: 76M/365M
>>>>>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>> (default-compile) on project nifi-api: Compilation failure -> [Help 1]
>>>>>>>> [ERROR]
>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>>>> the
>>>>>>>> -e switch.
>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>>>>>>> [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/MojoFailureException
>>>>>>>> [ERROR]
>>>>>>>> [ERROR] After correcting the problems, you can resume the build with
>>>> the
>>>>>>>> command
>>>>>>>> [ERROR] mvn <goals> -rf :nifi-api
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Can you go ahead and try just plain ol'
>>>>>>>>>
>>>>>>>>> mvn clean install
>>>>>>>>>
>>>>>>>>> I am curious if there is a memory/settings issue that is manifesting
>>>>>>>>> as an exception during compilation but that it isn't actually a
>>>>>>>>> compilation problem at all...
>>>>>>>>>
>>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>> The only other message I see is
>>>>>>>>>>
>>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac' from the
>>>>>>>> environment.
>>>>>>>>>>
>>>>>>>>>> No worries, it can wait.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to pull down
>>>>>>>>>>> centos. Is there anymore that can be found with those stack
>>>> traces .
>>>>>>>>>>> They're not saying much. Your java and maven versions seem quite
>>>>>> good
>>>>>>>>>>> so need to dig further.
>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>>>>>>>>>>
>>>>>>>>>>>> [root@localhost nifi]# java -version
>>>>>>>>>>>> openjdk version "1.8.0_65"
>>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> [root@localhost nifi]# mvn -version
>>>>>>>>>>>> which: no javac in
>>>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set.
>>>>>>>>>>>> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
>>>>>>>> 2015-04-22T06:57:37-05:00)
>>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3
>>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>>>>>>>>>>> Java home:
>>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch:
>>>>>>>> "amd64", family: "unix"
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Jeff
>>>>>>>>>>>>>
>>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do you get
>>>>>> back?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>> Joe
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com>
>>>> wrote:
>>>>>>>>>>>>>> I’m getting the below on a VM. It does build successfully on my
>>>>>>>> Mac, though.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install
>>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>> (default-compile) on project nifi-api: Compilation failure -> [Help 1]
>>>>>>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed
>>>> to
>>>>>>>> execute goal
>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>>>>>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>>>>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>>>>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>>>>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>>>>>>> at
>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>>>>>>> at
>>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>>>>>>> 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:1142)
>>>>>>>>>>>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>>>>>>> Caused by:
>>>>>>>> org.apache.maven.plugin.compiler.CompilationFailureException:
>>>>>> Compilation
>>>>>>>> failure
>>>>>>>>>>>>>> at
>>>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>>>>>>>>>>> at
>>>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>>>>>>>>>>> at
>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>>>>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>>>>>>> ... 11 more
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>> Jeff
>>>>
>>>>
Re: nifi fails build on CentOS 7
Posted by Cerulean Blue <j....@gmail.com>.
Oh, I also adjusted the memory!
Sent from my iPhone
> On Nov 3, 2015, at 6:50 PM, Joe Witt <jo...@gmail.com> wrote:
>
> Jeff - can you please send another note telling Tony that it turns out
> it was memory settings :-)
>
> He is making fun of me off-list. He should totally do that on-list!
>
> Glad you're in business now and sorry for my terrible misdirection.
>
> Joe
>
>> On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com> wrote:
>> Huzzah
>>
>>> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com> wrote:
>>>
>>>
>>> I removed openjdk and installed the Oracle jdk and it now works.
>>>
>>> Thanks for the help!!
>>>
>>>> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>>
>>>> it is entirely possible that you only have the jre installed. 'yum
>>>> whatprovides "*/bin/javac"' may tell you packages which you can install
>>>> which include a compiler.
>>>>
>>>>> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com> wrote:
>>>>>
>>>>>
>>>>>
>>>>> find / -name javac did not return anything
>>>>>
>>>>> I had JAVA_HOME set to
>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>
>>>>>
>>>>>
>>>>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>
>>>>>> Jeff,
>>>>>> Were you able to run that find command?
>>>>>>
>>>>>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>
>>>>>>>
>>>>>>> [INFO] BUILD FAILURE
>>>>>>> [INFO]
>>> ------------------------------------------------------------------------
>>>>>>> [INFO] Total time: 8.091 s
>>>>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
>>>>>>> [INFO] Final Memory: 76M/365M
>>>>>>> [INFO]
>>> ------------------------------------------------------------------------
>>>>>>> [ERROR] Failed to execute goal
>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>> (default-compile) on project nifi-api: Compilation failure -> [Help 1]
>>>>>>> [ERROR]
>>>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>>> the
>>>>>>> -e switch.
>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>>>>>> [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/MojoFailureException
>>>>>>> [ERROR]
>>>>>>> [ERROR] After correcting the problems, you can resume the build with
>>> the
>>>>>>> command
>>>>>>> [ERROR] mvn <goals> -rf :nifi-api
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> Can you go ahead and try just plain ol'
>>>>>>>>
>>>>>>>> mvn clean install
>>>>>>>>
>>>>>>>> I am curious if there is a memory/settings issue that is manifesting
>>>>>>>> as an exception during compilation but that it isn't actually a
>>>>>>>> compilation problem at all...
>>>>>>>>
>>>>>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j....@gmail.com> wrote:
>>>>>>>>> The only other message I see is
>>>>>>>>>
>>>>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac' from the
>>>>>>> environment.
>>>>>>>>>
>>>>>>>>> No worries, it can wait.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>> if i weren't on horrible hotel wifi right now i'd try to pull down
>>>>>>>>>> centos. Is there anymore that can be found with those stack
>>> traces .
>>>>>>>>>> They're not saying much. Your java and maven versions seem quite
>>>>> good
>>>>>>>>>> so need to dig further.
>>>>>>>>>>
>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>>>>>>>>>
>>>>>>>>>>> [root@localhost nifi]# java -version
>>>>>>>>>>> openjdk version "1.8.0_65"
>>>>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> [root@localhost nifi]# mvn -version
>>>>>>>>>>> which: no javac in
>>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>>>>>>>>>> Warning: JAVA_HOME environment variable is not set.
>>>>>>>>>>> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
>>>>>>> 2015-04-22T06:57:37-05:00)
>>>>>>>>>>> Maven home: /opt/apache-maven-3.3.3
>>>>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>>>>>>>>>> Java home:
>>>>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch:
>>>>>>> "amd64", family: "unix"
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Jeff
>>>>>>>>>>>>
>>>>>>>>>>>> When you run 'java -version' and 'mvn -version' what do you get
>>>>> back?
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>> Joe
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com>
>>> wrote:
>>>>>>>>>>>>> I’m getting the below on a VM. It does build successfully on my
>>>>>>> Mac, though.
>>>>>>>>>>>>>
>>>>>>>>>>>>> mvn -e -X -T 2.0C clean install
>>>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>> (default-compile) on project nifi-api: Compilation failure -> [Help 1]
>>>>>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed
>>> to
>>>>>>> execute goal
>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>>>>>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>>>>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>>>>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>>>>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>>>>>> at
>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>>>>>> at
>>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>>>>>> 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:1142)
>>>>>>>>>>>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>>>>>> Caused by:
>>>>>>> org.apache.maven.plugin.compiler.CompilationFailureException:
>>>>> Compilation
>>>>>>> failure
>>>>>>>>>>>>> at
>>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>>>>>>>>>> at
>>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>>>>>>>>>> at
>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>>>>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>>>>>> ... 11 more
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Jeff
>>>
>>>
Re: nifi fails build on CentOS 7
Posted by Joe Witt <jo...@gmail.com>.
Jeff - can you please send another note telling Tony that it turns out
it was memory settings :-)
He is making fun of me off-list. He should totally do that on-list!
Glad you're in business now and sorry for my terrible misdirection.
Joe
On Wed, Nov 4, 2015 at 12:49 AM, Tony Kurc <tr...@gmail.com> wrote:
> Huzzah
>
> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com> wrote:
>
>>
>> I removed openjdk and installed the Oracle jdk and it now works.
>>
>> Thanks for the help!!
>>
>> > On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com> wrote:
>> >
>> > it is entirely possible that you only have the jre installed. 'yum
>> > whatprovides "*/bin/javac"' may tell you packages which you can install
>> > which include a compiler.
>> >
>> > On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com> wrote:
>> >
>> >>
>> >>
>> >> find / -name javac did not return anything
>> >>
>> >> I had JAVA_HOME set to
>> >> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>> >>
>> >>
>> >>
>> >>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com> wrote:
>> >>>
>> >>> Jeff,
>> >>> Were you able to run that find command?
>> >>>
>> >>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com> wrote:
>> >>>
>> >>>>
>> >>>> [INFO] BUILD FAILURE
>> >>>> [INFO]
>> >>>>
>> ------------------------------------------------------------------------
>> >>>> [INFO] Total time: 8.091 s
>> >>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
>> >>>> [INFO] Final Memory: 76M/365M
>> >>>> [INFO]
>> >>>>
>> ------------------------------------------------------------------------
>> >>>> [ERROR] Failed to execute goal
>> >>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>> >>>> (default-compile) on project nifi-api: Compilation failure -> [Help 1]
>> >>>> [ERROR]
>> >>>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>> the
>> >>>> -e switch.
>> >>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> >>>> [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/MojoFailureException
>> >>>> [ERROR]
>> >>>> [ERROR] After correcting the problems, you can resume the build with
>> the
>> >>>> command
>> >>>> [ERROR] mvn <goals> -rf :nifi-api
>> >>>>
>> >>>>
>> >>>>
>> >>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com> wrote:
>> >>>>>
>> >>>>> Can you go ahead and try just plain ol'
>> >>>>>
>> >>>>> mvn clean install
>> >>>>>
>> >>>>> I am curious if there is a memory/settings issue that is manifesting
>> >>>>> as an exception during compilation but that it isn't actually a
>> >>>>> compilation problem at all...
>> >>>>>
>> >>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j....@gmail.com> wrote:
>> >>>>>> The only other message I see is
>> >>>>>>
>> >>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac' from the
>> >>>> environment.
>> >>>>>>
>> >>>>>> No worries, it can wait.
>> >>>>>>
>> >>>>>> Thanks,
>> >>>>>>
>> >>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com> wrote:
>> >>>>>>>
>> >>>>>>> if i weren't on horrible hotel wifi right now i'd try to pull down
>> >>>>>>> centos. Is there anymore that can be found with those stack
>> traces .
>> >>>>>>> They're not saying much. Your java and maven versions seem quite
>> >> good
>> >>>>>>> so need to dig further.
>> >>>>>>>
>> >>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j....@gmail.com> wrote:
>> >>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>> >>>>>>>>
>> >>>>>>>> [root@localhost nifi]# java -version
>> >>>>>>>> openjdk version "1.8.0_65"
>> >>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>> >>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> [root@localhost nifi]# mvn -version
>> >>>>>>>> which: no javac in
>> >>>>
>> >>
>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>> >>>>>>>> Warning: JAVA_HOME environment variable is not set.
>> >>>>>>>> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
>> >>>> 2015-04-22T06:57:37-05:00)
>> >>>>>>>> Maven home: /opt/apache-maven-3.3.3
>> >>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>> >>>>>>>> Java home:
>> >>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>> >>>>>>>> Default locale: en_US, platform encoding: UTF-8
>> >>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch:
>> >>>> "amd64", family: "unix"
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <jo...@gmail.com> wrote:
>> >>>>>>>>>
>> >>>>>>>>> Jeff
>> >>>>>>>>>
>> >>>>>>>>> When you run 'java -version' and 'mvn -version' what do you get
>> >> back?
>> >>>>>>>>>
>> >>>>>>>>> Thanks
>> >>>>>>>>> Joe
>> >>>>>>>>>
>> >>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com>
>> wrote:
>> >>>>>>>>>> I’m getting the below on a VM. It does build successfully on my
>> >>>> Mac, though.
>> >>>>>>>>>>
>> >>>>>>>>>> mvn -e -X -T 2.0C clean install
>> >>>>>>>>>> [ERROR] Failed to execute goal
>> >>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>> >>>> (default-compile) on project nifi-api: Compilation failure -> [Help 1]
>> >>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed
>> to
>> >>>> execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>> >>>> (default-compile) on project nifi-api: Compilation failure
>> >>>>>>>>>> at
>> >>>>
>> >>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>> >>>>>>>>>> at
>> >>>>
>> >>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>> >>>>>>>>>> at
>> >>>>
>> >>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>> >>>>>>>>>> at
>> >>>>
>> >>
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>> >>>>>>>>>> at
>> >>>>
>> >>
>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>> >>>>>>>>>> at
>> >>>>
>> >>
>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>> >>>>>>>>>> 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:1142)
>> >>>>>>>>>> at
>> >>>>
>> >>
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> >>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>> >>>>>>>>>> Caused by:
>> >>>> org.apache.maven.plugin.compiler.CompilationFailureException:
>> >> Compilation
>> >>>> failure
>> >>>>>>>>>> at
>> >>>>
>> >>
>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>> >>>>>>>>>> at
>> >>>>
>> >>
>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>> >>>>>>>>>> at
>> >>>>
>> >>
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>> >>>>>>>>>> at
>> >>>>
>> >>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>> >>>>>>>>>> ... 11 more
>> >>>>>>>>>>
>> >>>>>>>>>> Thanks,
>> >>>>>>>>>> Jeff
>> >>>>>>>>
>> >>>>>>
>> >>>>
>> >>>>
>> >>
>> >>
>>
>>
Re: nifi fails build on CentOS 7
Posted by Tony Kurc <tr...@gmail.com>.
Huzzah
On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j....@gmail.com> wrote:
>
> I removed openjdk and installed the Oracle jdk and it now works.
>
> Thanks for the help!!
>
> > On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com> wrote:
> >
> > it is entirely possible that you only have the jre installed. 'yum
> > whatprovides "*/bin/javac"' may tell you packages which you can install
> > which include a compiler.
> >
> > On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com> wrote:
> >
> >>
> >>
> >> find / -name javac did not return anything
> >>
> >> I had JAVA_HOME set to
> >> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
> >>
> >>
> >>
> >>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com> wrote:
> >>>
> >>> Jeff,
> >>> Were you able to run that find command?
> >>>
> >>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com> wrote:
> >>>
> >>>>
> >>>> [INFO] BUILD FAILURE
> >>>> [INFO]
> >>>>
> ------------------------------------------------------------------------
> >>>> [INFO] Total time: 8.091 s
> >>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
> >>>> [INFO] Final Memory: 76M/365M
> >>>> [INFO]
> >>>>
> ------------------------------------------------------------------------
> >>>> [ERROR] Failed to execute goal
> >>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >>>> (default-compile) on project nifi-api: Compilation failure -> [Help 1]
> >>>> [ERROR]
> >>>> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the
> >>>> -e switch.
> >>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> >>>> [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/MojoFailureException
> >>>> [ERROR]
> >>>> [ERROR] After correcting the problems, you can resume the build with
> the
> >>>> command
> >>>> [ERROR] mvn <goals> -rf :nifi-api
> >>>>
> >>>>
> >>>>
> >>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com> wrote:
> >>>>>
> >>>>> Can you go ahead and try just plain ol'
> >>>>>
> >>>>> mvn clean install
> >>>>>
> >>>>> I am curious if there is a memory/settings issue that is manifesting
> >>>>> as an exception during compilation but that it isn't actually a
> >>>>> compilation problem at all...
> >>>>>
> >>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j....@gmail.com> wrote:
> >>>>>> The only other message I see is
> >>>>>>
> >>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac' from the
> >>>> environment.
> >>>>>>
> >>>>>> No worries, it can wait.
> >>>>>>
> >>>>>> Thanks,
> >>>>>>
> >>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com> wrote:
> >>>>>>>
> >>>>>>> if i weren't on horrible hotel wifi right now i'd try to pull down
> >>>>>>> centos. Is there anymore that can be found with those stack
> traces .
> >>>>>>> They're not saying much. Your java and maven versions seem quite
> >> good
> >>>>>>> so need to dig further.
> >>>>>>>
> >>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j....@gmail.com> wrote:
> >>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
> >>>>>>>>
> >>>>>>>> [root@localhost nifi]# java -version
> >>>>>>>> openjdk version "1.8.0_65"
> >>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
> >>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> [root@localhost nifi]# mvn -version
> >>>>>>>> which: no javac in
> >>>>
> >>
> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
> >>>>>>>> Warning: JAVA_HOME environment variable is not set.
> >>>>>>>> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
> >>>> 2015-04-22T06:57:37-05:00)
> >>>>>>>> Maven home: /opt/apache-maven-3.3.3
> >>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
> >>>>>>>> Java home:
> >>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
> >>>>>>>> Default locale: en_US, platform encoding: UTF-8
> >>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch:
> >>>> "amd64", family: "unix"
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <jo...@gmail.com> wrote:
> >>>>>>>>>
> >>>>>>>>> Jeff
> >>>>>>>>>
> >>>>>>>>> When you run 'java -version' and 'mvn -version' what do you get
> >> back?
> >>>>>>>>>
> >>>>>>>>> Thanks
> >>>>>>>>> Joe
> >>>>>>>>>
> >>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com>
> wrote:
> >>>>>>>>>> I’m getting the below on a VM. It does build successfully on my
> >>>> Mac, though.
> >>>>>>>>>>
> >>>>>>>>>> mvn -e -X -T 2.0C clean install
> >>>>>>>>>> [ERROR] Failed to execute goal
> >>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >>>> (default-compile) on project nifi-api: Compilation failure -> [Help 1]
> >>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed
> to
> >>>> execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >>>> (default-compile) on project nifi-api: Compilation failure
> >>>>>>>>>> at
> >>>>
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> >>>>>>>>>> at
> >>>>
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> >>>>>>>>>> at
> >>>>
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> >>>>>>>>>> at
> >>>>
> >>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> >>>>>>>>>> at
> >>>>
> >>
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
> >>>>>>>>>> at
> >>>>
> >>
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
> >>>>>>>>>> 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:1142)
> >>>>>>>>>> at
> >>>>
> >>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> >>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
> >>>>>>>>>> Caused by:
> >>>> org.apache.maven.plugin.compiler.CompilationFailureException:
> >> Compilation
> >>>> failure
> >>>>>>>>>> at
> >>>>
> >>
> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
> >>>>>>>>>> at
> >>>>
> >>
> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
> >>>>>>>>>> at
> >>>>
> >>
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> >>>>>>>>>> at
> >>>>
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> >>>>>>>>>> ... 11 more
> >>>>>>>>>>
> >>>>>>>>>> Thanks,
> >>>>>>>>>> Jeff
> >>>>>>>>
> >>>>>>
> >>>>
> >>>>
> >>
> >>
>
>
Re: nifi fails build on CentOS 7
Posted by Jeff <j....@gmail.com>.
I removed openjdk and installed the Oracle jdk and it now works.
Thanks for the help!!
> On Nov 3, 2015, at 6:40 PM, Tony Kurc <tr...@gmail.com> wrote:
>
> it is entirely possible that you only have the jre installed. 'yum
> whatprovides "*/bin/javac"' may tell you packages which you can install
> which include a compiler.
>
> On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com> wrote:
>
>>
>>
>> find / -name javac did not return anything
>>
>> I had JAVA_HOME set to
>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>
>>
>>
>>> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>
>>> Jeff,
>>> Were you able to run that find command?
>>>
>>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com> wrote:
>>>
>>>>
>>>> [INFO] BUILD FAILURE
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Total time: 8.091 s
>>>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
>>>> [INFO] Final Memory: 76M/365M
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [ERROR] Failed to execute goal
>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>> (default-compile) on project nifi-api: Compilation failure -> [Help 1]
>>>> [ERROR]
>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>>>> -e switch.
>>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>>> [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/MojoFailureException
>>>> [ERROR]
>>>> [ERROR] After correcting the problems, you can resume the build with the
>>>> command
>>>> [ERROR] mvn <goals> -rf :nifi-api
>>>>
>>>>
>>>>
>>>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>
>>>>> Can you go ahead and try just plain ol'
>>>>>
>>>>> mvn clean install
>>>>>
>>>>> I am curious if there is a memory/settings issue that is manifesting
>>>>> as an exception during compilation but that it isn't actually a
>>>>> compilation problem at all...
>>>>>
>>>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j....@gmail.com> wrote:
>>>>>> The only other message I see is
>>>>>>
>>>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac' from the
>>>> environment.
>>>>>>
>>>>>> No worries, it can wait.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>
>>>>>>> if i weren't on horrible hotel wifi right now i'd try to pull down
>>>>>>> centos. Is there anymore that can be found with those stack traces .
>>>>>>> They're not saying much. Your java and maven versions seem quite
>> good
>>>>>>> so need to dig further.
>>>>>>>
>>>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>>>>>>
>>>>>>>> [root@localhost nifi]# java -version
>>>>>>>> openjdk version "1.8.0_65"
>>>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>>>>>>
>>>>>>>>
>>>>>>>> [root@localhost nifi]# mvn -version
>>>>>>>> which: no javac in
>>>>
>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>>>>>>> Warning: JAVA_HOME environment variable is not set.
>>>>>>>> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
>>>> 2015-04-22T06:57:37-05:00)
>>>>>>>> Maven home: /opt/apache-maven-3.3.3
>>>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>>>>>>> Java home:
>>>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch:
>>>> "amd64", family: "unix"
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Jeff
>>>>>>>>>
>>>>>>>>> When you run 'java -version' and 'mvn -version' what do you get
>> back?
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>> Joe
>>>>>>>>>
>>>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>>>> I’m getting the below on a VM. It does build successfully on my
>>>> Mac, though.
>>>>>>>>>>
>>>>>>>>>> mvn -e -X -T 2.0C clean install
>>>>>>>>>> [ERROR] Failed to execute goal
>>>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>> (default-compile) on project nifi-api: Compilation failure -> [Help 1]
>>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>> execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>>>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>>>> at
>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>>> at
>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>>> at
>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>>> at
>>>>
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>>> at
>>>>
>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>>>> at
>>>>
>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>>>> 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:1142)
>>>>>>>>>> at
>>>>
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>>>> Caused by:
>>>> org.apache.maven.plugin.compiler.CompilationFailureException:
>> Compilation
>>>> failure
>>>>>>>>>> at
>>>>
>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>>>>>>> at
>>>>
>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>>>>>>> at
>>>>
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>>> at
>>>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>>>> ... 11 more
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Jeff
>>>>>>>>
>>>>>>
>>>>
>>>>
>>
>>
Re: nifi fails build on CentOS 7
Posted by Tony Kurc <tr...@gmail.com>.
it is entirely possible that you only have the jre installed. 'yum
whatprovides "*/bin/javac"' may tell you packages which you can install
which include a compiler.
On Tue, Nov 3, 2015 at 7:35 PM, Jeff <j....@gmail.com> wrote:
>
>
> find / -name javac did not return anything
>
> I had JAVA_HOME set to
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>
>
>
> > On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com> wrote:
> >
> > Jeff,
> > Were you able to run that find command?
> >
> > On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com> wrote:
> >
> >>
> >> [INFO] BUILD FAILURE
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] Total time: 8.091 s
> >> [INFO] Finished at: 2015-11-03T12:08:59-06:00
> >> [INFO] Final Memory: 76M/365M
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [ERROR] Failed to execute goal
> >> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >> (default-compile) on project nifi-api: Compilation failure -> [Help 1]
> >> [ERROR]
> >> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> >> -e switch.
> >> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> >> [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/MojoFailureException
> >> [ERROR]
> >> [ERROR] After correcting the problems, you can resume the build with the
> >> command
> >> [ERROR] mvn <goals> -rf :nifi-api
> >>
> >>
> >>
> >>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com> wrote:
> >>>
> >>> Can you go ahead and try just plain ol'
> >>>
> >>> mvn clean install
> >>>
> >>> I am curious if there is a memory/settings issue that is manifesting
> >>> as an exception during compilation but that it isn't actually a
> >>> compilation problem at all...
> >>>
> >>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j....@gmail.com> wrote:
> >>>> The only other message I see is
> >>>>
> >>>> [WARNING] Unable to autodetect 'javac' path, using 'javac' from the
> >> environment.
> >>>>
> >>>> No worries, it can wait.
> >>>>
> >>>> Thanks,
> >>>>
> >>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com> wrote:
> >>>>>
> >>>>> if i weren't on horrible hotel wifi right now i'd try to pull down
> >>>>> centos. Is there anymore that can be found with those stack traces .
> >>>>> They're not saying much. Your java and maven versions seem quite
> good
> >>>>> so need to dig further.
> >>>>>
> >>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j....@gmail.com> wrote:
> >>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
> >>>>>>
> >>>>>> [root@localhost nifi]# java -version
> >>>>>> openjdk version "1.8.0_65"
> >>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
> >>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
> >>>>>>
> >>>>>>
> >>>>>> [root@localhost nifi]# mvn -version
> >>>>>> which: no javac in
> >>
> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
> >>>>>> Warning: JAVA_HOME environment variable is not set.
> >>>>>> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
> >> 2015-04-22T06:57:37-05:00)
> >>>>>> Maven home: /opt/apache-maven-3.3.3
> >>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
> >>>>>> Java home:
> >> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
> >>>>>> Default locale: en_US, platform encoding: UTF-8
> >>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch:
> >> "amd64", family: "unix"
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <jo...@gmail.com> wrote:
> >>>>>>>
> >>>>>>> Jeff
> >>>>>>>
> >>>>>>> When you run 'java -version' and 'mvn -version' what do you get
> back?
> >>>>>>>
> >>>>>>> Thanks
> >>>>>>> Joe
> >>>>>>>
> >>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com> wrote:
> >>>>>>>> I’m getting the below on a VM. It does build successfully on my
> >> Mac, though.
> >>>>>>>>
> >>>>>>>> mvn -e -X -T 2.0C clean install
> >>>>>>>> [ERROR] Failed to execute goal
> >> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >> (default-compile) on project nifi-api: Compilation failure -> [Help 1]
> >>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> >> execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> >> (default-compile) on project nifi-api: Compilation failure
> >>>>>>>> at
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> >>>>>>>> at
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> >>>>>>>> at
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> >>>>>>>> at
> >>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> >>>>>>>> at
> >>
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
> >>>>>>>> at
> >>
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
> >>>>>>>> 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:1142)
> >>>>>>>> at
> >>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> >>>>>>>> at java.lang.Thread.run(Thread.java:745)
> >>>>>>>> Caused by:
> >> org.apache.maven.plugin.compiler.CompilationFailureException:
> Compilation
> >> failure
> >>>>>>>> at
> >>
> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
> >>>>>>>> at
> >>
> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
> >>>>>>>> at
> >>
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> >>>>>>>> at
> >>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> >>>>>>>> ... 11 more
> >>>>>>>>
> >>>>>>>> Thanks,
> >>>>>>>> Jeff
> >>>>>>
> >>>>
> >>
> >>
>
>
Re: nifi fails build on CentOS 7
Posted by Jeff <j....@gmail.com>.
find / -name javac did not return anything
I had JAVA_HOME set to
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
> On Nov 3, 2015, at 6:30 PM, Tony Kurc <tr...@gmail.com> wrote:
>
> Jeff,
> Were you able to run that find command?
>
> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com> wrote:
>
>>
>> [INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 8.091 s
>> [INFO] Finished at: 2015-11-03T12:08:59-06:00
>> [INFO] Final Memory: 76M/365M
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>> (default-compile) on project nifi-api: Compilation failure -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [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/MojoFailureException
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>> [ERROR] mvn <goals> -rf :nifi-api
>>
>>
>>
>>> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com> wrote:
>>>
>>> Can you go ahead and try just plain ol'
>>>
>>> mvn clean install
>>>
>>> I am curious if there is a memory/settings issue that is manifesting
>>> as an exception during compilation but that it isn't actually a
>>> compilation problem at all...
>>>
>>> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j....@gmail.com> wrote:
>>>> The only other message I see is
>>>>
>>>> [WARNING] Unable to autodetect 'javac' path, using 'javac' from the
>> environment.
>>>>
>>>> No worries, it can wait.
>>>>
>>>> Thanks,
>>>>
>>>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>
>>>>> if i weren't on horrible hotel wifi right now i'd try to pull down
>>>>> centos. Is there anymore that can be found with those stack traces .
>>>>> They're not saying much. Your java and maven versions seem quite good
>>>>> so need to dig further.
>>>>>
>>>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j....@gmail.com> wrote:
>>>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>>>>
>>>>>> [root@localhost nifi]# java -version
>>>>>> openjdk version "1.8.0_65"
>>>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>>>>
>>>>>>
>>>>>> [root@localhost nifi]# mvn -version
>>>>>> which: no javac in
>> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>>>>> Warning: JAVA_HOME environment variable is not set.
>>>>>> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
>> 2015-04-22T06:57:37-05:00)
>>>>>> Maven home: /opt/apache-maven-3.3.3
>>>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>>>>> Java home:
>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch:
>> "amd64", family: "unix"
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>>>
>>>>>>> Jeff
>>>>>>>
>>>>>>> When you run 'java -version' and 'mvn -version' what do you get back?
>>>>>>>
>>>>>>> Thanks
>>>>>>> Joe
>>>>>>>
>>>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com> wrote:
>>>>>>>> I’m getting the below on a VM. It does build successfully on my
>> Mac, though.
>>>>>>>>
>>>>>>>> mvn -e -X -T 2.0C clean install
>>>>>>>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>> (default-compile) on project nifi-api: Compilation failure -> [Help 1]
>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>> execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
>> (default-compile) on project nifi-api: Compilation failure
>>>>>>>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>> at
>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>>>> at
>> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>>>> 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:1142)
>>>>>>>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>>> Caused by:
>> org.apache.maven.plugin.compiler.CompilationFailureException: Compilation
>> failure
>>>>>>>> at
>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>>>>> at
>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>>>>> at
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>>>> ... 11 more
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Jeff
>>>>>>
>>>>
>>
>>
Re: nifi fails build on CentOS 7
Posted by Tony Kurc <tr...@gmail.com>.
Jeff,
Were you able to run that find command?
On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j....@gmail.com> wrote:
>
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 8.091 s
> [INFO] Finished at: 2015-11-03T12:08:59-06:00
> [INFO] Final Memory: 76M/365M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> (default-compile) on project nifi-api: Compilation failure -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [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/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :nifi-api
>
>
>
> > On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com> wrote:
> >
> > Can you go ahead and try just plain ol'
> >
> > mvn clean install
> >
> > I am curious if there is a memory/settings issue that is manifesting
> > as an exception during compilation but that it isn't actually a
> > compilation problem at all...
> >
> > On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j....@gmail.com> wrote:
> >> The only other message I see is
> >>
> >> [WARNING] Unable to autodetect 'javac' path, using 'javac' from the
> environment.
> >>
> >> No worries, it can wait.
> >>
> >> Thanks,
> >>
> >>> On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com> wrote:
> >>>
> >>> if i weren't on horrible hotel wifi right now i'd try to pull down
> >>> centos. Is there anymore that can be found with those stack traces .
> >>> They're not saying much. Your java and maven versions seem quite good
> >>> so need to dig further.
> >>>
> >>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j....@gmail.com> wrote:
> >>>> JAVA_HOME is currently not set but I’ve tried both ways.
> >>>>
> >>>> [root@localhost nifi]# java -version
> >>>> openjdk version "1.8.0_65"
> >>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
> >>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
> >>>>
> >>>>
> >>>> [root@localhost nifi]# mvn -version
> >>>> which: no javac in
> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
> >>>> Warning: JAVA_HOME environment variable is not set.
> >>>> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
> 2015-04-22T06:57:37-05:00)
> >>>> Maven home: /opt/apache-maven-3.3.3
> >>>> Java version: 1.8.0_65, vendor: Oracle Corporation
> >>>> Java home:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
> >>>> Default locale: en_US, platform encoding: UTF-8
> >>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch:
> "amd64", family: "unix"
> >>>>
> >>>>
> >>>>
> >>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <jo...@gmail.com> wrote:
> >>>>>
> >>>>> Jeff
> >>>>>
> >>>>> When you run 'java -version' and 'mvn -version' what do you get back?
> >>>>>
> >>>>> Thanks
> >>>>> Joe
> >>>>>
> >>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com> wrote:
> >>>>>> I’m getting the below on a VM. It does build successfully on my
> Mac, though.
> >>>>>>
> >>>>>> mvn -e -X -T 2.0C clean install
> >>>>>> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> (default-compile) on project nifi-api: Compilation failure -> [Help 1]
> >>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile
> (default-compile) on project nifi-api: Compilation failure
> >>>>>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> >>>>>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> >>>>>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> >>>>>> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> >>>>>> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
> >>>>>> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
> >>>>>> 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:1142)
> >>>>>> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> >>>>>> at java.lang.Thread.run(Thread.java:745)
> >>>>>> Caused by:
> org.apache.maven.plugin.compiler.CompilationFailureException: Compilation
> failure
> >>>>>> at
> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
> >>>>>> at
> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
> >>>>>> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> >>>>>> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> >>>>>> ... 11 more
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Jeff
> >>>>
> >>
>
>
Re: nifi fails build on CentOS 7
Posted by Jeff <j....@gmail.com>.
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8.091 s
[INFO] Finished at: 2015-11-03T12:08:59-06:00
[INFO] Final Memory: 76M/365M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project nifi-api: Compilation failure -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[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/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :nifi-api
> On Nov 3, 2015, at 6:07 PM, Joe Witt <jo...@gmail.com> wrote:
>
> Can you go ahead and try just plain ol'
>
> mvn clean install
>
> I am curious if there is a memory/settings issue that is manifesting
> as an exception during compilation but that it isn't actually a
> compilation problem at all...
>
> On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j....@gmail.com> wrote:
>> The only other message I see is
>>
>> [WARNING] Unable to autodetect 'javac' path, using 'javac' from the environment.
>>
>> No worries, it can wait.
>>
>> Thanks,
>>
>>> On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com> wrote:
>>>
>>> if i weren't on horrible hotel wifi right now i'd try to pull down
>>> centos. Is there anymore that can be found with those stack traces .
>>> They're not saying much. Your java and maven versions seem quite good
>>> so need to dig further.
>>>
>>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j....@gmail.com> wrote:
>>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>>
>>>> [root@localhost nifi]# java -version
>>>> openjdk version "1.8.0_65"
>>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>>
>>>>
>>>> [root@localhost nifi]# mvn -version
>>>> which: no javac in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>>> Warning: JAVA_HOME environment variable is not set.
>>>> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T06:57:37-05:00)
>>>> Maven home: /opt/apache-maven-3.3.3
>>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>>> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>>> Default locale: en_US, platform encoding: UTF-8
>>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch: "amd64", family: "unix"
>>>>
>>>>
>>>>
>>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>>
>>>>> Jeff
>>>>>
>>>>> When you run 'java -version' and 'mvn -version' what do you get back?
>>>>>
>>>>> Thanks
>>>>> Joe
>>>>>
>>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com> wrote:
>>>>>> I’m getting the below on a VM. It does build successfully on my Mac, though.
>>>>>>
>>>>>> mvn -e -X -T 2.0C clean install
>>>>>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project nifi-api: Compilation failure -> [Help 1]
>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project nifi-api: Compilation failure
>>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>> at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>>> at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>>> 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:1142)
>>>>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>> Caused by: org.apache.maven.plugin.compiler.CompilationFailureException: Compilation failure
>>>>>> at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>>> at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>>> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>>> ... 11 more
>>>>>>
>>>>>> Thanks,
>>>>>> Jeff
>>>>
>>
Re: nifi fails build on CentOS 7
Posted by Joe Witt <jo...@gmail.com>.
Can you go ahead and try just plain ol'
mvn clean install
I am curious if there is a memory/settings issue that is manifesting
as an exception during compilation but that it isn't actually a
compilation problem at all...
On Wed, Nov 4, 2015 at 12:06 AM, Jeff <j....@gmail.com> wrote:
> The only other message I see is
>
> [WARNING] Unable to autodetect 'javac' path, using 'javac' from the environment.
>
> No worries, it can wait.
>
> Thanks,
>
>> On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com> wrote:
>>
>> if i weren't on horrible hotel wifi right now i'd try to pull down
>> centos. Is there anymore that can be found with those stack traces .
>> They're not saying much. Your java and maven versions seem quite good
>> so need to dig further.
>>
>> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j....@gmail.com> wrote:
>>> JAVA_HOME is currently not set but I’ve tried both ways.
>>>
>>> [root@localhost nifi]# java -version
>>> openjdk version "1.8.0_65"
>>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>>
>>>
>>> [root@localhost nifi]# mvn -version
>>> which: no javac in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>>> Warning: JAVA_HOME environment variable is not set.
>>> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T06:57:37-05:00)
>>> Maven home: /opt/apache-maven-3.3.3
>>> Java version: 1.8.0_65, vendor: Oracle Corporation
>>> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>>> Default locale: en_US, platform encoding: UTF-8
>>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch: "amd64", family: "unix"
>>>
>>>
>>>
>>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <jo...@gmail.com> wrote:
>>>>
>>>> Jeff
>>>>
>>>> When you run 'java -version' and 'mvn -version' what do you get back?
>>>>
>>>> Thanks
>>>> Joe
>>>>
>>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com> wrote:
>>>>> I’m getting the below on a VM. It does build successfully on my Mac, though.
>>>>>
>>>>> mvn -e -X -T 2.0C clean install
>>>>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project nifi-api: Compilation failure -> [Help 1]
>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project nifi-api: Compilation failure
>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>> at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>>> at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>>> 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:1142)
>>>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>> Caused by: org.apache.maven.plugin.compiler.CompilationFailureException: Compilation failure
>>>>> at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>>> at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>>> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>>> ... 11 more
>>>>>
>>>>> Thanks,
>>>>> Jeff
>>>
>
Re: nifi fails build on CentOS 7
Posted by Jeff <j....@gmail.com>.
The only other message I see is
[WARNING] Unable to autodetect 'javac' path, using 'javac' from the environment.
No worries, it can wait.
Thanks,
> On Nov 3, 2015, at 5:46 PM, Joe Witt <jo...@gmail.com> wrote:
>
> if i weren't on horrible hotel wifi right now i'd try to pull down
> centos. Is there anymore that can be found with those stack traces .
> They're not saying much. Your java and maven versions seem quite good
> so need to dig further.
>
> On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j....@gmail.com> wrote:
>> JAVA_HOME is currently not set but I’ve tried both ways.
>>
>> [root@localhost nifi]# java -version
>> openjdk version "1.8.0_65"
>> OpenJDK Runtime Environment (build 1.8.0_65-b17)
>> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>>
>>
>> [root@localhost nifi]# mvn -version
>> which: no javac in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
>> Warning: JAVA_HOME environment variable is not set.
>> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T06:57:37-05:00)
>> Maven home: /opt/apache-maven-3.3.3
>> Java version: 1.8.0_65, vendor: Oracle Corporation
>> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch: "amd64", family: "unix"
>>
>>
>>
>>> On Nov 3, 2015, at 5:37 PM, Joe Witt <jo...@gmail.com> wrote:
>>>
>>> Jeff
>>>
>>> When you run 'java -version' and 'mvn -version' what do you get back?
>>>
>>> Thanks
>>> Joe
>>>
>>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com> wrote:
>>>> I’m getting the below on a VM. It does build successfully on my Mac, though.
>>>>
>>>> mvn -e -X -T 2.0C clean install
>>>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project nifi-api: Compilation failure -> [Help 1]
>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project nifi-api: Compilation failure
>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>> at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>>> at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>>> 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:1142)
>>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>> at java.lang.Thread.run(Thread.java:745)
>>>> Caused by: org.apache.maven.plugin.compiler.CompilationFailureException: Compilation failure
>>>> at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>>> at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>>> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>>> ... 11 more
>>>>
>>>> Thanks,
>>>> Jeff
>>
Re: nifi fails build on CentOS 7
Posted by Joe Witt <jo...@gmail.com>.
if i weren't on horrible hotel wifi right now i'd try to pull down
centos. Is there anymore that can be found with those stack traces .
They're not saying much. Your java and maven versions seem quite good
so need to dig further.
On Tue, Nov 3, 2015 at 11:42 PM, Jeff <j....@gmail.com> wrote:
> JAVA_HOME is currently not set but I’ve tried both ways.
>
> [root@localhost nifi]# java -version
> openjdk version "1.8.0_65"
> OpenJDK Runtime Environment (build 1.8.0_65-b17)
> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
>
>
> [root@localhost nifi]# mvn -version
> which: no javac in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
> Warning: JAVA_HOME environment variable is not set.
> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T06:57:37-05:00)
> Maven home: /opt/apache-maven-3.3.3
> Java version: 1.8.0_65, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch: "amd64", family: "unix"
>
>
>
>> On Nov 3, 2015, at 5:37 PM, Joe Witt <jo...@gmail.com> wrote:
>>
>> Jeff
>>
>> When you run 'java -version' and 'mvn -version' what do you get back?
>>
>> Thanks
>> Joe
>>
>> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com> wrote:
>>> I’m getting the below on a VM. It does build successfully on my Mac, though.
>>>
>>> mvn -e -X -T 2.0C clean install
>>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project nifi-api: Compilation failure -> [Help 1]
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project nifi-api: Compilation failure
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>> at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>>> at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>>> 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:1142)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>> at java.lang.Thread.run(Thread.java:745)
>>> Caused by: org.apache.maven.plugin.compiler.CompilationFailureException: Compilation failure
>>> at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>>> at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>>> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>>> ... 11 more
>>>
>>> Thanks,
>>> Jeff
>
Re: nifi fails build on CentOS 7
Posted by Jeff <j....@gmail.com>.
JAVA_HOME is currently not set but I’ve tried both ways.
[root@localhost nifi]# java -version
openjdk version "1.8.0_65"
OpenJDK Runtime Environment (build 1.8.0_65-b17)
OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
[root@localhost nifi]# mvn -version
which: no javac in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/opt/apache-maven-3.3.3/bin)
Warning: JAVA_HOME environment variable is not set.
Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T06:57:37-05:00)
Maven home: /opt/apache-maven-3.3.3
Java version: 1.8.0_65, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-2.b17.el7_1.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-229.11.1.el7.x86_64", arch: "amd64", family: "unix"
> On Nov 3, 2015, at 5:37 PM, Joe Witt <jo...@gmail.com> wrote:
>
> Jeff
>
> When you run 'java -version' and 'mvn -version' what do you get back?
>
> Thanks
> Joe
>
> On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com> wrote:
>> I’m getting the below on a VM. It does build successfully on my Mac, though.
>>
>> mvn -e -X -T 2.0C clean install
>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project nifi-api: Compilation failure -> [Help 1]
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project nifi-api: Compilation failure
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>> at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
>> at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
>> 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:1142)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:745)
>> Caused by: org.apache.maven.plugin.compiler.CompilationFailureException: Compilation failure
>> at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
>> at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
>> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>> ... 11 more
>>
>> Thanks,
>> Jeff
Re: nifi fails build on CentOS 7
Posted by Joe Witt <jo...@gmail.com>.
Jeff
When you run 'java -version' and 'mvn -version' what do you get back?
Thanks
Joe
On Tue, Nov 3, 2015 at 11:35 PM, Jeff <j....@gmail.com> wrote:
> I’m getting the below on a VM. It does build successfully on my Mac, though.
>
> mvn -e -X -T 2.0C clean install
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project nifi-api: Compilation failure -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project nifi-api: Compilation failure
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
> at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
> 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:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.maven.plugin.compiler.CompilationFailureException: Compilation failure
> at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
> at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 11 more
>
> Thanks,
> Jeff
nifi fails build on CentOS 7
Posted by Jeff <j....@gmail.com>.
I’m getting the below on a VM. It does build successfully on my Mac, though.
mvn -e -X -T 2.0C clean install
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project nifi-api: Compilation failure -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project nifi-api: Compilation failure
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:189)
at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
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:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.maven.plugin.compiler.CompilationFailureException: Compilation failure
at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:913)
at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 11 more
Thanks,
Jeff
Re: "External" extensions
Posted by Joe Witt <jo...@gmail.com>.
I think Adam,sumo,others point out good paths or models to consider. But
as I and Benson are mentioning we must find a good path that also adheres
to the principles of the apache way.
On Nov 2, 2015 10:10 AM, <xm...@gmail.com> wrote:
> In nodejs/npm world, each module has package.json, which declaratively
> indicate which node version and other external modules it depends on.
> Similarly I am thinking Nar modules can declare which version of JVM and
> NiFi it depends on and also which other modules it depends on. NPM ( NiFi
> Package Manager) can warn users if the module they are trying to Install
> doesn't match their runtime.
>
> -Sumo
>
>
>
> Sent from my iPad
>
> > On Nov 1, 2015, at 2:14 PM, Oleg Zhurakousky <
> ozhurakousky@hortonworks.com> wrote:
> >
> > Well the question still remains unanswered, what relationship those
> projects have to ASF distribution of NiFi? I seriously doubt that anyone on
> this list suggests that all have to be part of the release. And if they are
> not then they are just individual projects managed in/out of ASF, right?
> >
> > Sent from my iPhone
> >
> >> On Nov 1, 2015, at 17:10, Adam Estrada <es...@gmail.com> wrote:
> >>
> >> The elasticsearch project has a really cool plugin utility that
> automatically downloads and builds plugins from GitHub, BitBucket, etc...
> >>
> >> Has anyone taken a look at that?
> >>
> >> A
> >>
> >> Sent from my iPhone
> >>
> >>> On Nov 1, 2015, at 3:54 PM, Benson Margulies <bi...@gmail.com>
> wrote:
> >>>
> >>> ASF policy; a PMC should not be in the business of creating and
> >>> maintaining code 'somewhere else' and/or under another license, for
> >>> fear of confusion.
> >>>
> >>> Gray area -- some PMC members can be in that business, as long as the
> >>> boundary is clear.
> >>>
> >>> There was a thing called 'apache extras' for this. Unfortunately, it
> >>> was hosted as part of google code, which is defunct. As far as I know,
> >>> various plans to replace it have not come to fruition, but I might be
> >>> behind.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>> On Sun, Nov 1, 2015 at 3:04 PM, <xm...@gmail.com> wrote:
> >>>> How about maintaining a registry like npm https://www.npmjs.com or
> https://github.com/jspm/registry where individuals host their modules on
> github and users can discover them via registry?
> >>>>
> >>>> Sent from my iPad
> >>>>
> >>>>> On Nov 1, 2015, at 10:35 AM, Joe Witt <jo...@gmail.com> wrote:
> >>>>>
> >>>>> " but raises several questions, all pertaining to the relationship of
> >>>>> this project with ASF, its ownership and control."
> >>>>>
> >>>>> ...that is what I'm struggling to respond to as well.
> >>>>>
> >>>>> It feels like the right path within the ASF is to establish child
> >>>>> projects of Apache NiFi. I think we knew we needed to do this anyway
> >>>>> as we've mentioned before. It just might be time now...
> >>>>>
> >>>>> On Sun, Nov 1, 2015 at 1:34 PM, Oleg Zhurakousky
> >>>>> <oz...@hortonworks.com> wrote:
> >>>>>> Tony, plenty of opinion but so are the questions/concerns.
> >>>>>> Managing it on GitHub is perfect, but raises several questions, all
> pertaining to the relationship of this project with ASF, its ownership and
> control.
> >>>>>> Perhaps some PMCs on the list can shed some light as to how it
> could be done?
> >>>>>>
> >>>>>> Cheers
> >>>>>> Oleg
> >>>>>>
> >>>>>> Sent from my iPhone
> >>>>>>
> >>>>>>> On Nov 1, 2015, at 13:08, Adam Estrada <es...@gmail.com>
> wrote:
> >>>>>>>
> >>>>>>> This has been suggested before. It's a great idea!!! I suggest
> creating a repo on github for NiFi-Processors or something like that. There
> are many more folks searching through GitHub than on the Apache wikis, IMO.
> This will inevitably help spread the word...
> >>>>>>>
> >>>>>>> A
> >>>>>>>
> >>>>>>> Sent from my iPhone
> >>>>>>>
> >>>>>>>> On Nov 1, 2015, at 12:55 PM, Tony Kurc <tr...@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>> Not very strong opinions on this?
> >>>>>>>>> On Oct 30, 2015 10:53 AM, "Joe Witt" <jo...@gmail.com> wrote:
> >>>>>>>>>
> >>>>>>>>> Tony,
> >>>>>>>>>
> >>>>>>>>> I completely agree we should do this. A quick github search
> reveals
> >>>>>>>>> there are some nice utilities/processors folks have built for
> NiFi but
> >>>>>>>>> for which they're not necessarily going to submit them as PRs.
> We
> >>>>>>>>> should link to these as much as possible but we should also help
> folks
> >>>>>>>>> understand these aren't 'apache' things and are not of the
> Apache NiFi
> >>>>>>>>> community directly but they are good for users and developers to
> know
> >>>>>>>>> about.
> >>>>>>>>>
> >>>>>>>>> Perhaps a wiki page linking to these is good provided we have the
> >>>>>>>>> above sort of disclaimer and a healthy recognition such
> references
> >>>>>>>>> will become stale...
> >>>>>>>>>
> >>>>>>>>> Thanks
> >>>>>>>>> Joe
> >>>>>>>>>
> >>>>>>>>>> On Fri, Oct 30, 2015 at 10:48 AM, Tony Kurc <tr...@gmail.com>
> wrote:
> >>>>>>>>>> All,
> >>>>>>>>>> I wanted to start a conversation about projects that are good
> for people
> >>>>>>>>>> using or developing NiFi, but either can't or don't belong in
> the source
> >>>>>>>>>> tree. This could be due to licensing issues (for example not
> compatible
> >>>>>>>>> (or
> >>>>>>>>>> not yet determined if it is compatible (GPL [1])) with the
> Apache
> >>>>>>>>> License),
> >>>>>>>>>> or other thought provoking mild concerns like we're discussing
> on
> >>>>>>>>> NIFI-1074
> >>>>>>>>>> [2].
> >>>>>>>>>>
> >>>>>>>>>> I'd like to propose either capturing these on the website or on
> the wiki
> >>>>>>>>> or
> >>>>>>>>>> some other approach I didn't think of. I was hoping to find a
> good
> >>>>>>>>>> archetype for this type of documentation in another apache
> project, but
> >>>>>>>>>> didn't find anything I personally liked. If you have seen
> something you
> >>>>>>>>>> like or don't, I'd be interested to hear.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> [1] http://www.apache.org/licenses/GPL-compatibility.html
> >>>>>>>>>> [2] https://issues.apache.org/jira/browse/NIFI-1074
> >>
>
Re: "External" extensions
Posted by xm...@gmail.com.
In nodejs/npm world, each module has package.json, which declaratively indicate which node version and other external modules it depends on.
Similarly I am thinking Nar modules can declare which version of JVM and NiFi it depends on and also which other modules it depends on. NPM ( NiFi Package Manager) can warn users if the module they are trying to Install doesn't match their runtime.
-Sumo
Sent from my iPad
> On Nov 1, 2015, at 2:14 PM, Oleg Zhurakousky <oz...@hortonworks.com> wrote:
>
> Well the question still remains unanswered, what relationship those projects have to ASF distribution of NiFi? I seriously doubt that anyone on this list suggests that all have to be part of the release. And if they are not then they are just individual projects managed in/out of ASF, right?
>
> Sent from my iPhone
>
>> On Nov 1, 2015, at 17:10, Adam Estrada <es...@gmail.com> wrote:
>>
>> The elasticsearch project has a really cool plugin utility that automatically downloads and builds plugins from GitHub, BitBucket, etc...
>>
>> Has anyone taken a look at that?
>>
>> A
>>
>> Sent from my iPhone
>>
>>> On Nov 1, 2015, at 3:54 PM, Benson Margulies <bi...@gmail.com> wrote:
>>>
>>> ASF policy; a PMC should not be in the business of creating and
>>> maintaining code 'somewhere else' and/or under another license, for
>>> fear of confusion.
>>>
>>> Gray area -- some PMC members can be in that business, as long as the
>>> boundary is clear.
>>>
>>> There was a thing called 'apache extras' for this. Unfortunately, it
>>> was hosted as part of google code, which is defunct. As far as I know,
>>> various plans to replace it have not come to fruition, but I might be
>>> behind.
>>>
>>>
>>>
>>>
>>>
>>>> On Sun, Nov 1, 2015 at 3:04 PM, <xm...@gmail.com> wrote:
>>>> How about maintaining a registry like npm https://www.npmjs.com or https://github.com/jspm/registry where individuals host their modules on github and users can discover them via registry?
>>>>
>>>> Sent from my iPad
>>>>
>>>>> On Nov 1, 2015, at 10:35 AM, Joe Witt <jo...@gmail.com> wrote:
>>>>>
>>>>> " but raises several questions, all pertaining to the relationship of
>>>>> this project with ASF, its ownership and control."
>>>>>
>>>>> ...that is what I'm struggling to respond to as well.
>>>>>
>>>>> It feels like the right path within the ASF is to establish child
>>>>> projects of Apache NiFi. I think we knew we needed to do this anyway
>>>>> as we've mentioned before. It just might be time now...
>>>>>
>>>>> On Sun, Nov 1, 2015 at 1:34 PM, Oleg Zhurakousky
>>>>> <oz...@hortonworks.com> wrote:
>>>>>> Tony, plenty of opinion but so are the questions/concerns.
>>>>>> Managing it on GitHub is perfect, but raises several questions, all pertaining to the relationship of this project with ASF, its ownership and control.
>>>>>> Perhaps some PMCs on the list can shed some light as to how it could be done?
>>>>>>
>>>>>> Cheers
>>>>>> Oleg
>>>>>>
>>>>>> Sent from my iPhone
>>>>>>
>>>>>>> On Nov 1, 2015, at 13:08, Adam Estrada <es...@gmail.com> wrote:
>>>>>>>
>>>>>>> This has been suggested before. It's a great idea!!! I suggest creating a repo on github for NiFi-Processors or something like that. There are many more folks searching through GitHub than on the Apache wikis, IMO. This will inevitably help spread the word...
>>>>>>>
>>>>>>> A
>>>>>>>
>>>>>>> Sent from my iPhone
>>>>>>>
>>>>>>>> On Nov 1, 2015, at 12:55 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> Not very strong opinions on this?
>>>>>>>>> On Oct 30, 2015 10:53 AM, "Joe Witt" <jo...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Tony,
>>>>>>>>>
>>>>>>>>> I completely agree we should do this. A quick github search reveals
>>>>>>>>> there are some nice utilities/processors folks have built for NiFi but
>>>>>>>>> for which they're not necessarily going to submit them as PRs. We
>>>>>>>>> should link to these as much as possible but we should also help folks
>>>>>>>>> understand these aren't 'apache' things and are not of the Apache NiFi
>>>>>>>>> community directly but they are good for users and developers to know
>>>>>>>>> about.
>>>>>>>>>
>>>>>>>>> Perhaps a wiki page linking to these is good provided we have the
>>>>>>>>> above sort of disclaimer and a healthy recognition such references
>>>>>>>>> will become stale...
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>> Joe
>>>>>>>>>
>>>>>>>>>> On Fri, Oct 30, 2015 at 10:48 AM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>>>>> All,
>>>>>>>>>> I wanted to start a conversation about projects that are good for people
>>>>>>>>>> using or developing NiFi, but either can't or don't belong in the source
>>>>>>>>>> tree. This could be due to licensing issues (for example not compatible
>>>>>>>>> (or
>>>>>>>>>> not yet determined if it is compatible (GPL [1])) with the Apache
>>>>>>>>> License),
>>>>>>>>>> or other thought provoking mild concerns like we're discussing on
>>>>>>>>> NIFI-1074
>>>>>>>>>> [2].
>>>>>>>>>>
>>>>>>>>>> I'd like to propose either capturing these on the website or on the wiki
>>>>>>>>> or
>>>>>>>>>> some other approach I didn't think of. I was hoping to find a good
>>>>>>>>>> archetype for this type of documentation in another apache project, but
>>>>>>>>>> didn't find anything I personally liked. If you have seen something you
>>>>>>>>>> like or don't, I'd be interested to hear.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> [1] http://www.apache.org/licenses/GPL-compatibility.html
>>>>>>>>>> [2] https://issues.apache.org/jira/browse/NIFI-1074
>>
Re: "External" extensions
Posted by Tony Kurc <tr...@gmail.com>.
Bryan, I just realized that there is a gap and was wanted to start a
discussion. Other than "let's make things better", I had no specific
expectations.
On Nov 1, 2015 5:27 PM, "Bryan Bende" <bb...@gmail.com> wrote:
> Tony,
>
> Was your original thought here related to the registry idea?
>
> I got the impression you were thinking more about documenting links to
> related projects on the Wiki or Website. We obviously want the registry
> eventually, but these two ideas would be significantly different in effort.
>
> We had started a design page for the registry idea here:
>
> https://cwiki.apache.org/confluence/display/NIFI/Extension+and+Template+Registry
>
> -Bryan
>
>
>
> On Sun, Nov 1, 2015 at 5:14 PM, Oleg Zhurakousky <
> ozhurakousky@hortonworks.com> wrote:
>
> > Well the question still remains unanswered, what relationship those
> > projects have to ASF distribution of NiFi? I seriously doubt that anyone
> on
> > this list suggests that all have to be part of the release. And if they
> are
> > not then they are just individual projects managed in/out of ASF, right?
> >
> > Sent from my iPhone
> >
> > > On Nov 1, 2015, at 17:10, Adam Estrada <es...@gmail.com> wrote:
> > >
> > > The elasticsearch project has a really cool plugin utility that
> > automatically downloads and builds plugins from GitHub, BitBucket, etc...
> > >
> > > Has anyone taken a look at that?
> > >
> > > A
> > >
> > > Sent from my iPhone
> > >
> > >> On Nov 1, 2015, at 3:54 PM, Benson Margulies <bi...@gmail.com>
> > wrote:
> > >>
> > >> ASF policy; a PMC should not be in the business of creating and
> > >> maintaining code 'somewhere else' and/or under another license, for
> > >> fear of confusion.
> > >>
> > >> Gray area -- some PMC members can be in that business, as long as the
> > >> boundary is clear.
> > >>
> > >> There was a thing called 'apache extras' for this. Unfortunately, it
> > >> was hosted as part of google code, which is defunct. As far as I know,
> > >> various plans to replace it have not come to fruition, but I might be
> > >> behind.
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>> On Sun, Nov 1, 2015 at 3:04 PM, <xm...@gmail.com> wrote:
> > >>> How about maintaining a registry like npm https://www.npmjs.com or
> > https://github.com/jspm/registry where individuals host their modules on
> > github and users can discover them via registry?
> > >>>
> > >>> Sent from my iPad
> > >>>
> > >>>> On Nov 1, 2015, at 10:35 AM, Joe Witt <jo...@gmail.com> wrote:
> > >>>>
> > >>>> " but raises several questions, all pertaining to the relationship
> of
> > >>>> this project with ASF, its ownership and control."
> > >>>>
> > >>>> ...that is what I'm struggling to respond to as well.
> > >>>>
> > >>>> It feels like the right path within the ASF is to establish child
> > >>>> projects of Apache NiFi. I think we knew we needed to do this
> anyway
> > >>>> as we've mentioned before. It just might be time now...
> > >>>>
> > >>>> On Sun, Nov 1, 2015 at 1:34 PM, Oleg Zhurakousky
> > >>>> <oz...@hortonworks.com> wrote:
> > >>>>> Tony, plenty of opinion but so are the questions/concerns.
> > >>>>> Managing it on GitHub is perfect, but raises several questions, all
> > pertaining to the relationship of this project with ASF, its ownership
> and
> > control.
> > >>>>> Perhaps some PMCs on the list can shed some light as to how it
> could
> > be done?
> > >>>>>
> > >>>>> Cheers
> > >>>>> Oleg
> > >>>>>
> > >>>>> Sent from my iPhone
> > >>>>>
> > >>>>>> On Nov 1, 2015, at 13:08, Adam Estrada <es...@gmail.com>
> > wrote:
> > >>>>>>
> > >>>>>> This has been suggested before. It's a great idea!!! I suggest
> > creating a repo on github for NiFi-Processors or something like that.
> There
> > are many more folks searching through GitHub than on the Apache wikis,
> IMO.
> > This will inevitably help spread the word...
> > >>>>>>
> > >>>>>> A
> > >>>>>>
> > >>>>>> Sent from my iPhone
> > >>>>>>
> > >>>>>>> On Nov 1, 2015, at 12:55 PM, Tony Kurc <tr...@gmail.com> wrote:
> > >>>>>>>
> > >>>>>>> Not very strong opinions on this?
> > >>>>>>>> On Oct 30, 2015 10:53 AM, "Joe Witt" <jo...@gmail.com>
> wrote:
> > >>>>>>>>
> > >>>>>>>> Tony,
> > >>>>>>>>
> > >>>>>>>> I completely agree we should do this. A quick github search
> > reveals
> > >>>>>>>> there are some nice utilities/processors folks have built for
> > NiFi but
> > >>>>>>>> for which they're not necessarily going to submit them as PRs.
> We
> > >>>>>>>> should link to these as much as possible but we should also help
> > folks
> > >>>>>>>> understand these aren't 'apache' things and are not of the
> Apache
> > NiFi
> > >>>>>>>> community directly but they are good for users and developers to
> > know
> > >>>>>>>> about.
> > >>>>>>>>
> > >>>>>>>> Perhaps a wiki page linking to these is good provided we have
> the
> > >>>>>>>> above sort of disclaimer and a healthy recognition such
> references
> > >>>>>>>> will become stale...
> > >>>>>>>>
> > >>>>>>>> Thanks
> > >>>>>>>> Joe
> > >>>>>>>>
> > >>>>>>>>> On Fri, Oct 30, 2015 at 10:48 AM, Tony Kurc <tr...@gmail.com>
> > wrote:
> > >>>>>>>>> All,
> > >>>>>>>>> I wanted to start a conversation about projects that are good
> > for people
> > >>>>>>>>> using or developing NiFi, but either can't or don't belong in
> > the source
> > >>>>>>>>> tree. This could be due to licensing issues (for example not
> > compatible
> > >>>>>>>> (or
> > >>>>>>>>> not yet determined if it is compatible (GPL [1])) with the
> Apache
> > >>>>>>>> License),
> > >>>>>>>>> or other thought provoking mild concerns like we're discussing
> on
> > >>>>>>>> NIFI-1074
> > >>>>>>>>> [2].
> > >>>>>>>>>
> > >>>>>>>>> I'd like to propose either capturing these on the website or on
> > the wiki
> > >>>>>>>> or
> > >>>>>>>>> some other approach I didn't think of. I was hoping to find a
> > good
> > >>>>>>>>> archetype for this type of documentation in another apache
> > project, but
> > >>>>>>>>> didn't find anything I personally liked. If you have seen
> > something you
> > >>>>>>>>> like or don't, I'd be interested to hear.
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> [1] http://www.apache.org/licenses/GPL-compatibility.html
> > >>>>>>>>> [2] https://issues.apache.org/jira/browse/NIFI-1074
> > >
> >
>
Re: "External" extensions
Posted by Bryan Bende <bb...@gmail.com>.
Tony,
Was your original thought here related to the registry idea?
I got the impression you were thinking more about documenting links to
related projects on the Wiki or Website. We obviously want the registry
eventually, but these two ideas would be significantly different in effort.
We had started a design page for the registry idea here:
https://cwiki.apache.org/confluence/display/NIFI/Extension+and+Template+Registry
-Bryan
On Sun, Nov 1, 2015 at 5:14 PM, Oleg Zhurakousky <
ozhurakousky@hortonworks.com> wrote:
> Well the question still remains unanswered, what relationship those
> projects have to ASF distribution of NiFi? I seriously doubt that anyone on
> this list suggests that all have to be part of the release. And if they are
> not then they are just individual projects managed in/out of ASF, right?
>
> Sent from my iPhone
>
> > On Nov 1, 2015, at 17:10, Adam Estrada <es...@gmail.com> wrote:
> >
> > The elasticsearch project has a really cool plugin utility that
> automatically downloads and builds plugins from GitHub, BitBucket, etc...
> >
> > Has anyone taken a look at that?
> >
> > A
> >
> > Sent from my iPhone
> >
> >> On Nov 1, 2015, at 3:54 PM, Benson Margulies <bi...@gmail.com>
> wrote:
> >>
> >> ASF policy; a PMC should not be in the business of creating and
> >> maintaining code 'somewhere else' and/or under another license, for
> >> fear of confusion.
> >>
> >> Gray area -- some PMC members can be in that business, as long as the
> >> boundary is clear.
> >>
> >> There was a thing called 'apache extras' for this. Unfortunately, it
> >> was hosted as part of google code, which is defunct. As far as I know,
> >> various plans to replace it have not come to fruition, but I might be
> >> behind.
> >>
> >>
> >>
> >>
> >>
> >>> On Sun, Nov 1, 2015 at 3:04 PM, <xm...@gmail.com> wrote:
> >>> How about maintaining a registry like npm https://www.npmjs.com or
> https://github.com/jspm/registry where individuals host their modules on
> github and users can discover them via registry?
> >>>
> >>> Sent from my iPad
> >>>
> >>>> On Nov 1, 2015, at 10:35 AM, Joe Witt <jo...@gmail.com> wrote:
> >>>>
> >>>> " but raises several questions, all pertaining to the relationship of
> >>>> this project with ASF, its ownership and control."
> >>>>
> >>>> ...that is what I'm struggling to respond to as well.
> >>>>
> >>>> It feels like the right path within the ASF is to establish child
> >>>> projects of Apache NiFi. I think we knew we needed to do this anyway
> >>>> as we've mentioned before. It just might be time now...
> >>>>
> >>>> On Sun, Nov 1, 2015 at 1:34 PM, Oleg Zhurakousky
> >>>> <oz...@hortonworks.com> wrote:
> >>>>> Tony, plenty of opinion but so are the questions/concerns.
> >>>>> Managing it on GitHub is perfect, but raises several questions, all
> pertaining to the relationship of this project with ASF, its ownership and
> control.
> >>>>> Perhaps some PMCs on the list can shed some light as to how it could
> be done?
> >>>>>
> >>>>> Cheers
> >>>>> Oleg
> >>>>>
> >>>>> Sent from my iPhone
> >>>>>
> >>>>>> On Nov 1, 2015, at 13:08, Adam Estrada <es...@gmail.com>
> wrote:
> >>>>>>
> >>>>>> This has been suggested before. It's a great idea!!! I suggest
> creating a repo on github for NiFi-Processors or something like that. There
> are many more folks searching through GitHub than on the Apache wikis, IMO.
> This will inevitably help spread the word...
> >>>>>>
> >>>>>> A
> >>>>>>
> >>>>>> Sent from my iPhone
> >>>>>>
> >>>>>>> On Nov 1, 2015, at 12:55 PM, Tony Kurc <tr...@gmail.com> wrote:
> >>>>>>>
> >>>>>>> Not very strong opinions on this?
> >>>>>>>> On Oct 30, 2015 10:53 AM, "Joe Witt" <jo...@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>> Tony,
> >>>>>>>>
> >>>>>>>> I completely agree we should do this. A quick github search
> reveals
> >>>>>>>> there are some nice utilities/processors folks have built for
> NiFi but
> >>>>>>>> for which they're not necessarily going to submit them as PRs. We
> >>>>>>>> should link to these as much as possible but we should also help
> folks
> >>>>>>>> understand these aren't 'apache' things and are not of the Apache
> NiFi
> >>>>>>>> community directly but they are good for users and developers to
> know
> >>>>>>>> about.
> >>>>>>>>
> >>>>>>>> Perhaps a wiki page linking to these is good provided we have the
> >>>>>>>> above sort of disclaimer and a healthy recognition such references
> >>>>>>>> will become stale...
> >>>>>>>>
> >>>>>>>> Thanks
> >>>>>>>> Joe
> >>>>>>>>
> >>>>>>>>> On Fri, Oct 30, 2015 at 10:48 AM, Tony Kurc <tr...@gmail.com>
> wrote:
> >>>>>>>>> All,
> >>>>>>>>> I wanted to start a conversation about projects that are good
> for people
> >>>>>>>>> using or developing NiFi, but either can't or don't belong in
> the source
> >>>>>>>>> tree. This could be due to licensing issues (for example not
> compatible
> >>>>>>>> (or
> >>>>>>>>> not yet determined if it is compatible (GPL [1])) with the Apache
> >>>>>>>> License),
> >>>>>>>>> or other thought provoking mild concerns like we're discussing on
> >>>>>>>> NIFI-1074
> >>>>>>>>> [2].
> >>>>>>>>>
> >>>>>>>>> I'd like to propose either capturing these on the website or on
> the wiki
> >>>>>>>> or
> >>>>>>>>> some other approach I didn't think of. I was hoping to find a
> good
> >>>>>>>>> archetype for this type of documentation in another apache
> project, but
> >>>>>>>>> didn't find anything I personally liked. If you have seen
> something you
> >>>>>>>>> like or don't, I'd be interested to hear.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> [1] http://www.apache.org/licenses/GPL-compatibility.html
> >>>>>>>>> [2] https://issues.apache.org/jira/browse/NIFI-1074
> >
>
Re: "External" extensions
Posted by Oleg Zhurakousky <oz...@hortonworks.com>.
Well the question still remains unanswered, what relationship those projects have to ASF distribution of NiFi? I seriously doubt that anyone on this list suggests that all have to be part of the release. And if they are not then they are just individual projects managed in/out of ASF, right?
Sent from my iPhone
> On Nov 1, 2015, at 17:10, Adam Estrada <es...@gmail.com> wrote:
>
> The elasticsearch project has a really cool plugin utility that automatically downloads and builds plugins from GitHub, BitBucket, etc...
>
> Has anyone taken a look at that?
>
> A
>
> Sent from my iPhone
>
>> On Nov 1, 2015, at 3:54 PM, Benson Margulies <bi...@gmail.com> wrote:
>>
>> ASF policy; a PMC should not be in the business of creating and
>> maintaining code 'somewhere else' and/or under another license, for
>> fear of confusion.
>>
>> Gray area -- some PMC members can be in that business, as long as the
>> boundary is clear.
>>
>> There was a thing called 'apache extras' for this. Unfortunately, it
>> was hosted as part of google code, which is defunct. As far as I know,
>> various plans to replace it have not come to fruition, but I might be
>> behind.
>>
>>
>>
>>
>>
>>> On Sun, Nov 1, 2015 at 3:04 PM, <xm...@gmail.com> wrote:
>>> How about maintaining a registry like npm https://www.npmjs.com or https://github.com/jspm/registry where individuals host their modules on github and users can discover them via registry?
>>>
>>> Sent from my iPad
>>>
>>>> On Nov 1, 2015, at 10:35 AM, Joe Witt <jo...@gmail.com> wrote:
>>>>
>>>> " but raises several questions, all pertaining to the relationship of
>>>> this project with ASF, its ownership and control."
>>>>
>>>> ...that is what I'm struggling to respond to as well.
>>>>
>>>> It feels like the right path within the ASF is to establish child
>>>> projects of Apache NiFi. I think we knew we needed to do this anyway
>>>> as we've mentioned before. It just might be time now...
>>>>
>>>> On Sun, Nov 1, 2015 at 1:34 PM, Oleg Zhurakousky
>>>> <oz...@hortonworks.com> wrote:
>>>>> Tony, plenty of opinion but so are the questions/concerns.
>>>>> Managing it on GitHub is perfect, but raises several questions, all pertaining to the relationship of this project with ASF, its ownership and control.
>>>>> Perhaps some PMCs on the list can shed some light as to how it could be done?
>>>>>
>>>>> Cheers
>>>>> Oleg
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>>> On Nov 1, 2015, at 13:08, Adam Estrada <es...@gmail.com> wrote:
>>>>>>
>>>>>> This has been suggested before. It's a great idea!!! I suggest creating a repo on github for NiFi-Processors or something like that. There are many more folks searching through GitHub than on the Apache wikis, IMO. This will inevitably help spread the word...
>>>>>>
>>>>>> A
>>>>>>
>>>>>> Sent from my iPhone
>>>>>>
>>>>>>> On Nov 1, 2015, at 12:55 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>>
>>>>>>> Not very strong opinions on this?
>>>>>>>> On Oct 30, 2015 10:53 AM, "Joe Witt" <jo...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> Tony,
>>>>>>>>
>>>>>>>> I completely agree we should do this. A quick github search reveals
>>>>>>>> there are some nice utilities/processors folks have built for NiFi but
>>>>>>>> for which they're not necessarily going to submit them as PRs. We
>>>>>>>> should link to these as much as possible but we should also help folks
>>>>>>>> understand these aren't 'apache' things and are not of the Apache NiFi
>>>>>>>> community directly but they are good for users and developers to know
>>>>>>>> about.
>>>>>>>>
>>>>>>>> Perhaps a wiki page linking to these is good provided we have the
>>>>>>>> above sort of disclaimer and a healthy recognition such references
>>>>>>>> will become stale...
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> Joe
>>>>>>>>
>>>>>>>>> On Fri, Oct 30, 2015 at 10:48 AM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>>>> All,
>>>>>>>>> I wanted to start a conversation about projects that are good for people
>>>>>>>>> using or developing NiFi, but either can't or don't belong in the source
>>>>>>>>> tree. This could be due to licensing issues (for example not compatible
>>>>>>>> (or
>>>>>>>>> not yet determined if it is compatible (GPL [1])) with the Apache
>>>>>>>> License),
>>>>>>>>> or other thought provoking mild concerns like we're discussing on
>>>>>>>> NIFI-1074
>>>>>>>>> [2].
>>>>>>>>>
>>>>>>>>> I'd like to propose either capturing these on the website or on the wiki
>>>>>>>> or
>>>>>>>>> some other approach I didn't think of. I was hoping to find a good
>>>>>>>>> archetype for this type of documentation in another apache project, but
>>>>>>>>> didn't find anything I personally liked. If you have seen something you
>>>>>>>>> like or don't, I'd be interested to hear.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> [1] http://www.apache.org/licenses/GPL-compatibility.html
>>>>>>>>> [2] https://issues.apache.org/jira/browse/NIFI-1074
>
Re: "External" extensions
Posted by Adam Estrada <es...@gmail.com>.
The elasticsearch project has a really cool plugin utility that automatically downloads and builds plugins from GitHub, BitBucket, etc...
Has anyone taken a look at that?
A
Sent from my iPhone
> On Nov 1, 2015, at 3:54 PM, Benson Margulies <bi...@gmail.com> wrote:
>
> ASF policy; a PMC should not be in the business of creating and
> maintaining code 'somewhere else' and/or under another license, for
> fear of confusion.
>
> Gray area -- some PMC members can be in that business, as long as the
> boundary is clear.
>
> There was a thing called 'apache extras' for this. Unfortunately, it
> was hosted as part of google code, which is defunct. As far as I know,
> various plans to replace it have not come to fruition, but I might be
> behind.
>
>
>
>
>
>> On Sun, Nov 1, 2015 at 3:04 PM, <xm...@gmail.com> wrote:
>> How about maintaining a registry like npm https://www.npmjs.com or https://github.com/jspm/registry where individuals host their modules on github and users can discover them via registry?
>>
>> Sent from my iPad
>>
>>> On Nov 1, 2015, at 10:35 AM, Joe Witt <jo...@gmail.com> wrote:
>>>
>>> " but raises several questions, all pertaining to the relationship of
>>> this project with ASF, its ownership and control."
>>>
>>> ...that is what I'm struggling to respond to as well.
>>>
>>> It feels like the right path within the ASF is to establish child
>>> projects of Apache NiFi. I think we knew we needed to do this anyway
>>> as we've mentioned before. It just might be time now...
>>>
>>> On Sun, Nov 1, 2015 at 1:34 PM, Oleg Zhurakousky
>>> <oz...@hortonworks.com> wrote:
>>>> Tony, plenty of opinion but so are the questions/concerns.
>>>> Managing it on GitHub is perfect, but raises several questions, all pertaining to the relationship of this project with ASF, its ownership and control.
>>>> Perhaps some PMCs on the list can shed some light as to how it could be done?
>>>>
>>>> Cheers
>>>> Oleg
>>>>
>>>> Sent from my iPhone
>>>>
>>>>> On Nov 1, 2015, at 13:08, Adam Estrada <es...@gmail.com> wrote:
>>>>>
>>>>> This has been suggested before. It's a great idea!!! I suggest creating a repo on github for NiFi-Processors or something like that. There are many more folks searching through GitHub than on the Apache wikis, IMO. This will inevitably help spread the word...
>>>>>
>>>>> A
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>>> On Nov 1, 2015, at 12:55 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>
>>>>>> Not very strong opinions on this?
>>>>>>> On Oct 30, 2015 10:53 AM, "Joe Witt" <jo...@gmail.com> wrote:
>>>>>>>
>>>>>>> Tony,
>>>>>>>
>>>>>>> I completely agree we should do this. A quick github search reveals
>>>>>>> there are some nice utilities/processors folks have built for NiFi but
>>>>>>> for which they're not necessarily going to submit them as PRs. We
>>>>>>> should link to these as much as possible but we should also help folks
>>>>>>> understand these aren't 'apache' things and are not of the Apache NiFi
>>>>>>> community directly but they are good for users and developers to know
>>>>>>> about.
>>>>>>>
>>>>>>> Perhaps a wiki page linking to these is good provided we have the
>>>>>>> above sort of disclaimer and a healthy recognition such references
>>>>>>> will become stale...
>>>>>>>
>>>>>>> Thanks
>>>>>>> Joe
>>>>>>>
>>>>>>>> On Fri, Oct 30, 2015 at 10:48 AM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>>> All,
>>>>>>>> I wanted to start a conversation about projects that are good for people
>>>>>>>> using or developing NiFi, but either can't or don't belong in the source
>>>>>>>> tree. This could be due to licensing issues (for example not compatible
>>>>>>> (or
>>>>>>>> not yet determined if it is compatible (GPL [1])) with the Apache
>>>>>>> License),
>>>>>>>> or other thought provoking mild concerns like we're discussing on
>>>>>>> NIFI-1074
>>>>>>>> [2].
>>>>>>>>
>>>>>>>> I'd like to propose either capturing these on the website or on the wiki
>>>>>>> or
>>>>>>>> some other approach I didn't think of. I was hoping to find a good
>>>>>>>> archetype for this type of documentation in another apache project, but
>>>>>>>> didn't find anything I personally liked. If you have seen something you
>>>>>>>> like or don't, I'd be interested to hear.
>>>>>>>>
>>>>>>>>
>>>>>>>> [1] http://www.apache.org/licenses/GPL-compatibility.html
>>>>>>>> [2] https://issues.apache.org/jira/browse/NIFI-1074
>>>>>
Re: "External" extensions
Posted by Benson Margulies <bi...@gmail.com>.
ASF policy; a PMC should not be in the business of creating and
maintaining code 'somewhere else' and/or under another license, for
fear of confusion.
Gray area -- some PMC members can be in that business, as long as the
boundary is clear.
There was a thing called 'apache extras' for this. Unfortunately, it
was hosted as part of google code, which is defunct. As far as I know,
various plans to replace it have not come to fruition, but I might be
behind.
On Sun, Nov 1, 2015 at 3:04 PM, <xm...@gmail.com> wrote:
> How about maintaining a registry like npm https://www.npmjs.com or https://github.com/jspm/registry where individuals host their modules on github and users can discover them via registry?
>
> Sent from my iPad
>
>> On Nov 1, 2015, at 10:35 AM, Joe Witt <jo...@gmail.com> wrote:
>>
>> " but raises several questions, all pertaining to the relationship of
>> this project with ASF, its ownership and control."
>>
>> ...that is what I'm struggling to respond to as well.
>>
>> It feels like the right path within the ASF is to establish child
>> projects of Apache NiFi. I think we knew we needed to do this anyway
>> as we've mentioned before. It just might be time now...
>>
>> On Sun, Nov 1, 2015 at 1:34 PM, Oleg Zhurakousky
>> <oz...@hortonworks.com> wrote:
>>> Tony, plenty of opinion but so are the questions/concerns.
>>> Managing it on GitHub is perfect, but raises several questions, all pertaining to the relationship of this project with ASF, its ownership and control.
>>> Perhaps some PMCs on the list can shed some light as to how it could be done?
>>>
>>> Cheers
>>> Oleg
>>>
>>> Sent from my iPhone
>>>
>>>> On Nov 1, 2015, at 13:08, Adam Estrada <es...@gmail.com> wrote:
>>>>
>>>> This has been suggested before. It's a great idea!!! I suggest creating a repo on github for NiFi-Processors or something like that. There are many more folks searching through GitHub than on the Apache wikis, IMO. This will inevitably help spread the word...
>>>>
>>>> A
>>>>
>>>> Sent from my iPhone
>>>>
>>>>> On Nov 1, 2015, at 12:55 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>
>>>>> Not very strong opinions on this?
>>>>>> On Oct 30, 2015 10:53 AM, "Joe Witt" <jo...@gmail.com> wrote:
>>>>>>
>>>>>> Tony,
>>>>>>
>>>>>> I completely agree we should do this. A quick github search reveals
>>>>>> there are some nice utilities/processors folks have built for NiFi but
>>>>>> for which they're not necessarily going to submit them as PRs. We
>>>>>> should link to these as much as possible but we should also help folks
>>>>>> understand these aren't 'apache' things and are not of the Apache NiFi
>>>>>> community directly but they are good for users and developers to know
>>>>>> about.
>>>>>>
>>>>>> Perhaps a wiki page linking to these is good provided we have the
>>>>>> above sort of disclaimer and a healthy recognition such references
>>>>>> will become stale...
>>>>>>
>>>>>> Thanks
>>>>>> Joe
>>>>>>
>>>>>>> On Fri, Oct 30, 2015 at 10:48 AM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>>> All,
>>>>>>> I wanted to start a conversation about projects that are good for people
>>>>>>> using or developing NiFi, but either can't or don't belong in the source
>>>>>>> tree. This could be due to licensing issues (for example not compatible
>>>>>> (or
>>>>>>> not yet determined if it is compatible (GPL [1])) with the Apache
>>>>>> License),
>>>>>>> or other thought provoking mild concerns like we're discussing on
>>>>>> NIFI-1074
>>>>>>> [2].
>>>>>>>
>>>>>>> I'd like to propose either capturing these on the website or on the wiki
>>>>>> or
>>>>>>> some other approach I didn't think of. I was hoping to find a good
>>>>>>> archetype for this type of documentation in another apache project, but
>>>>>>> didn't find anything I personally liked. If you have seen something you
>>>>>>> like or don't, I'd be interested to hear.
>>>>>>>
>>>>>>>
>>>>>>> [1] http://www.apache.org/licenses/GPL-compatibility.html
>>>>>>> [2] https://issues.apache.org/jira/browse/NIFI-1074
>>>>
Re: "External" extensions
Posted by xm...@gmail.com.
How about maintaining a registry like npm https://www.npmjs.com or https://github.com/jspm/registry where individuals host their modules on github and users can discover them via registry?
Sent from my iPad
> On Nov 1, 2015, at 10:35 AM, Joe Witt <jo...@gmail.com> wrote:
>
> " but raises several questions, all pertaining to the relationship of
> this project with ASF, its ownership and control."
>
> ...that is what I'm struggling to respond to as well.
>
> It feels like the right path within the ASF is to establish child
> projects of Apache NiFi. I think we knew we needed to do this anyway
> as we've mentioned before. It just might be time now...
>
> On Sun, Nov 1, 2015 at 1:34 PM, Oleg Zhurakousky
> <oz...@hortonworks.com> wrote:
>> Tony, plenty of opinion but so are the questions/concerns.
>> Managing it on GitHub is perfect, but raises several questions, all pertaining to the relationship of this project with ASF, its ownership and control.
>> Perhaps some PMCs on the list can shed some light as to how it could be done?
>>
>> Cheers
>> Oleg
>>
>> Sent from my iPhone
>>
>>> On Nov 1, 2015, at 13:08, Adam Estrada <es...@gmail.com> wrote:
>>>
>>> This has been suggested before. It's a great idea!!! I suggest creating a repo on github for NiFi-Processors or something like that. There are many more folks searching through GitHub than on the Apache wikis, IMO. This will inevitably help spread the word...
>>>
>>> A
>>>
>>> Sent from my iPhone
>>>
>>>> On Nov 1, 2015, at 12:55 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>>
>>>> Not very strong opinions on this?
>>>>> On Oct 30, 2015 10:53 AM, "Joe Witt" <jo...@gmail.com> wrote:
>>>>>
>>>>> Tony,
>>>>>
>>>>> I completely agree we should do this. A quick github search reveals
>>>>> there are some nice utilities/processors folks have built for NiFi but
>>>>> for which they're not necessarily going to submit them as PRs. We
>>>>> should link to these as much as possible but we should also help folks
>>>>> understand these aren't 'apache' things and are not of the Apache NiFi
>>>>> community directly but they are good for users and developers to know
>>>>> about.
>>>>>
>>>>> Perhaps a wiki page linking to these is good provided we have the
>>>>> above sort of disclaimer and a healthy recognition such references
>>>>> will become stale...
>>>>>
>>>>> Thanks
>>>>> Joe
>>>>>
>>>>>> On Fri, Oct 30, 2015 at 10:48 AM, Tony Kurc <tr...@gmail.com> wrote:
>>>>>> All,
>>>>>> I wanted to start a conversation about projects that are good for people
>>>>>> using or developing NiFi, but either can't or don't belong in the source
>>>>>> tree. This could be due to licensing issues (for example not compatible
>>>>> (or
>>>>>> not yet determined if it is compatible (GPL [1])) with the Apache
>>>>> License),
>>>>>> or other thought provoking mild concerns like we're discussing on
>>>>> NIFI-1074
>>>>>> [2].
>>>>>>
>>>>>> I'd like to propose either capturing these on the website or on the wiki
>>>>> or
>>>>>> some other approach I didn't think of. I was hoping to find a good
>>>>>> archetype for this type of documentation in another apache project, but
>>>>>> didn't find anything I personally liked. If you have seen something you
>>>>>> like or don't, I'd be interested to hear.
>>>>>>
>>>>>>
>>>>>> [1] http://www.apache.org/licenses/GPL-compatibility.html
>>>>>> [2] https://issues.apache.org/jira/browse/NIFI-1074
>>>
Re: "External" extensions
Posted by Joe Witt <jo...@gmail.com>.
" but raises several questions, all pertaining to the relationship of
this project with ASF, its ownership and control."
...that is what I'm struggling to respond to as well.
It feels like the right path within the ASF is to establish child
projects of Apache NiFi. I think we knew we needed to do this anyway
as we've mentioned before. It just might be time now...
On Sun, Nov 1, 2015 at 1:34 PM, Oleg Zhurakousky
<oz...@hortonworks.com> wrote:
> Tony, plenty of opinion but so are the questions/concerns.
> Managing it on GitHub is perfect, but raises several questions, all pertaining to the relationship of this project with ASF, its ownership and control.
> Perhaps some PMCs on the list can shed some light as to how it could be done?
>
> Cheers
> Oleg
>
> Sent from my iPhone
>
>> On Nov 1, 2015, at 13:08, Adam Estrada <es...@gmail.com> wrote:
>>
>> This has been suggested before. It's a great idea!!! I suggest creating a repo on github for NiFi-Processors or something like that. There are many more folks searching through GitHub than on the Apache wikis, IMO. This will inevitably help spread the word...
>>
>> A
>>
>> Sent from my iPhone
>>
>>> On Nov 1, 2015, at 12:55 PM, Tony Kurc <tr...@gmail.com> wrote:
>>>
>>> Not very strong opinions on this?
>>>> On Oct 30, 2015 10:53 AM, "Joe Witt" <jo...@gmail.com> wrote:
>>>>
>>>> Tony,
>>>>
>>>> I completely agree we should do this. A quick github search reveals
>>>> there are some nice utilities/processors folks have built for NiFi but
>>>> for which they're not necessarily going to submit them as PRs. We
>>>> should link to these as much as possible but we should also help folks
>>>> understand these aren't 'apache' things and are not of the Apache NiFi
>>>> community directly but they are good for users and developers to know
>>>> about.
>>>>
>>>> Perhaps a wiki page linking to these is good provided we have the
>>>> above sort of disclaimer and a healthy recognition such references
>>>> will become stale...
>>>>
>>>> Thanks
>>>> Joe
>>>>
>>>>> On Fri, Oct 30, 2015 at 10:48 AM, Tony Kurc <tr...@gmail.com> wrote:
>>>>> All,
>>>>> I wanted to start a conversation about projects that are good for people
>>>>> using or developing NiFi, but either can't or don't belong in the source
>>>>> tree. This could be due to licensing issues (for example not compatible
>>>> (or
>>>>> not yet determined if it is compatible (GPL [1])) with the Apache
>>>> License),
>>>>> or other thought provoking mild concerns like we're discussing on
>>>> NIFI-1074
>>>>> [2].
>>>>>
>>>>> I'd like to propose either capturing these on the website or on the wiki
>>>> or
>>>>> some other approach I didn't think of. I was hoping to find a good
>>>>> archetype for this type of documentation in another apache project, but
>>>>> didn't find anything I personally liked. If you have seen something you
>>>>> like or don't, I'd be interested to hear.
>>>>>
>>>>>
>>>>> [1] http://www.apache.org/licenses/GPL-compatibility.html
>>>>> [2] https://issues.apache.org/jira/browse/NIFI-1074
>>
Re: "External" extensions
Posted by Oleg Zhurakousky <oz...@hortonworks.com>.
Tony, plenty of opinion but so are the questions/concerns.
Managing it on GitHub is perfect, but raises several questions, all pertaining to the relationship of this project with ASF, its ownership and control.
Perhaps some PMCs on the list can shed some light as to how it could be done?
Cheers
Oleg
Sent from my iPhone
> On Nov 1, 2015, at 13:08, Adam Estrada <es...@gmail.com> wrote:
>
> This has been suggested before. It's a great idea!!! I suggest creating a repo on github for NiFi-Processors or something like that. There are many more folks searching through GitHub than on the Apache wikis, IMO. This will inevitably help spread the word...
>
> A
>
> Sent from my iPhone
>
>> On Nov 1, 2015, at 12:55 PM, Tony Kurc <tr...@gmail.com> wrote:
>>
>> Not very strong opinions on this?
>>> On Oct 30, 2015 10:53 AM, "Joe Witt" <jo...@gmail.com> wrote:
>>>
>>> Tony,
>>>
>>> I completely agree we should do this. A quick github search reveals
>>> there are some nice utilities/processors folks have built for NiFi but
>>> for which they're not necessarily going to submit them as PRs. We
>>> should link to these as much as possible but we should also help folks
>>> understand these aren't 'apache' things and are not of the Apache NiFi
>>> community directly but they are good for users and developers to know
>>> about.
>>>
>>> Perhaps a wiki page linking to these is good provided we have the
>>> above sort of disclaimer and a healthy recognition such references
>>> will become stale...
>>>
>>> Thanks
>>> Joe
>>>
>>>> On Fri, Oct 30, 2015 at 10:48 AM, Tony Kurc <tr...@gmail.com> wrote:
>>>> All,
>>>> I wanted to start a conversation about projects that are good for people
>>>> using or developing NiFi, but either can't or don't belong in the source
>>>> tree. This could be due to licensing issues (for example not compatible
>>> (or
>>>> not yet determined if it is compatible (GPL [1])) with the Apache
>>> License),
>>>> or other thought provoking mild concerns like we're discussing on
>>> NIFI-1074
>>>> [2].
>>>>
>>>> I'd like to propose either capturing these on the website or on the wiki
>>> or
>>>> some other approach I didn't think of. I was hoping to find a good
>>>> archetype for this type of documentation in another apache project, but
>>>> didn't find anything I personally liked. If you have seen something you
>>>> like or don't, I'd be interested to hear.
>>>>
>>>>
>>>> [1] http://www.apache.org/licenses/GPL-compatibility.html
>>>> [2] https://issues.apache.org/jira/browse/NIFI-1074
>
Re: "External" extensions
Posted by Adam Estrada <es...@gmail.com>.
This has been suggested before. It's a great idea!!! I suggest creating a repo on github for NiFi-Processors or something like that. There are many more folks searching through GitHub than on the Apache wikis, IMO. This will inevitably help spread the word...
A
Sent from my iPhone
> On Nov 1, 2015, at 12:55 PM, Tony Kurc <tr...@gmail.com> wrote:
>
> Not very strong opinions on this?
>> On Oct 30, 2015 10:53 AM, "Joe Witt" <jo...@gmail.com> wrote:
>>
>> Tony,
>>
>> I completely agree we should do this. A quick github search reveals
>> there are some nice utilities/processors folks have built for NiFi but
>> for which they're not necessarily going to submit them as PRs. We
>> should link to these as much as possible but we should also help folks
>> understand these aren't 'apache' things and are not of the Apache NiFi
>> community directly but they are good for users and developers to know
>> about.
>>
>> Perhaps a wiki page linking to these is good provided we have the
>> above sort of disclaimer and a healthy recognition such references
>> will become stale...
>>
>> Thanks
>> Joe
>>
>>> On Fri, Oct 30, 2015 at 10:48 AM, Tony Kurc <tr...@gmail.com> wrote:
>>> All,
>>> I wanted to start a conversation about projects that are good for people
>>> using or developing NiFi, but either can't or don't belong in the source
>>> tree. This could be due to licensing issues (for example not compatible
>> (or
>>> not yet determined if it is compatible (GPL [1])) with the Apache
>> License),
>>> or other thought provoking mild concerns like we're discussing on
>> NIFI-1074
>>> [2].
>>>
>>> I'd like to propose either capturing these on the website or on the wiki
>> or
>>> some other approach I didn't think of. I was hoping to find a good
>>> archetype for this type of documentation in another apache project, but
>>> didn't find anything I personally liked. If you have seen something you
>>> like or don't, I'd be interested to hear.
>>>
>>>
>>> [1] http://www.apache.org/licenses/GPL-compatibility.html
>>> [2] https://issues.apache.org/jira/browse/NIFI-1074
>>
Re: "External" extensions
Posted by Tony Kurc <tr...@gmail.com>.
Not very strong opinions on this?
On Oct 30, 2015 10:53 AM, "Joe Witt" <jo...@gmail.com> wrote:
> Tony,
>
> I completely agree we should do this. A quick github search reveals
> there are some nice utilities/processors folks have built for NiFi but
> for which they're not necessarily going to submit them as PRs. We
> should link to these as much as possible but we should also help folks
> understand these aren't 'apache' things and are not of the Apache NiFi
> community directly but they are good for users and developers to know
> about.
>
> Perhaps a wiki page linking to these is good provided we have the
> above sort of disclaimer and a healthy recognition such references
> will become stale...
>
> Thanks
> Joe
>
> On Fri, Oct 30, 2015 at 10:48 AM, Tony Kurc <tr...@gmail.com> wrote:
> > All,
> > I wanted to start a conversation about projects that are good for people
> > using or developing NiFi, but either can't or don't belong in the source
> > tree. This could be due to licensing issues (for example not compatible
> (or
> > not yet determined if it is compatible (GPL [1])) with the Apache
> License),
> > or other thought provoking mild concerns like we're discussing on
> NIFI-1074
> > [2].
> >
> > I'd like to propose either capturing these on the website or on the wiki
> or
> > some other approach I didn't think of. I was hoping to find a good
> > archetype for this type of documentation in another apache project, but
> > didn't find anything I personally liked. If you have seen something you
> > like or don't, I'd be interested to hear.
> >
> >
> > [1] http://www.apache.org/licenses/GPL-compatibility.html
> > [2] https://issues.apache.org/jira/browse/NIFI-1074
>
Re: "External" extensions
Posted by Joe Witt <jo...@gmail.com>.
Tony,
I completely agree we should do this. A quick github search reveals
there are some nice utilities/processors folks have built for NiFi but
for which they're not necessarily going to submit them as PRs. We
should link to these as much as possible but we should also help folks
understand these aren't 'apache' things and are not of the Apache NiFi
community directly but they are good for users and developers to know
about.
Perhaps a wiki page linking to these is good provided we have the
above sort of disclaimer and a healthy recognition such references
will become stale...
Thanks
Joe
On Fri, Oct 30, 2015 at 10:48 AM, Tony Kurc <tr...@gmail.com> wrote:
> All,
> I wanted to start a conversation about projects that are good for people
> using or developing NiFi, but either can't or don't belong in the source
> tree. This could be due to licensing issues (for example not compatible (or
> not yet determined if it is compatible (GPL [1])) with the Apache License),
> or other thought provoking mild concerns like we're discussing on NIFI-1074
> [2].
>
> I'd like to propose either capturing these on the website or on the wiki or
> some other approach I didn't think of. I was hoping to find a good
> archetype for this type of documentation in another apache project, but
> didn't find anything I personally liked. If you have seen something you
> like or don't, I'd be interested to hear.
>
>
> [1] http://www.apache.org/licenses/GPL-compatibility.html
> [2] https://issues.apache.org/jira/browse/NIFI-1074