nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Witt <joe.w...@gmail.com>
Subject Re: nifi fails build on CentOS 7
Date Wed, 04 Nov 2015 00:50:36 GMT
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 <trkurc@gmail.com> wrote:
> Huzzah
>
> On Tue, Nov 3, 2015 at 7:48 PM, Jeff <j.007ba7@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 <trkurc@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.007ba7@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 <trkurc@gmail.com> wrote:
>> >>>
>> >>> Jeff,
>> >>> Were you able to run that find command?
>> >>>
>> >>> On Tue, Nov 3, 2015 at 7:09 PM, Jeff <j.007ba7@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 <joe.witt@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
>> >>>>>>>>
>> >>>>>>
>> >>>>
>> >>>>
>> >>
>> >>
>>
>>

Mime
View raw message