- This topic has 16 replies, 10 voices, and was last updated 9 years, 7 months ago by
.
-
Posts
-
Hello:
While running our web application, in the Debug Perspective, I am unable to get any debug expression to evaluate. I can see the variables and their values but I am unable to see anything in the expression view/pane.
Please check out the attached image.
Thanks,
Biju
P.S: It would be nice if you can increase the size of the subject.Biju,
Thank you for raising it. I could replicate the issue at my end. I have filed a PR for the dev team to look into it.
Sorry for inconvenience caused.
All,
Our dev team has targeted this issue to MyEclipse 2014 SR1 release. We will do our best to get the fix out with MyEclipse 2014 SR1 release, which is due to release soon.
Sorry for inconvenience caused.
kvanapal,
I’m afraid we don’t yet have an update on the 2014 SR1 release at this point. We have currently fixed this bug on the 2015 stream and are in the process of porting the fix over to the 2014 stream, we’re looking into options to make this fix available asap and I will keep you posted.
Apologize for the inconvenience caused.
I am having the same issue and the debug feature is not that useful without the runtime expression evaluation feature 🙁 Last time I was told MyEclipse Blue edition is the one which will get immediate fixes compared to Standard Edition and that is the reason I upgraded my license. So when is this going to be fixed? Any dates available?
Brian:
It seems like I have been waiting forever to get this fix. It is totally irresponsible on your team side to entice everyone to use the new version and then not provide or fix a bug that is a fundamental need when debugging an issue. A huge handicap indeed!
I hope you give this utmost importance before people like me start using other products and recommend the same to our company.
Thanks,
BijuBiju,
I agree, not being able to provide a fix for a fundamental issue like this one is frustrating.
It is frustrating to the developer team as well but we’ve moved to a point in development where we have no option but to push all fixes to the upcoming 2015 release.
With 2015 and all future releases we’ll be moving to a model where we can release at a much faster pace; unfortunately the groundwork required here makes porting these fixes backwards problematic.
Please bear with us during this transition. See https://www.genuitec.com/forums/topic/2014-issue-status/ for more details.
The other post reads “a fix for these issues will be available in the 2015 EA release due towards the end of May 2014. A 2014 SR1 release, to be released post 2015 EA will include fixes for these issues…”
Why would you push an EA release in a hurry when the existing release has a bunch of problems that needs fix.
Shouldn’t it be the other way around?
We certainly do not do this at our work!Cheers,
BijuThis is not very serious.
Wasn’t 2014 SR1 supposed to be released yet?
There are lot of people stuck with these inconceivable fails, specially JPA performance issue refreshing model.So I got this e-mail from your sales to renew the license in the next 50 days.
Are you kidding me?
What support can I expect from a company that does not support basic functions in its IDE?
This despite the bug being disclosed several months in advance.
You care more about floating a new version of the product rather than fix an existing version so you can sell it.So, what have we been doing about it?
We are testing out several other options and will soon make a decision to switch and cut out the 50+ MyEclipse licenses that we use currently.Sad it needs to get to this and now we have to get used to another product!
Biju,
Several of our customers have shifted to 2015 CI stream . We’ve made 3 releases there so far, releases have been spread by around 3 weeks. We’ve therefore been focusing on getting CI to a GA asap. For current context, the debug issue and the JPA issue have both been fixed in CI 1. Give the fundamental changes in 2015 (especially in the server area) 2015 is really the best version of MyEclipse to use (we do have some versions of WebSphere servers missing which we are adding progressively).
As before, I completely understand your frustration with this problem. Is shifting to 2015 an option for your team?
I will take your concerns up with my management and executive team nevertheless.
