[jccartwright]

Hello All,

I’m trying to install 3.84 w/ eclipse3.1RC2 and the installation keeps complaining about the version – is it really limited to eclipse 3.1M7 and will not work w/ later 3.1 releases?

If so, when is a version that works w/ 3.1 expected?

Thanks!

— john

[Unknown Author]

Same here, M7 was the last release before the RCn series… Is it really incompatible or is this an overly agressive limitation?

[zapa]

same here …

newest download for 3.1 does not work with RC2 that’s for sure . I don’t think it’s a limitation as they specify it’s for M7 and LATER releases .

Hopefully will be fixed soon as I have the 30 days free membership and I’d like to make up my mind if I’m buying

[Scott Anderson]

newest download for 3.1 does not work with RC2 that’s for sure ..

That is correct; it works *only* with 3.1M7 due to changes in the underlying Eclipse APIs.

I don’t think it’s a limitation as they specify it’s for M7 and LATER releases

I double checked and on the downloads page we have stated: “This release will only work with Eclipse 3.1 M7,…”. Is there somewhere else on the website we need to correct so as not to confuse others? If you can send us a link I’ll be sure it gets changed right away.

Hopefully will be fixed soon as I have the 30 days free membership and I’d like to make up my mind if I’m buying

What we’d encourage you to do is to evaluate our production release (3.8.4) or our developmental milestone release (4.0Mx) on Eclipse 3.0.2. They will give you a very good indication of where the product capabilities are now and where they’ll be very soon. After the 4.0M2 release in a few days, we’ll be porting and updating the build for the latest release of Eclipse 3.1. Given the timing, we’ll likely have a 4.0M2 release for Eclipse 3.1 right around the time that 3.1 becomes final.

[jccartwright]

Thanks, Scott. The website says clearly that the release I downloaded was intended for eclipse3.1M7. I was simply hoping that M7 was a *minimum* and not an absolute requirement.

It wasn’t entirely clear to me however when you expect to have a 3.8.4 that runs against the 3.1 eclipse release. I assume that since we’re now on RC3, the APIs are frozen.

I’m hope there’s not too long a period that I have to choose between myeclipse (which I really like!) and eclipse 3.1.

Thanks again!

— john

[Scott Anderson]

John,

I’m hope there’s not too long a period that I have to choose between myeclipse (which I really like!) and eclipse 3.1.

We’re doing our best to make sure that time is as small as possible, and smaller than any other J2EE IDE on the market.
Give us a couple of weeks and we’ll have a 4.0 milestone on 3.1 that should be stable enough for “real use”.

[Rick Ross]

I think you guys are between a rock and a hard place on this issue of staying current with near-final developmental releases of Eclipse. All things considered, however, it is probably wiser for you to remove the version checking code that PREVENTS installations and instead have it trigger a clear WARNING that continuing installation implies use of an untested and not officially supported environment.

People using Eclipse are clearly people interested in innovation, so the latest version has a lot of appeal to them – even a test version. You don’t serve your own interests well by having MyEclipseIDE be difficult to install. There’s no chance whatsoever that I am going to use Eclipse 3.0.x in order to try your latest version, but having done the manual install I have been enjoying pretty good success using MyEclipseIDE with 3.1RC2.

Letting users proceed with the install will get you a lot more feedback on where real problems are, anyway. Let your intrepid users click past a warning, do the install, and then hope they will be kind enough to respect that they went into “caveat emptor” territory by doing so. They can be the leading edge of your quality assurance effort.

Regards,
Rick Ross

[Scott Anderson]

All things considered, however, it is probably wiser for you to remove the version checking code that PREVENTS installations and instead have it trigger a clear WARNING that continuing installation implies use of an untested and not officially supported environment.

Rick, the issue isn’t that it’s untested; I wish that it was. The probme is that we’ve loaded the code up and there are several compilation problems in multiple plugins. So, we *know* portions of the product are broken by the API changes. However, for the boldest out there, they may download our manual installation zip archive which will allow them to install on any configuration they wish. The installation instructions are quite trivial and available here:
http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-3424.html

There’s no chance whatsoever that I am going to use Eclipse 3.0.x in order to try your latest version, but having done the manual install I have been enjoying pretty good success using MyEclipseIDE with 3.1RC2.

That’s very good to hear. Perhaps the problems are more in “fringe” functionalities, which would be great. Unfortunately, we can’t really respin a build of the 3.8.4 installers, due to the time involved – especially since we’re wrapping up 4.0M2. Our next step is to port 4.0M2 to Eclipse 3.1 and then maintain 3.1 as our “first ship” platform going forward. We checked with our user base and they seem much more interested in a 4.0 on 3.1 than a 3.8.4 on 3.1, at this point.

They can be the leading edge of your quality assurance effort.

Actually, that’s exactly why we started milestoning builds with 4.0 (in the downloads section, manual installer only). Users like to get the tools as fast as possible and they’re used to it since Eclipse does the same thing. The process seems to be going well, thus far and the users are great at helping us find problems and suggest improvements, as they’ve always been.

Currently, doing some final test this weekend on 4.0M2 for 3.0.2 and once released we expect to ship 4.0M2 for 3.1 within a week or so. Trust us, we’re doing our very best to support all our existing customers on Eclipse 3.0 (big companies move more slowly than individuals), as well as all the early adopters on 3.1. It’s just been tough given the volume of breaking code changes in 3.1 thus far. But, we’re sort of used to how it goes since we managed to survive the Eclipse 2.0 to 3.0 changes. 🙂

When we get 4.0M2 for Eclipse 3.1 available, please give it a look. We’re really excited about where the product is going and the additional tools available over 3.8.4 are really amazing (to me at least ;-).

[Author]

Posts