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.
Open plugin.xml
Go to the tab Overview
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?
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.,
https://bugs.eclipse.org/bugs/show_bug.cgi?id=371215
https://bugs.eclipse.org/bugs/show_bug.cgi?id=378596
https://bugs.eclipse.org/bugs/show_bug.cgi?id=385077
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).
This is fixed in Eclipse 3.8.2 and 4.3.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=392434
Related
I'm looking to use Slather to export unit test code coverage to TeamCity, however I am running into issues even getting it to run, and I'm a little confused as I'm not finding other people encountering this error. So hopefully someone can help me. I'm a build engineer, not XCode developer, and our devs don't seem to know what could be causing it.
Anyway, to trial Slather, I was given a new Mac, so I installed RVM and Ruby 2.4.1. I then installed the Slather gem, which all was quite easy and fast.
I built the XCode project, ran the unit tests and saw XCode displaying the code coverage data in the IDE.
In my terminal I ran the slather coverage command, and it returns the error:
Slathering...
/Users/me/.rvm/gems/ruby-2.4.1/gems/CFPropertyList-2.3.5/lib/cfpropertylist/rbCFPropertyList.rb:349:in `load`: File /Library/Developer/CommandLineTools/../Info.plist not readable! (IOError).
So my question is what am I missing?
The Mac is new, I only added XCode v8.2.1, RVM, Ruby and Slather. Slather pulled in all the dependencies it needed. The XCode project has test coverage turned on, and there is nothing in the Slather site mentioning that I need to modify plist reference paths in the project settings.
I even went to a blog site and tried their demo project for using Slather https://cocoacasts.com/how-to-generate-code-coverage-reports-in-xcode-with-slather/ and I get the same error with their project also.
It seems Slather just works for most other people, so hoping its just some really simple small thing that I need to setup on this Mac environment.
Sorry to be posting an answer to my own question, but I found out what I was doing wrong and it was an environment issue.
The solution was found from this answer: StackOverflow XCode Select Active Developer Directory Error
The issue was I had opened XCode from a XIP and was essentially running it from the Downloads folder as opposed to the Applications folder. However the XCode commandline tools were expecting it to be in Applications. Once I put XCode in the correct location, Slather worked fine.
Basically a rookie OSX error by a Windows user.
I should mention that I originally posted this as an issue on Neovim's tracker, but it hasn't been getting a ton of traction there lately and I'm beginning to suspect that it's more an issue with my setup rather than Neovim itself.
Essentially, I had stopped building neovim nightlies for a few months. Having heard that it's getting integrated terminal support I decided to rebuild using the latest source, only to get a persistent, odd error. No matter what my build settings are, it always boils down to make hitting an error when it has to compile a file called loop.so. I hadn't noticed this issue with any other software I try to build, but I suspect it could be an issue with my environment.
Does anyone here know what this file's role is, and why the compilation could be failing at that point?
You might need to install the full Xcode app and not just the command line. This fixed the issue for me.
The issue turned out to be a bad typedef in a libuv header, object.h.
I run OpenSUSE v 13.1 32-bit and recently installed Android Studio v 0.8.6 (updated to v 0.8.9). If I remember correctly, it comes with Gradle v 1.12.
When I'm trying to create a new project as soon as I click the magic Finish button the IDE does it's thing and creates the project with Gradle instantly throwing an error:
Gradle project refresh failed, Error: Cause: invalid address family type.
I have already tried searching it online, including these forums, and so far came across nothing. I have posed the same question on Gradle forums but apart from two other poor souls, that have the same problem, nobody suggested any solutions so far.
set JAVA_HOME var to Oracle Java, from
http://forums.gradle.org/gradle/topics/gradle-project-refresh-faild-error-cause-invalid-address-family-type
I had the same problem, setting the $JAVA_HOME as described above didn't solve my problem.
My solution was to delete the $HOME/.gradle directory
After doing this Android-Studio installs gradle and configures it again and it worked :-)
I downloaded the latest adt bundle (adt-bundle-windows-x86_64-20140624), and uncompresed that zip file, but when i try to open that adt, it open as juno eclipse. can any body help me to resolve this prblem.
thanks in advance
ADT Bundle contains Eclipse, to start Android development you need the ADT and the bundle comes with both you don't have to spend time searching for the ADT and Eclipse
Same problem here, using OSX. The downloaded ADB dows not show the typical ADB buttons and other extension provided by the plugins, but just a plain Eclipse. Installing an older version of ADT (adt-bundle-mac-x86_64-20140321) and updating won't help.
The package seemes somehow broken, some files like the ADT app icon, just aren't there. Other people experimented problems (Same problem; Other problem, also documented here).
I know it's not a real answer, but I just switched to Android Studio. I think the only other option is reverting to an older versione and wait for a new release.
To not get blocked I've continued to install the latest ADT Bundle 23.0.0 and adt-bundle-windows-x86_64-20140624 fresh on my system. Updated the SDK to the latest and continued to set "targetVersion as '19'" instead of setting it to 20 or 21.
That way you can proceed ahead with your coding and later when things get resolved...you can implement that to new version. BTW, I've also selected 'Blank Activity / Empty Activity" during the project creation
Comment back if it makes sense or NOT until the problem gets resolved by Google... :)
The Bug thread about this issue can be tracked here : Latest ADT Bundle Bug Tracker
Today I had a problem with my old Eclipse 3.4 installation and I had to re-download the entire package. However, I don't think that I got the exact package as before, and I'm having some problems.
The problem can be summarized as follows: when developing a plug-in, I cannot resolve dependencies towards 'org.eclipse.jdt.ui'. When trying to add the missing plugin, in the dialog the closest match is 'org.eclipse.jdt.ui**.source**'. A similar thing happens with other core plugins.
In order to test, I created a new plug-in using the wizard and I obtained a non-compiling plugin: one of the classes uses the class org.eclipse.jdt.ui.JavaUI and it cannot be resolved. Similarly, the MANIFEST.MF includes a dependency towards 'org.eclipse.jdt.ui', but the 'Bundle 'org.eclipse.jdt.ui' cannot be resolved'.
Now a summary of my platform:
I'm running Mac OS X 10.4 Tiger and Java 1.5.0_19-138
I'm running Eclipse Version: 3.4.1 Build id: M20080911-1700
I downloaded the modeling package, which comes in a file called 'eclipse-modeling-ganymede-SR1-incubation-macosx-carbon.tar.gz'
I've performed a fresh installation, in a new folder and using a new workspace.
If I look at the Plug-in Registry view, I can find the 'org.eclipse.jdt.ui' plugin in there, and it appears to be running. By the way, if it is disabled, then the workbench breaks and stops working.
I cannot understand what is happening. Is my installation broken? I wonder if the Eclipse package that I downloaded has an error and they included the sources instead of the compiled files. But in that case, the plug-in shouldn't be working in the workbench, isn't it?
In any case, why I cannot find the plug-in when I'm adding the dependencies, even if I see it in the Plug-in Registry?
Thanks for your help!
Problem solved: just restart the computer.
I don't restart my computer very frequently, so it took me a lot of time to find out that this was the solution. After I restarted it, everything started to work perfectly again. It seems that either Eclipse leaves something in the memory after running, or that some of my initial failures had left something nasty behind. In any case, I had checked and there were no Eclipse related processes running .... weird, but at least now it's fixed!