- This topic has 15 replies, 4 voices, and was last updated 16 years, 6 months ago by
.
-
Posts
-
The message is:
Unable to load catalog Error instantiating [com.genuitec.pulse2.model.RealmBlueprint – 17]Software Update is impossible with Pulse.
Check my download info for Myeclipse release.
System is Ubuntu with sun jdk 1.6.0.10
2 GB RAM
Athlon 3200+
uname -a
Linux hobbarey.com 2.6.27-8-server #1 SMP Thu Nov 6 18:29:16 UTC 2008 i686 GNU/LinuxI found this by adding manually Software Updates…
http://www.poweredbypulse.com/forums/showthread.php?t=235
But it is funny that no one is answering around. Christmas parties makes you exshausted guys 😀
Kunthar,
Sorry for the delay in response. It’s not that we’re at Christmas parties; more like everyone is exhausted due to the QA cycle of MyEclipse 7.0 we’re prepping for release.
First, thanks for providing the link to the Pulse documentation you were using. I read it and noted that it was so old and out of date that I deleted it. Sorry it was still out there because it was very misleading and for an earlier version of Pulse.
The correct document for making local modifications for plugins is this one. Can you please give that a try and let us know your additions now work as expected?
Scott – don’t want to be off thread but how is that prep for release coming? I think that there are a lot of anxious subscribers out there waiting to get their hands on ME 7.0. Can someone please give us a confirm date???
Mike,
I don’t mind the question at all because it’s a great question.
The confirm date is honestly “very soon now”. Right now we’re in final QA builds of 7.0 and had actually planned on shipping prior to now. What ended up happening was we found a couple of issues that the management team decided were “must fix” before we could ship. The entire team is effectively working 24×7 to close the remaining items so we can deliver a very high quality release. What it looks like right now is we’re expecting availability late on Monday (12/8) and it’s “all hands on deck” until our users can download. There’s no higher priority.
It seems that youre quite exhausted.
Steps i’ve taken
1. Add/remove software,
Result was this error: “Unable to load catalog Error instantiating [com.genuitec.pulse2.model.RealmBlueprint – 17]”
2. After this i’ve opened this thread and started to pray if someone take into account my already spent 31buck.
3. Nothings happened of course.
4. But i was in a hurry. Why? Because of YOUR US patented bloody work work system. So i had to find a solution.
5. After i did steps from my found link, Pulse Add/Remove Entry totally removed from Software Updates menu item.
6. I had to integrate Terracotta and forced to do it.In short all story begun with no Add/Remove menu item work at all.
Your QA dept. can use the Pulse link in every manner that they can handle on their b*ck, cos my MyEclipse installation basically screwed and i had to spent way too much bloody hours on front of computer, instead of having fun in parties.Cheers a lot,
KunthScott – don’t want to be off thread but how is that prep for release coming? I think that there are a lot of anxious subscribers out there waiting to get their hands on ME 7.0. Can someone please give us a confirm date???
Please open a brand new thread in this quite huge forum. No need to have a kinda troll around. We have real world problems here.
Kunth,
Sorry for the poor followup on this thread. We have actively been researching this issue as it has been reported by you and others in different threads. In short, we have identified it as a problem with installing MyEclipse 7 on 64-bit Linux that leads to failures like you’re seeing. From your initial comment you’re definitely running Ubuntu 8.1 and since you’re seeing a “blueprint instantiation failure” I believe you’re experiencing this exact issue. Fixing this problem is extremely high priority for us and the development team has been working in shifts to get a fix in place since the issue was first isolated. Currently, the fix is undergoing testing by the QA team. At present we anticipate the fix will be made available either late today or tomorrow morning.
Once the fix is promoted to production I’ll post a followup to this thread to let you know.
