For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 6 replies, 4 voices, and was last updated 22 years ago by
.
-
Posts
-
I just downloaded release 3.0 M6 Integration Build I20040121 and was not able to install the version of myeclipse – reason given that the version was not correct. Are there specific integration builds that are supported and others that are not? Is there a work around that will allow me to install with this build?
FYI, I downloaded that version as the suggested version (stbability and performance) for running on Mac OS X 10.3.2
Thanks in advance.
I don’t think you can just use nightly or integration builds, I believe you need to use the Stream Stable builds for the M6 release
http://download.eclipse.org/downloads/drops/S-3.0M6-200312182000/index.php, try that and see if it worked.I just checked the release notes for Mac and it points to the stream stable M6 build that I linked to above… where did you see the link to the integration build for that date?
The message below from is from Andre Weinand who is primarily responsible (or at least very involved) for OS X versions of Eclipse——————————
Eclipse 3.0 M4 or integration build I20040121 (preferred).
(the only problem I have with the integration build is that sometimes
you need to remove the .config folder in the Eclipse directory in
order to be able to run newly installed plugins).–andre
BTW: There will be a BoF for Mac OS X users at next week’s EclipseCon
2004 (www.eclipsecon.org)
And I’ll be there, too.I installed 3.7RC2 on Integration Build I20040121 (Windows). The install worked, but I get a ClassNotFoundException for de.bb.jsp.JspCC when using JSPs, though the corresponding library (bb_jsp.jar) is there.
Any ideas? M6 is just too buggy and slow, I20040121 is way better!
Michael
Guys since the 3.x release of MyEclipse is developed against/tested against a particular release of Eclipse 3.x, and given that 3.x is under heavy development, I think its pretty reasonable to say that on any given integration or nightly build something might (and probably does) change that will break MyEclipse’s ability to work with it. If you want to use MyEclipse with Eclipse 3.x, then the only thing I can tell you to do is follow the MyEclipse installation guidelines (using the M6 build) and not Eclipse’s release suggestions.
No doubt that some of the newer integration builds are better than M6, but the MyEclipse team can’t predict or develope against potential future changes in the Eclipse codebase.
I will make Scott aware of your request (incase he knows what may help you get working with it) but I can’t promise anything.
All,
Sorry, but we only support the milestone builds. The 3.0 codebase changes greatly from build to build and we simply don’t have the resources to build and test on the “flavor of the day” builds. They might work and they might not. Part of the problem with being on the bleeding edge of the Eclipse builds is that sometimes the blood is yours. 😉
