Maverik
Maverik

Reputation: 2398

Exporting eclipse plugin fails under Mountain Lion

I'm developing a plugin for Eclipse Juno under Mountain Lion.

I can test my plugin without problem by doing run as > Eclipse application.

However when I try to export the plugin by doing the following action it fails.

  1. Open plugin.xml
  2. Go to the tab Overview
  3. Select Export Wizard

It returns the following error:

/Users/luca/Documents/University/PhD/FODA/.metadata/.plugins/org.eclipse.pde.core/temp/org.eclipse.pde.container.feature/compile.org.eclipse.pde.container.feature.xml:4: The following error occurred while executing this line:
/Users/luca/Documents/University/PhD/FODA/it.unibg.robotics.featuremodels.model/build.xml:31: /Library/Java/JavaVirtualMachines/jdk1.7.0_07.jdk/Contents/Home/Classes does not exist.
The following error occurred while executing this line:
/Users/luca/Documents/University/PhD/FODA/it.unibg.robotics.featuremodels.model/build.xml:31: /Library/Java/JavaVirtualMachines/jdk1.7.0_07.jdk/Contents/Home/Classes does not exist.

What's the problem?

Upvotes: 2

Views: 668

Answers (2)

CWindatt
CWindatt

Reputation: 124

This is fixed in Eclipse 3.8.2 and 4.3.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=392434

Upvotes: 0

Just ran into this problem myself today. As far as I understood, it comes from the fact that recently Apple stopped maintaining their version of Java in favor of an official version for the MacOS X from Oracle. The Oracle version, however, doesn't have the same directory structure as before, and the build script generated by Eclipse assumes the old structure.

You can see many bug reports related to this. E.g.,

I heard that switching to using Java 6 would solve the issue, as MacOS X still has the Apple Java 6 installation with the old directory structure. I didn't want to go back to Java 6, so I didn't try this.

Instead, I tried creating the directory that is reported missing (i.e., /Library/Java/JavaVirtualMachines/jdk1.7.0_07.jdk/Contents/Home/Classes), with nothing in it. Oddly, it seems to have worked.

Let me know if it works out for you as well... Future updates of Eclipse might also fix this (I updated mine today, but the problem was still there).

Upvotes: 6

Related Questions