- This topic has 24 replies, 11 voices, and was last updated 17 years, 7 months ago by
.
-
Posts
-
Ben,
Work on it continues in the 5.5M2 scope. It appears to be a thread race condition that only affects the Mac due to differences in how SWT and Swing are implemented there versus other platforms. As a result, it’s taking awhile to run down. Trust me, when we nail it down we’ll let everyone know.
Along with many other OS X / MyEclipse users, I’ve been patiently waiting for many months for this issue to be resolved. The message from Genuitec has consistently been that the problem is outside their control and that it must be addressed by the Eclipse team and Apple.
Well, here’s the latest update on Eclipse bug #145890 from Apple in response to a disgruntled MyEclipse user’s post:
I talked to their [Genuitec’s] director of marketing (I believe) at EclipseCon this year, and asked what they were trying to do that wasn’t working. He wasn’t fully aware of what the problems were, but said he would follow up with his engineers. I haven’t heard back yet, but I also have been extremely busy with Leopard work.
Haven’t heard back yet? I would think that if this were a priority issue for Genuitec, they would be beating down the door at Apple with the information necessary to help resolve the problem. However, it sounds to me like Genuitec is just taking this “not our fault” stance as an excuse for not providing full OS X support.
My license renewal is coming up and, honestly, I’m out of patience. I think the Eclipse Web Tools Platform (which MyEclipse uses for much of its functionality) has come a long way. WTP along with other open source plug-ins provide everything that MyEclipse currently delivers on OS X.
Why wait around for something that’s never going to come?
Sure, that things are working now with SWT (i’m using Omondo and Active BPEL designer with no issues).
I agree with jcowley above, except i’ve already renew my license ! I couldn’t imagine this king of things could again be a problem on mac platform on a fresh new release claiming that it’s multiplatform.
Is there any chance to have a normal working release soon ?Guys,
We hear you; honestly. Part of the issue is timing and part of it is difficulty. You’re correct that the work that Apple and the Eclipse team have done on compatibility has helped a lot. We looked into the problem last during the 5.1 release cycle and found that we had a race condition between the SWT UI thread and the Swing one. We ran out of time to run it down before we had to ship. Then we went into the 5.5 effort and we always do “big features first” so we can milestione them a time or two before GA. We’ve got 5.5M2 slated for release next week and then it’s all bug fixes and minor enhancement work to harden the release for the GA at the end of the month. Why the story? Because it’s in this M2 to GA window that we’ll look into it again. One of our best developers uses a Mac as his primary machine and he’s motivated to help work this out. I’m hopeful he’ll be able to do it for 5.5GA. So, please give us a few more weeks; it’s queued up in the schedule for investigation with a high priority assigned to it so it will definitely get some attention.
Thanks a lot for the update scott. I will wait a few week for this being available. The Mac community will greetings you for that !
I installed the libraries from apple DP2. But when I try to use UML in myeclipse, I still get the message “Cannot create new Model repository” and stating MyEclipse is unsupported on the mac platform.
Some people got it to work for other applicaitons, but I believe MyEclipse guys needs to give some instructions on how to get UML modelling up and running. It looks like eclipse is simply check your OS and version rather than checking to see what libraries are installed, and therefore they need to give us configuration information to enable us to run it after installing libraries.It looks like eclipse is simply check your OS and version rather than checking to see what libraries are installed, and therefore they need to give us configuration information to enable us to run it after installing libraries.
That’s exactly what it’s doing right now because the current implementation is unstable, so letting you launch doesn’t help much if it takes down the workbench a few minutes later. As Scott mentioned we are going to have someone look into this (hopefully before GA)… but even if we miss that deadline and it goes out in a service release, you guys made enough noise about it that management cannot ignore it 🙂
