techhealth
asked on
Couldn't create new Force.com project in Eclipse
I just installed Eclipse and Force.com IDE on Ubuntu Hardy to do some Salesforce.com development. But I can't get it to create any new Force.com project. It always gives me this error message: "Selected wizard could not be started. Reason: Plug-in com.salesforce.ide.ui was unable to load class com.salesforce.ide.ui.wiza rds.projec t.ProjectC reateWizar d."
I tried both Eclipse 3.2.2 which comes through Hardy's repository and 3.3.2 I downloaded from Eclipse sourceforge page. Same message. I followed all the instructions for Force.com IDE installation. The only thing that's a little out of normal was Eclipse claimed the plugin packages are unsigned, but I did continue it at the prompt.
Where should I start troubleshooting
I tried both Eclipse 3.2.2 which comes through Hardy's repository and 3.3.2 I downloaded from Eclipse sourceforge page. Same message. I followed all the instructions for Force.com IDE installation. The only thing that's a little out of normal was Eclipse claimed the plugin packages are unsigned, but I did continue it at the prompt.
Where should I start troubleshooting
ASKER
Since I'm using Ubuntu Linux 8.04 (Hardy), I did
./eclipse -clean
but that didn't help. Same error.
There're 3 jar files in the plugins directory related to com.salesforce.ide.ui:
com.salesforce.ide.ui_14.0 .1.2008103 11433.jarcom.salesforce.ide.ui.edit ors_14.0.1 .200810311 433.jarcom.salesforce.ide.ui.edit ors.intro_ 14.0.1.200 810311433. jar
Are they the ones I should have? There're also a whole bunch of other com.salesforce.ide jar files.
./eclipse -clean
but that didn't help. Same error.
There're 3 jar files in the plugins directory related to com.salesforce.ide.ui:
com.salesforce.ide.ui_14.0
Are they the ones I should have? There're also a whole bunch of other com.salesforce.ide jar files.
Hmm, wierd. So you followed the instructions described here to install the plugin?
http://wiki.apexdevnet.com/index.php/Force.com_IDE_Installation_for_Eclipse_3.3.x
This describes performing an update, it may not be relevant though:
http://wiki.apexdevnet.com/index.php/Updating_the_Force.com_IDE
If all else fails you can at least verify that the class file is in one of the jars. Try the following command:
> cd <force plugin location>
> find . -name "*.jar" | xargs -IZ jar tvf Z | grep "ProjectCreateWizard.class "
That command looks through all the jar files under that directory, scanning for the class file missing. If you get any output, then the file is there. If not, then the file is missing and that's where the problem lies. If the file is there, then there's some plugin configuration problem.
Sorry I couldn't be more specific at this point in time.
http://wiki.apexdevnet.com/index.php/Force.com_IDE_Installation_for_Eclipse_3.3.x
This describes performing an update, it may not be relevant though:
http://wiki.apexdevnet.com/index.php/Updating_the_Force.com_IDE
If all else fails you can at least verify that the class file is in one of the jars. Try the following command:
> cd <force plugin location>
> find . -name "*.jar" | xargs -IZ jar tvf Z | grep "ProjectCreateWizard.class
That command looks through all the jar files under that directory, scanning for the class file missing. If you get any output, then the file is there. If not, then the file is missing and that's where the problem lies. If the file is there, then there's some plugin configuration problem.
Sorry I couldn't be more specific at this point in time.
ASKER
Thanks for the help. I mostly followed the instructions to the letter, except the very last step at which I'm supposed to be able to open force.com perspective. Things broke down there - I couldn't open that perspective, neither could I create any force.com project.
grep did find the wizard class, so I guess it's probably some kind of configuration issue. It's really weird. It's a virgin Eclipse installation, which really doesn't have that much to configure.
Hope someone can come up with an idea. In the mean time I'll try to have Eclipse on some other computers.
grep did find the wizard class, so I guess it's probably some kind of configuration issue. It's really weird. It's a virgin Eclipse installation, which really doesn't have that much to configure.
Hope someone can come up with an idea. In the mean time I'll try to have Eclipse on some other computers.
Hmm, well if the plugin jars are under 5MB zipped you could try attaching then so I could take a look. Additionally: are there any *salesforce* directories under /plugins in addition to the /plugins/*salesforce*.jar files? If so, those would be useful too.
ASKER
One of the jar files is big (ide.api) . Others are OK. I've tried attaching them here, but EE wouldn't allow the extensions inside the jar files (I changed .jar to .zip). Can you tell me what I should look for? Maybe I can take a look myself.
There is only one Salesforce directory under the plugins directory: com.salesforce.ide.documen tation_14. 0.1.200810 311433.
There is only one Salesforce directory under the plugins directory: com.salesforce.ide.documen
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sorry I haven't followed up yet. I'll post what I found soon.
ASKER
There isn't any META-INF/MANIFEST.MF directly under plugins directory. The only one I found related to salesforce.com is under plugins/com.salesforce.ide.documen tation_14. 0.1.200810 311433. Is that location right? There isn't anything about ProjectCreateWizard in that MF.
ASKER
I have no problem awarding szigeti the points. Just want to state that the problem is unresolved so far.
First try running Eclipse in clean mode, e.g.:
C:\eclipse\eclipse.exe -clean (assuming you're using Windows)
If that failed, try checking under the directory eclipse/plugins for the plugin "com.salesforce.ide.ui" and see if you can find the related class under there. If it's not there, perhaps the plugin wasn't installed correctly. Try re-installing it by downloading the plugin manually from the vendor, and unzipping it under eclipse/plugins. After this run "clean" again.