Community
Participate
Working Groups
Build Identifier: v6.1 build 7600 see link http://stackoverflow.com/questions/8111765/java-why-is-long-value-in-if-statement-validated-wrong Reproducible: Always Steps to Reproduce: 1.see http://stackoverflow.com/questions/8111765/java-why-is-long-value-in-if-statement-validated-wrong 2. 3.
this is so weird and im sure the problem is on my side. we are talking about the good-old-if-statement..:) Sorry for any inconvenience but a saw no other way then bugreport it
2 movies showing the phenomenology: http://www.youtube.com/watch?v=DFcRfPErfik http://www.youtube.com/watch?v=NEC04-kLQBE Notice how Expression evaluation show false for diffHours > 3L
If any of you like, Im willing to open a remote control session using tightVnc or any tool you prefers to resolve this issue. My private phone is +46761997948 SWEDEN
First look makes me wonder what your auto build setting is? If auto-build is off as you make changes and save there is no HCR (Hot Code Replace) occurring, and I notice in the videos once you step into the if statement (as it appears) you have actually stepped out of scope of the method - the reason the expression(s) fail to update. If you expand the error node for the expression, what does it say?
I think the build settings where set to automatic, i cannot open eclipse anymore the Maven indexing is freezing everything on startup. I never toggle the build setting just use default. The eclipse installation must have been compromised because everything went downhill since i posted this bug. now running Indigo i will work with the same code so if this happen again i will post. I tried to reproduce the bug in Indigo but everything works as supposed. (In reply to comment #4) > First look makes me wonder what your auto build setting is? If auto-build is > off as you make changes and save there is no HCR (Hot Code Replace) occurring, > and I notice in the videos once you step into the if statement (as it appears) > you have actually stepped out of scope of the method - the reason the > expression(s) fail to update. > > If you expand the error node for the expression, what does it say?
> I tried to reproduce the bug in Indigo but everything works as supposed. Closing as worksforme then...
