- This topic has 11 replies, 4 voices, and was last updated 14 years, 11 months ago by
.
-
Posts
-
I am sorry, but throw away MyEclipse and I am back to the old Eclipse version with the basic plugin’s that I need.
I am use MyEclipse for a long time now, and noticed that last few years that quality is getting poor poor… realllly poor… Every release I get more bugs and I can’t work with and won’t accept it…How come that when I rename a simple class:
public class EmptyFormsValidatorPresenter implements HasItems<FormSimple>looks like this after a simple rename of the class:
public class EntriesEmptyFormsValidatorPresenter implements HaEntriesFormsItemsnal FormButtonEntries entries;public EntriesEmptyFormsValidatorPresenter(final FormButEntriesFormsItemsnotNull(getClass(), entries, “Entries”);
this.entries = entries;
}EntriesEmptyFormsValidatorPresenter() {
this.eEntriesFormsItemsimple get(final int index) {
return this.entries.get(index).getFormViewerNode().getViewer().getForm();
}As you can see, it completely f**cks up my code, which cost me quite some time to correct.
Yep, I did clean my workspace a few times, and I am not a beginner here, So don’t even start that “it will probably be me”… I am experiencing more bugs and bugs on every release and get very angry when a paying product cost me time….
Also when I start a piece of javadoc and start with @… and in the meantime continue typing, I get an error popup…I am back to the old fashion way and I can tell you: now working for a day with it: works fine, no problem yet… (The myeclipse bugs I got about every 12 hours)….
I get a bit irritated by the fact that MyEclipse is bringing out a new version already while the other version still have all those bugs… :(… In the past, this wasn’t like that… So I dont’ know what you guys changed, but I can tell you: it’s not goodd…
Good luck, my membership will not be renewed… (Many of my team did this already but for me it always worked fine….. tilll now… )….
Ed,
I can understand why this renaming issue is frustrating. I tried several different configurations to try to reproduce it but could not. I also search Eclipse’s Bugzilla and found that this has occurred before in several bugs against JDT. Here is the one that looks identical (to me) to what you’re reporting. You’ll note that it was resolved as a duplicate of another bug and that bug was resolved as WORKSFORME. That just goes to show that these issues are extremely difficult to reproduce, which is why Brian asked if you could send in an example. If you can get one that is reproducible then we can likely get it fixed.
From your final post you mentioned what looks like code being reformatted after a rename. There’s actually nothing that is added in MyEclipse to the refactoring support in Eclipse. We don’t do anything with rename or cause source to format. All those functions come from Eclipse itself, which is why all the stack dumps you’ve posted don’t show any MyEclipse code in the stack.
Of course, we understand that when you’re using MyEclipse you expect everything to work correctly all the time. We honestly do too, and we do our best to ensure that is the case by asking our users to report bugs so we can get them fixed. However, sometimes the bugs simply aren’t ours, as in this case, but we’ll still work to get them resolved. But we would at least like you to understand that not everything is our fault.
–Scott
MyEclipse SupportEd,
I can understand why this renaming issue is frustrating. I tried several different configurations to try to reproduce it but could not. I also search Eclipse’s Bugzilla and found that this has occurred before in several bugs against JDT. Here is the one that looks identical (to me) to what you’re reporting. You’ll note that it was resolved as a duplicate of another bug and that bug was resolved as WORKSFORME. That just goes to show that these issues are extremely difficult to reproduce, which is why Brian asked if you could send in an example. If you can get one that is reproducible then we can likely get it fixed.
From your final post you mentioned what looks like code being reformatted after a rename. There’s actually nothing that is added in MyEclipse to the refactoring support in Eclipse. We don’t do anything with rename or cause source to format. All those functions come from Eclipse itself, which is why all the stack dumps you’ve posted don’t show any MyEclipse code in the stack.
Of course, we understand that when you’re using MyEclipse you expect everything to work correctly all the time. We honestly do too, and we do our best to ensure that is the case by asking our users to report bugs so we can get them fixed. However, sometimes the bugs simply aren’t ours, as in this case, but we’ll still work to get them resolved. But we would at least like you to understand that not everything is our fault.
–Scott
MyEclipse Support
