RubyMine fails to start on Yosemite - webstorm

RubyMine won't start under Yosemite, no loading screen, no error message.
This seems to be caused by the default JVM that comes with Yosemite
EDIT This also seems to affect WebStorm

This solution is controversial - please read all of it before applying changes!
Open this file
Check the version of Java, most likely 1.8, by using java -version, you should see something like:
java version "1.8.0_20"
Java(TM) SE Runtime Environment (build 1.8.0_20-b26)
Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode)
Open and edit
/Applications/RubyMine.app/Contents/Info.plist
Or for WebStorm
/Applications/WebStorm.app/Contents/Info.plist
Update the following key
<key>JVMVersion</key>
<string>1.7*</string>
to
<key>JVMVersion</key>
<string>1.8*</string>
RubyMine should now be good to go
Feedback on this solution
JetBrains do not recommend this solution as it will break autoupdating with patches. That tradeoff was acceptable for me as I just wanted to get going quickly and avoid installing Java 1.6.
The full discussion is here https://intellij-support.jetbrains.com/entries/27854363-IDE-doesn-t-start-after-updating-to-Mac-OS-Yosemite-or-Mavericks

You shouldn't edit your plist file since it will prevent Rubymine from autoupdating. This is direct from their support pages:
Modifying Info.plist will break the application digital signature and prevent the patch updates. We do not recommend modifying Info.plist file to run under JDK 1.7 or 1.8.
Page located here:
https://intellij-support.jetbrains.com/entries/27854363-IDE-doesn-t-start-after-updating-to-Mac-OS-Yosemite-or-Mavericks
The correct answer is to install Apple JDK 1.6

JDK 1.6 is required to run and may be missing on your system. Please install Apple JDK 1.6. There should be a window with the suggestion to install Java when you start the product for the first time, but it could be hidden by other application windows.
Apple JDK 1.6 download: http://support.apple.com/kb/DL1572.
I have tried to down load the JDK 1.6, it works in my Mac.

Just install java for OS X, and it'll solve the issue.
Up till OS X El Capitan(10.11), this link solves. Or you can just google "java for osx", most probably first link will show you the right answer.

Related

The specified Microsoft.NETCore.App', version '2.0.7' was not found

cannot start .NET Core app because of this error:
"It was not possible to find any compatible framework version
The specified framework 'Microsoft.NETCore.App', version '2.0.7' was not found.
- Check application dependencies and target a framework version installed at:
\
- Alternatively, install the framework version '2.0.7'.
The program '[1560] dotnet.exe' has exited with code -2147450749 (0x80008083)."
Editing .csproj didn't help. It looks like this:
<PropertyGroup>
<TargetFramework>netcoreapp2.0</TargetFramework>
<RuntimeFrameworkVersion>2.0.7</RuntimeFrameworkVersion>
<DockerComposeProjectPath>..\docker-compose.dcproj</DockerComposeProjectPath>
<MvcRazorCompileOnPublish>false</MvcRazorCompileOnPublish>
<CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>
You don't have the right .NET Core runtime installed. It's not good enough that's a .NET Core 2 runtime; it needs to be a minor version that is equal to or encompasses the version you're trying to target. You can see all the available runtimes here: https://www.microsoft.com/net/download/all. Specifically, you need 2.0 Runtime (v2.0.7) or higher. You can just choose 2.1, though. 2.0.7 will be rolled in and then, if you do end up upgrading your project later, you won't run into this issue again.
After playing around for a (longer) while, eventually it turned out that the solution is to comment out RuntimeFrameworkVersion in .csproj:
<PropertyGroup>
<TargetFramework>netcoreapp2.0</TargetFramework>
<!--<RuntimeFrameworkVersion>2.0.7</RuntimeFrameworkVersion>-->
<DockerComposeProjectPath>..\docker-compose.dcproj</DockerComposeProjectPath>
<MvcRazorCompileOnPublish>false</MvcRazorCompileOnPublish>
<CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>
It is worth mentioning that the problem occured after my collegues upgraded a .NET Core to higher version and I did 'Get latest version'.

