For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 18 replies, 11 voices, and was last updated 21 years, 1 month ago by
.
-
Posts
-
Are you planning to release a version of MyEclipse 3.8.x that supports the upcoming Eclipse 3.1 final release?
Cmon! You get a far as 3.1M7 then drop support in the main branch … thats crazy? 😕
3.1 final candidates are out, and AFAIK they are meant to be API compatbile with M7 anyway. Ill bet it can run on final builds with trivial work, if any at all.
*Is* there a real reason? If so, it it technical, or a deliberate business-oriented “no-can-do”?
Anyway, if you go this way, its your own loss. In a day or two, you wont be compatbile with the latest stable release of Eclipse.
AFAIK they are meant to be API compatbile with M7 anyway.
They are *meant* to be, but they are not.
Ill bet it can run on final builds with trivial work, if any at all.
And you would be greatly mistaken. Non-plugin developers typically underestimate how much Eclipse changes their APIs and how drastic those changes can be.
*Is* there a real reason? If so, it it technical, or a deliberate business-oriented “no-can-do”?
It’s technical, due to the amount of effort involved with each M or RC build that brings breaking changes. RC1 broke a lot of things and it will take us a bit of time to correct and validate. It’s certainly not that we don’t want to provide a 3.1 solution; we’re working on a port of 4.0M2 right now. It is just taking some time.
Anyway, if you go this way, its your own loss. In a day or two, you wont be compatbile with the latest stable release of Eclipse.
Trust me, it’s not by choice. But, we’ve got 180 plugins built on top of a platform that is (or was) changing from build to build. At some point it just isn’t worth it to port to the “build of the week” as it’s hugely disruptful to our development efforts. Now that the platform has finally stabilized, we’re doing everything we can to get a 4.0M2 build for 3.1 out the door as quickly as possible.
Very well, actually. It’s being tested by our QA board (external user group) right now. We plan on rolling it out shortly after 3.1 final, so we can test just a little more on the *final* build as well. Definately next week though.
Note: ME4.0 M2 has just been released for Eclipse 3.1 GA. It has all of the base ME 3.8.4 features plus many new features such as better JSF and Hibernate3 support, UML, and Spring support.
How stable is 4.0M2 compared to 3.8.4 for Eclipse 3.1M6 (considering only the ‘old’ features)? I think I read that 4.0M1 did not incorporate all bugfixes from your 3.8.x branch – are those fixes integrated into 4.0M2?
Best regards
SoerenSoeren,
Great question. It’s more stable than 3.8.4 for 3.1M6 and *does* incorporate all fixes from 3.8.4 along with a ton of new features. If you like 3.8.4 on M6, you won’t have any problems on 4.0M2 for 3.1.
That said, since you have to install a new Eclipse 3.1 anyway, just keep the old install and put the new one in place “in parallel”. That way you can try it out without risk to your current development setup.
Scott, I am not really interested in the *new* features in MyEclipse 4.0 at this time but I am strongly interested in knowing how stable the *old* features are in MyEclipse 4.0M2 on Eclipse 3.1 final.
If you could confirm that those features are positively stable and can recommend everyone interested in Eclipse 3.1 to use MyEclipse 4.0M2, I think you’ll see everyone rush in. If you can’t make that recommendation, then we can’t use 4.0M2 either and you’ll see little interest in 4.0M2 as well as being hounded by us until MyEclipse 3.8.4 for Eclipse 3.1 is released.
I am strongly interested in knowing how stable the *old* features are in MyEclipse 4.0M2 on Eclipse 3.1 final.
We understand completely. The problem with releasing 3.8.4 for 3.1 is that it required just as much porting work as releasing 4.0M2 did. So, we chose to focus on delivering 4.0M2 with the understanding that it would be production worthy on Eclipse 3.1 for the 3.8.4 feature set (no regresssions + many fixes) and be at a solid “milestone” level on the new, leading edge features. 4.0M2 for 3.1 went through a full, production QA cycle. Additionally, we’ve already had a few thousand downloads and no one has reported any showstoppers, either with the new or old functionality. Historically, if there’s a showstopper, we’ve always heard about it within the first few hundred downloads. Given all that, we’re comfortable recommending the core 3.8.4 feature set within it for production use. Additionally, the new features should be quite stable, just incomplete at this point. Please let us know if you determine this not to be the case, but we think you’ll like the build. If a showstopper is found, we’ll turn an update build immediately.
