I don't believe there is any code in nifi-web-ui that should be generating 
these sort of errors. Could be one of the JSPs that get compiled at build time 
which I believe is what Tony is eluding to.

I also notice in your environment is an Oracle JVM on your path but an openjdk 
for your JAVA_HOME. This doesn't necessarily show a problem, but let us know if 
your seeing anything when you build. Thanks!

Matt

Sent from my iPhone

> On Dec 6, 2015, at 6:13 PM, Tony Kurc <[email protected]> wrote:
> 
> @Andre: do you see a lot of these when you build?
> 
> [WARNING] Unable to autodetect 'javac' path, using 'javac' from the
> environment.
> 
> 
>> On Sun, Dec 6, 2015 at 6:08 PM, Tony Kurc <[email protected]> wrote:
>> 
>> Going to try this:
>> tkurc@computer:~/nifi/$ export
>> JAVA_HOME=/usr/lib/jvm/java-1.7.0-openjdk-amd64/jre
>> tkurc@computer:~/nifi/$ mvn -version
>> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
>> 2015-04-22T07:57:37-04:00)
>> Maven home: /opt/maven/apache-maven-3.3.3
>> Java version: 1.7.0_85, vendor: Oracle Corporation
>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "linux", version: "3.13.0-68-generic", arch: "amd64", family:
>> "unix"
>> 
>> 
>>> On Sun, Dec 6, 2015 at 6:06 PM, Joe Witt <[email protected]> wrote:
>>> 
>>> I am not seeing this.  Built on 8.  Run on 7.
>>> 
>>> But def want to help get to the bottom of it.
>>>> On Dec 6, 2015 5:59 PM, "Matt Burgess" <[email protected]> wrote:
>>>> 
>>>> I couldn't find the reference on a quick internet search; instead they
>>> say
>>>> it has something to do with non-transitive Comparators and/or the new
>>>> TimSort implementation. I would think if that were the case we would've
>>>> seen this a lot earlier though; not everyone is having this problem
>>> right?
>>>> 
>>>> Sent from my iPhone
>>>> 
>>>>> On Dec 6, 2015, at 5:49 PM, Tony Kurc <[email protected]> wrote:
>>>>> 
>>>>> @Matt, I'm compiling now too
>>>>> 
>>>>>> On Sun, Dec 6, 2015 at 5:46 PM, Matt Burgess <[email protected]>
>>>> wrote:
>>>>>> 
>>>>>> Yes sir. I think they changed the way constructor bytecodes are
>>>> generated
>>>>>> in Java 8, so if you want to run on Java 8 you're supposed to
>>> compile on
>>>>>> Java 8 (even if you also want a Java 7 target). I will try to find a
>>>>>> reference on this to make sure I'm not entirely crazy, but I'm pretty
>>>> sure
>>>>>> I've run into this before.
>>>>>> 
>>>>>> Sent from my iPhone
>>>>>> 
>>>>>>> On Dec 6, 2015, at 5:35 PM, Tony Kurc <[email protected]> wrote:
>>>>>>> 
>>>>>>> @Matt - so I could try to replicate by setting my JAVA_HOME to a 7
>>> jdk
>>>>>> when
>>>>>>> I build, then when I launch, use an 8 jre? I'll give that a try
>>>>>>> 
>>>>>>>> On Sun, Dec 6, 2015 at 5:31 PM, Matt Burgess <[email protected]>
>>>>>> wrote:
>>>>>>>> 
>>>>>>>> I think I've seen that with Java 7 compiled code (not compiled
>>> with 8
>>>>>>>> using 7 target) loaded on a Java 8 VM.
>>>>>>>> 
>>>>>>>> Sent from my iPhone
>>>>>>>> 
>>>>>>>>> On Dec 6, 2015, at 4:58 PM, Andre <[email protected]> wrote:
>>>>>>>>> 
>>>>>>>>> Matt,
>>>>>>>>> 
>>>>>>>>> $ mvn -version
>>>>>>>>> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
>>>>>>>>> 2015-11-11T03:41:47+11:00)
>>>>>>>>> Maven home: /usr/local/apache-maven-3.3.9
>>>>>>>>> Java version: 1.7.0_91, vendor: Oracle Corporation
>>>>>>>>> Java home: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.91.x86_64/jre
>>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>>> OS name: "linux", version: "2.6.32-573.8.1.el6.x86_64", arch:
>>>> "amd64",
>>>>>>>>> family: "unix"
>>>>>>>>> 
>>>>>>>>> Yes. It did happen with the RC1 as well.
>>>>>>>>> 
>>>>>>>>> System is a centos development box with nothing in special, all
>>>>>>>>> packages, except maven are installed from Centos & EPEL repos.
>>> Maven
>>>>>>>>> installed from TGZ.
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> On Mon, Dec 7, 2015 at 12:26 AM, Matt Gilman <
>>>> [email protected]
>>>>>>> 
>>>>>>>> wrote:
>>>>>>>>>> Andre,
>>>>>>>>>> 
>>>>>>>>>> Can you confirm that your up to date? And then run 'mvn
>>> -version' to
>>>>>>>>>> provide your environment? Also do you see them same thing running
>>>> the
>>>>>>>> 0.4.0
>>>>>>>>>> RC candidate that was sent out yesterday?
>>>>>>>>>> 
>>>>>>>>>> Thanks!
>>>>>>>>>> 
>>>>>>>>>> Matt
>>>>>>>>>> 
>>>>>>>>>>> On Sun, Dec 6, 2015 at 4:19 AM, Andre <[email protected]>
>>>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> Hi there,
>>>>>>>>>>> 
>>>>>>>>>>> I am wondering if anyone else is facing the following error when
>>>>>>>>>>> starting nifi 0.4.0 compiled from master??
>>>>>>>>>>> 
>>>>>>>>>>> 2015-12-06 19:58:31,325 WARN [main]
>>>>>>>>>>> org.eclipse.jetty.webapp.WebAppContext Failed startup of context
>>>>>>>>>>> o.e.j.w.WebAppContext@2c9af8c3
>>> {/nifi,file:/home/user/development/nifi/nifi-assembly/target/nifi-0.4.0-SNAPSHOT-bin/nifi-0.4.0-SNAPSHOT/work/jetty/nifi-web-ui-0.4.0-SNAPSHOT.war/webapp/,STARTING}{./work/nar/framework/nifi-framework-nar-0.4.0-SNAPSHOT.nar-unpacked/META-INF/bundled-dependencies/nifi-web-ui-0.4.0-SNAPSHOT.war}
>>>>>>>>>>> java.lang.IllegalArgumentException: Comparison method violates
>>> its
>>>>>>>>>>> general contract!
>> 
>> 

Reply via email to