- This topic has 5 replies, 3 voices, and was last updated 21 years, 1 month ago by
.
-
Posts
-
M4 has a bug working with external sources paths (using linked resources), so for those of you who do work with this feature M4 is not for you and the bug will be resolved in M5.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=44690
— Erez
Erez,
Thanks for the research and for posting this hear for everyone. The current workaround is to use the current production release of Eclipse (2.1.1/2.1.2) and MyEclipse 2.6.3. 🙂
–Scott
MyEclipse SupportA nice workaround but..
I think I’ll stick to the M3, there are some great features about their editor that worth it, and besides it works, and we don’t leave so quickly things that work, do we? 🙂— Erez
Erez,
we don’t leave so quickly things that work, do we?
No we don’t. Every change takes time and there is always some amount of risk in it. Staying put often is the best course of action. At Genuitec, we never touch a working development environment during a development cycle. The downside risk of breaking a team’s environment is simply too high.
–Scott
MyEclipse SupportI can’t agree more with what you’ve said. It’s a matter of what gain, and sometimes I admit having the latest version carries some charm in it but it doesn’t always worth it. After all I am human and fall for temptation from times to times but the project must go on 🙂
Erez