Is the gstreamer-java 1.6 compatible with gstreamer 1.6.1 windows binaries

Do anyone have any idea if the gstreamer-java-1.6.jar downloadable from https://code.google.com/p/gstreamer-java/downloads/list is compatible with gstreamer windows 1.6.1 binaries? I installed both and setup the eclipse environment but somehow it gives me the warning for all(assuming as lot of warnings are on the eclipse console) the gstreamer plugins.
(javaw.exe:9744): GStreamer-WARNING **: Failed to load plugin 'D:\gstreamer\1.0\x86_64\lib\gstreamer-1.0\libgstgio.dll': 'D:\gstreamer\1.0\x86_64\lib\gstreamer-1.0\libgstgio.dll': The specified module could not be found..............
Although I can see everything is fine from command prompt running gstreamer(creating sample pipeline etc).
For any other, it will be helpful that gstreamer-1.6 compatible java bindings are there and available on https://github.com/praxis-live/praxis/tree/master/lib.gst1-java-core/release/modules/ext.
See reply on java-gstreamer forum.
No, it isn't!
The new home of the Java bindings is at https://github.com/gstreamer-java
The old GStreamer-Java only supports GStreamer 0.10. Try
gst1-java-core at https://github.com/gstreamer-java/gst1-java-core
There are no pre-built binaries there, although you can get my one
from Praxis LIVE -
https://github.com/praxis-live/praxis/tree/master/lib.gst1-java-core/release/modules/ext
Click on it, then click view raw and you can download it.
It's still a work in progress, and I haven't tested on Windows yet,
although others may have.
Best wishes,
Neil

cfimage writetobrowser throwing error on CF10

I get the following error with <cfimage action="writeToBrowser" on a Mac Mavericks CF10 machine:
java.lang.ClassNotFoundException: javax.media.jai.util.ImagingException
I've googled extensively and only came up with one person with a similar problem.
http://qiita.com/cubdesign/items/c5cc0435cb6e928fd3b5
It's in Japanese but translated with Google he says he rolled back to java 1.6.0_65.jdk. Unfortunately, I can't seem to find that particular java version on Oracle's site.
I tried rolling the jdk to 1.6.0_45 but then CF10 wouldn't start.
My machine is set up with java 1.7.0_55.jdk and the latest Mavericks patch from Adobe has been applied to the CF server (update 13).
Update:
Submitted Bug Report #3759721 for this issue.
Update Fixed:
Credit goes to Leigh (see comments below).
It seems that the Mavericks update wiped the JVM in the /System/Library/Java folder. Unfortunately, it looks like Adobe still has an issue with any version of the jdk above 1.6
Download and install the dmg file on this page: Java for OS X 2013-005
Found a solution:
Credit goes to Leigh (see comments below question).
It seems that the Mavericks update wiped the JVM in the /System/Library/Java folder. Unfortunately, it looks like Adobe still has an issue with any version of the jdk above 1.6. See Bug Report #3759721.
Download and install the dmg file on this page for the time being: Java for OS X 2013-005

Meteorite installation error on windows XP - "c:\Microsoft.Cpp.Default.props" was not found

I'm learning to create meteor application on my windows machine now. Everything is working fine because http://win.meteor.com have windows installation that I can try with.
The problem I have is now I want to have routing capability in my app. From my research the Meteor-Router package can add by using meteorite. So here's what I've done
Install node.js for windows --> everything looks OK, I can type node -v to look at node version
Install meteorite by type npm install -g meteorite --> every working fine up until async module installation that complain about "c:\Microsoft.Cpp.Default.props" was not found
I've try googling to looking for the answer but have no luck.
Any idea for me to solve this problem?
According to meteorite's official documentation, Meteorite does not work in Windows as of time of writing this. Sorry.
... However, meteorite's git based approach runs counter to the MSI installation that's required to get it working. So meteorite does not work under windows right now. Pull Requests which change this would be gladly accepted!

