- This topic has 75 replies, 25 voices, and was last updated 15 years, 11 months ago by
.
-
Posts
-
Grrrr, I can’t reproduce this no matter what I try (3 separate machines and networks so far).
Are you on Europa or Ganymede? What version of MyEclipse is Pulse showing you to try and provision?
Ok, So starting fresh :
Downloaded new pule installer (tar file creates directory pulse2-2.3.1.200810022130-linux-gtk-x86_64)
Start pulse, select Ganymede from combobox, Select Profiles from the list.
On the right I select MyEclipse 7.0 Milestone-2 and add to my profile.
Now in the My Profiles section on the left, I select the newly added profile. It shows the following
Base software
-
Eclipse Base
MyEclipse Enterprise Workbench
Pulse Services and Extensions
Sun Java 1.5.0_11No additional software is selected.
I right click on the profile and choose ‘Install then Run’. It spends some time resolving and validating the profile.
and then gives me the message :
Pulse has been unable to create a plan for MyEclipse 7.0 Milestone-2 – fresh. Please check the details below to diagnose the issue. If the problem persist, contact Pulse support via the forums at http://www.poweredbypulse.com.
Reason:
Cannot complete the install because some dependencies are not satisfiable.And then of course the list of dependencies when I press the Details button.
I added the ‘-fresh’ into the name of the profile to distinguish between the one I used to install on a 32 bit machine and this one.
Is there some cache I need to clean out?
Edward
Edward,
Your steps are all perfect (I just walked through them, worked fine), because it’s such a fundamental fail, I have to wonder if this is some network issue or something like that.
Are you behind a proxy by chance that needs to be setup?
No, no proxy that I had to set up.
Something may be interfering with it at work, but I get the exact same behavior at home. But II will try again.
I just tried again at work after deleting all Pulse related directories and still get the same. I’ll update this after I get home. The MyEclipse version I am seeing in pulse has a version number of 6.9.201, just to insure I have getting the right build number.
I just tried at home with a clean Pulse directory and I get the same thing.
So you are able to get this to work with the 64bit version of Pulse on Linux?
Edward
So you are able to get this to work with the 64bit version of Pulse on Linux?
Damn, I’m really sorry for missing that, it is a known issue specifically on 64-bit Linux that the 64-bit Pulse installer cannot provision MyEclipse 7.0M2, I was trying this with 32-bit builds and missed that you mentioned 64-bit installer above. I’m really sorry about that.
We are working on a fix for this soon.
@support-rkalla wrote:
So you are able to get this to work with the 64bit version of Pulse on Linux?
We are working on a fix for this soon.
Great, just keep us informed. I am more than willing to test it out when it’s ready (or even before it’s ready).
Thanks,
EdwardI finally had some time to try 7.0 M2 with Windows x64 and the 64-bit version of eclipse. It hasn’t been as successful as the M1 build. I’m getting stuck on a XULRunner dependency when using the Update Manager. Any suggestions?
Revo are you doing the install via Pulse or did you drop down Eclipse 64-bit and drop the Archived Update Site version of MyEclipse ontop of it? We don’t have a fully vetted 64-bit build of MyEclipse at this time, so some of the native dependencies of the IDE (like XUL) could be an issue.
I tried with the x64 version of Eclipse classic (both 3.4 and 3.4.1) using the Update Manager links provided in the forum. The M1 build worked first try, so I was excited to try with M2. However, Like you stated above, the M2 build has an issue with some of the native dependencies. XUL is the one I could not get past, so I’m unable to say if there are others.
Just FYI, the 32-bit version works great under Windows x64.
revoman,
I’m glad to hear that the 32-bit version works, I’m pushing to see if we can rectify the provisioning support for a 64-bit compatible version soon. Part of the issue that Pulse tries to honor the platform (64-bit) and we develop against the 32-bit XUL library, so we’d need to forcibly set that dependency for Pulse to grab that one instead of the 64-bit one (or try to).
There is also the issue that we don’t test on 64-bit Eclipse either, so pulling down 32-bit build of MyEclipse ontop of 64-bit Eclipse may not be the best approach either. We just need some time to test all this out.
I have just figured out that by installing Eclipse Classic 3.4/3.41 and unpacking the archive site of MyEclipse 7.0 into the ‘dropins’ directory of Eclipse, MyEclipse will work perfectly well on a 64bit Linux system.. no need to run the Update manager and run into all kinds of problems with missing dependencies. The only thing that needs fixing is pointing config.ini to the MyEclipse splash screen.
Am I the only one who did NOT know this?That sounds interesting. I’m not behind a Linux workstation now, but I’m sure going to try that. Thanks a lot for the tip! (btw, which JDK did you use?)
@henk wrote:
That sounds interesting. I’m not behind a Linux workstation now, but I’m sure going to try that. Thanks a lot for the tip! (btw, which JDK did you use?)
I did this with JDK1.6.0_10 (64bit) from Sun.
cjbrathw,
Great tip, that is absolutely another way you can do the install (and… as you said, dead easy).
1. So you download the entire 556 MB update site and unzip it into eclipse/dropins? Geez, good thing I have decent bandwidth…
2. What does “pointing config.ini to the MyEclipse splash screen” mean? I have this line in my config file now:
osgi.splashPath=platform\:/base/plugins/org.eclipse.platform
Do I change this line to refer to something in the update site I unzipped?Thanks.
