- This topic has 11 replies, 7 voices, and was last updated 19 years, 7 months ago by
.
-
Posts
-
Guys,
How soon we will have MyEclipse supporting 3.1M7 ?
We are using eclipse 3.1 M6 and its very buggy so want to upgrade to M7 asap. Myeclipse compatibility is critical for this move.
Thanks,
Ashisheclipse.org states that the M6 release meant a freez of API. I guess this means, IN THEORY, that myeclipse should also be compatible with M7. But I guess that’s not the case 🙂
Manual install of 3.8.4 for 3.1M6 seems to work OK with 3.1M7. The executable install on Linux doesnt seem to want to install.
It’s not really OK with M7. We’re prepping an M7 build of 3.8.4 today and will have it available as early as Tuesday morning.
For the 4.0 versions, we’ll have 3.1 support in the Milestone 2 build, now that the Eclpse team has frozen the APIs for 3.1
As of now, the download states that it has M7 compatibility, but looking at my configuration I see an error (when I attempt to install a new feature — this doesn’t show up in my configuration management screen, ONLY when I select a new feature to install in the update manager):
The current configuration contains errors and this operation can have unpredictable results.
MyEclipse Web Development Tooling (3.8.4) requires plug-in “org.eclipse.core.runtime (3.0.0)”, or equivalent.We just released the latest M7 build, but you should do a clean installation of it, rather than trying to upgrade an existing version. New M7 install, new MyEclipse 3.8.4 for M7 and restart with -clean on the commandline and you should be fine.
just found a small bug in the M7 build, the snippets customization seems to be broken. There comes no dialog or an empty one if you chose customize from the snippets view context menu.
Thanks for reporting that! We’ve got a bug report on it and will try to get it in the next milestone beta.
Another one, this one is tricky and I am not sure if this is a bug of myeclipse at all (eclipse 3.1m7 and the 3.8 myeclipse build)
there seem to be some synchronisation issues between subclipse and myeclipse, after working for a while with xml files (web.xml, faces-config ) and jsp files, I get the message, that the file has changed on the filesystem.
Also I did a checkout from my svn repository and myeclipse seemed to have serious problems recognizing the myeclipse related project files at svn checkout time. MyEclipse in the process deleted my entire webapp folder due to the fact that it had a different name, which was specified in the remote project file.
I dont know if this is a myeclipse issue, but I assume the behavior is rather similar on cvs.I dont know if this is a myeclipse issue, but I assume the behavior is rather similar on cvs.
Actually, it’s not similar on CVS at all. 🙂
It’s likely a weird interaction between all the products you’re using. The “change on the filesystem” message is caused by one of your other products using external means to modify something in the workspace rather than workspace operations. Refreshing the project will resolve the issue, in any case.