How do I make Windows XP machine stop trying to use uninstalled Java JDK (1.6.0_13)

My Windows XP workstation at the office had several old versions of the Java JDK installed on it. Today I decided to install the newest Java JDK and uninstall the older ones. BIG MISTAKE APPARENTLY!
I don't understand why, but XP seems to think that one of the removed JDK installations is the one that it wants to use. Not sure if it is relevant, but it was JDK 1.6.0_13. I uninstalled it earlier using the XP "Add or Remove Programs" from the Control Panel. The JDK folder is gone (as one would expect) but apparently not forgotten. Here are the symptoms:
Eclipse will no longer start up and use the new JDK that I installed. Eclipse acts as if there is no JDK available on the system.
When I type java -version at a Command Prompt I get the following response:
Error: could not open `C:\jdk1.6.0_13\jre\lib\i386\jvm.cfg'
(Gee thanks. I never would have guessed that the uninstalled JDK could not be found...)
When searching around on the machine I found a system service named "Java Quick Starter" that is pointing to the removed JDK directory.
Now I know what some of you are probably thinking. He has a JAVA_HOME system variable pointing to the old location and/or has the old location in his PATH system variable. Not the case! There are no system variables that reference this old JDK and neither does my PATH. In fact, I have already defined a new JAVA_HOME for the new JDK that I installed this morning and added it to the system PATH. I was sure that would at least give me success from the Command Prompt, but no luck.
And in case you're wondering if I have rebooted after the install/uninstall/system variable changes, yes I have.
QUESTION
Does anyone know what I did wrong here? How do I purge these references to the uninstalled JDK from my system so it can start using the newly installed one?
EDIT 1
I checked the registry as duffymo suggested. There was some stuff under HKEY_LOCAL_MACHINE/SOFTWARE/JavaSoft that did not look right. An entry still existed for the 1.6.0_13 JDK that I had deleted, and a number of the newer JDK installs had entries here with their JavaHome attribute set to the path for the old 1.6.0_13 JDK for some inexplicable reason!
I uninstalled all of the JDKs on the machine, but still there is a remnant of the old 1.6.0_13 JDK in this registry section.
Also, a 1.6.0_21 JRE is still listed in the Add and Remove Programs list that gives an error if I try to uninstall it. That one is also shown in the registry and has a registry "JavaHome" key with a value that points to the no-longer-existing JDK 1.6.0_13.
Check the registry to see if something is hanging around there to point to the old JRE.
Look at HKEY_LOCAL_MACHINE/SOFTWARE/JavaSoft. You'll see Java Development Kit and Java Runtime Environment there. See what they say.
Now that you've found that the registry values are incorrect, I'd recommend either modifying them to point to the correct values OR remove them, uninstall the JDK, and reinstall.
You could also maybe try disabling the service from starting.
Copied from my repost of this quesiton on www.superuser.com:
https://superuser.com/questions/203143/cannot-install-java-jre-on-windows-xp-workstation-possibly-due-to-previous-faile
I tried CCleaner on the registry, but it didn't solve the problem. I was feeling pretty desperate at that point and decided to search the registry with regedt32 for instances of "jdk1.6.0" and delete everything that was obviously garbage. Any registry references to JDK/JRE instances that I knew no longer existed got deleted. Usually this meant deleting the whole key, but there were a few keys where I just had to delete an individual value/data pair. I rebooted after I was done performing meatball surgery on my poor defenceless registry.
DISCLAIMER: I don't recommend that anyone start messing with random keys in their registry as the primary way to solve a problem! This was my last resort before considering the option of re-imaging my workstation and re-installing EVERYTHING.
Having said that, this approach did solve my problem. I was able to install the JRE and then things like Eclipse started working normally once again. I next installed a JDK of the same version without incident.