I am trying to use Notepad++ as my all-in-one tool edit, run, compile, etc.
I have JRE installed, and I have setup my path variable to the .../bin directory.
When I run my "Hello world" in Notepad++, I get this message:
java.lang.UnsupportedClassVersionError: test_hello_world :
Unsupported major.minor version 51.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(Unknown Source)
.........................................
I think the problem here is about versions; some versions of Java may be old or too new.
How do I fix it?
Should I install the JDK, and setup my path variable to the JDK instead of JRE?
What is the difference between the PATH variable in JRE or JDK?
The version number shown describes the version of the JRE the class file is compatible with.
The reported major numbers are:
Java SE 19 = 63,
Java SE 18 = 62,
Java SE 17 = 61,
Java SE 16 = 60,
Java SE 15 = 59,
Java SE 14 = 58,
Java SE 13 = 57,
Java SE 12 = 56,
Java SE 11 = 55,
Java SE 10 = 54,
Java SE 9 = 53,
Java SE 8 = 52,
Java SE 7 = 51,
Java SE 6.0 = 50,
Java SE 5.0 = 49,
JDK 1.4 = 48,
JDK 1.3 = 47,
JDK 1.2 = 46,
JDK 1.1 = 45
(Source: Wikipedia)
To fix the actual problem you should try to either run the Java code with a newer version of Java JRE or specify the target parameter to the Java compiler to instruct the compiler to create code compatible with earlier Java versions.
For example, in order to generate class files compatible with Java 1.4, use the following command line:
javac -target 1.4 HelloWorld.java
With newer versions of the Java compiler you are likely to get a warning about the bootstrap class path not being set. More information about this error is available in a blog post New javac warning for setting an older source without bootclasspath.
java.lang.UnsupportedClassVersionError happens because of a higher JDK during compile time and lower JDK during runtime.
In Eclipse, I just went to menu command Window -> Preferences -> Java -> Compiler and then set "Compiler compliance level" to 1.6.
Don't worry, I got it solved.
It is actually simple - you need to install BOTH JRE / JDK with the same version.
JRE 6 -> JDK 6
JRE 7 -> JDK 7
And so on.
This error means you're trying to load a Java "class" file that was compiled with a newer version of Java than you have installed.
For example, your .class file could have been compiled for JDK 7, and you're trying to run it with JDK 6.
So the solution is to either:
Upgrade your Java runtime or
Recompile the class if you have the source, using your local Java compiler (if you have one).
javac FileName.java
For developers, this can happen if another developer checks in a .class file, and they've got a newer version of java than you have!
You are trying to run your program with a Java version that does not support the version in which the code was compiled. So basically you must have compiled your code with a higher version and trying to run it using a lower version.
As you are getting
Unsupported major.minor version 51.0
and version 51.0 corresponds to J2SE 7 you have most probably compiled your code in Java 7 and trying to run it using a lower version. Check what java -version displays. It should be the Java 7 version. If not make appropriate changes in the PATH/JAVA_HOME. Or you can compile with the same version you are trying to run the code. If the configurations are confusing you can always give absolute path /home/user/jdk1.7.0_11/bin/javac and /home/user/jdk1.7.0_11/bin/java.
I had a similar situation on Mac, and the following process worked for me:
In the terminal, type
vi ~/.profile
Then add this line in the file, and save
export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk<version>.jdk/Contents/Home
where version is the one on your computer, such as 1.7.0_25.
Exit the editor, then type the following command make it become effective
source ~/.profile
Then type java -version to check the result
java -version
What is .profile file?
.profile file is a hidden file. It is an optional file which tells the system which commands to run when the user whose profile file it is logs in. For example, if my username is bruno and there is a .profile file in /Users/bruno/, all of its contents will be executed during the log-in procedure.
Source: http://computers.tutsplus.com/tutorials/speed-up-your-terminal-workflow-with-command-aliases-and-profile--mac-30515
In Eclipse's menu Window -> Preferences -> Java -> Compiler check also "Configure Project Specific Settings".
If you stil have the error with same Java version: try to delete build folder of your project manually. Then restart Eclipse.
You can have some JAR library compiled in Java 7, and you have only Java 6 as Java Runtime. It could happen with some new libraries.
The most common issue is misconfiguration of your JAVA_HOME variable which should point to the right Java Development Kit library, if you've multiple installed.
To find where SDK Java folder is located, run the following commands:
jrunscript -e 'java.lang.System.out.println(java.lang.System.getProperty("java.home"));'
Debian/Ubuntu
To check which java (openjdk) you've installed, check via:
dpkg -l "openjdk*" | grep ^i
or:
update-java-alternatives -l
To change it, use:
update-alternatives --config java
Prefix with sudo if required.
to select the alternative java version.
Or check which are available for install:
apt-cache search ^openjdk
Prefix with sudo if required.
Then you can install, for example:
apt-get install openjdk-7-jre
Prefix with sudo if required.
Fedora, Oracle Linux, Red Hat
Install/upgrade appropriate package via:
yum install java-1.7.0-openjdk java-1.7.0-openjdk-devel
The java-1.7.0-openjdk package contains just the Java Runtime Environment. If you want to develop Java programs then install the java-1.7.0-openjdk-devel package.
BSD
There is an OpenJDK 7 package in the FreeBSD Ports collection called openjdk7 which probably needs to be reconfigured.
See: OpenJDK wiki page.
Windows
Just install appropriate Java SE Development Kit library from the Oracle site or install
Jenkins
If you're experiencing this issue with Jenkins, see:
JENKINS-30561 - Unable to launch agent using SSH
However selecting the right version of Java (newer) with update-alternatives should work.
I got the same problem with a project written in 1.7 and tried to execute in 1.6.
My solution in Eclipse:
Right click on your Project Properties -> Java Build Path -> Libraries
Select your JRE System Library and click Edit on the right, and choose the target JRE.
Now go to Java Compiler on the left, and change the Compiler compliance level to your target.
That worked for me.
I have faced the same problem when I was working with an Ant script to build my application.
I use Eclipse for my application development, and I changed the compiler version in build properties of the project. But that didn't work for me. Then I found out that I can provide the compiler version in the Ant script.
I modified the Ant script at the section where it compile Java files.
<target name="build-java" depends="prepare-build">
<echo message="Compiling java files"/>
<javac ....
target="1.5"...
</javac>
</target>
This worked for me to resolve the unsupported major minor issue.
When I installed JDK 1.7, the problem got solved.
Based on this...
J2SE 8 = 52
J2SE 7 = 51
J2SE 6.0 = 50
J2SE 5.0 = 49
JDK 1.4 = 48
JDK 1.3 = 47
JDK 1.2 = 46
JDK 1.1 = 45
In Eclipse, right click on project in package explorer:
Build Path -> Configure Build Path
Under:
Java Build Path -> Libraries -> Add Library -> JRE System Library -> Installed JREs -> Search.
Add the required JRE by selecting the library in the list available after the search is complete.
As answered elsewhere by several people, the Java program is being run on an older version of Java than the one it was compiled it for. It needs to be "crosscompiled" for backward compatibility. To put it another way, there is a mismatch between source and target Java versions.
Changing options in Eclipse menus don't answer the original poster, who said he/she is not using Eclipse. On OpenJDK javac version 1.7, you can crosscompile for 1.6 if you use parameters -source and -target, plus provide the rt.jar -file of the target version (that is, the older one) at compile time. If you actually install the 1.6 JRE, you can point to its installation (for example, /usr/lib/jvm/java-6-openjdk-i386/jre/lib/rt.jar on Ubuntu, /usr/jdk/jdk1.6.0_60/jre/lib/rt.jar on SunOS apparently. Sorry, I don't know where it is on a Windows system). Like so:
javac -source 1.6 -target 1.6 -bootclasspath /usr/lib/jvm/java-6-openjdk-i386/jre/lib/rt.jar HelloWorld.java
It looks like you can just download rt.jar from the Internet, and point to it. This is not too elegant though:
javac -source 1.6 -target 1.6 -bootclasspath ./rt.jar HelloWorld.java
If you use Maven, set your Java compile level. Open a command line and write java -version for your compile level:
If you use IntelliJ IDEA, select project → File → Settings → Build Execution Deployment → Compiler → Java Compiler. Then change byte code as 1.7 like this image:
If you're facing this issue while using Maven, you can compile your code using the plug-in Maven Compiler.
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.1</version>
<configuration>
<source>1.6</source>
<target>1.6</target>
</configuration>
</plugin>
.....
UPDATE: set source and target to 1.8, if you are using JDK 8.
I had the same error message when running Ant from Eclipse, but the other solutions mentioned here didn't solve my problem. The funny thing was that running Ant from the Windows command line was running fine, so it had to be a configuration issue within Eclipse.
It turned out that under Eclipse you can specify the environment that Ant should be running with and this was set as a JRE instead of a JDK.
Go to: Run -> External Tools -> External Tools Configurations ...
Select the Ant build.xml for your project (if you have multiple projects)
Activate the Tab 'JRE'
Here was selected 'Separate JRE: jre6'. When I changed this to a JDK from the 1.6 or 1.7 series, the error was gone.
You have used a higher version of the JDK to compile and trying to run from a lower version of JDK/JRE.
To check this, see the version information:
javac -version
java -version
They will be different and javac will have a higher version number.
To get around this, run using java from the JDK version or if you have a newer JRE/JDK that will work as well.
which javac will tell you the location, for example, /usr/bin/javac. Just run directly using /usr/bin/java <program>.
OR you can set the environment variable as a permanent solution.
How do I fix it?
This error means that the JRE that is being used to execute your class code does not recognise the version of Java used. Usually because the version of Java that generated your class file (i.e. compiled it) is newer.
To fix it, you can either
a) Compile your Java sources with the same, or older, version of the Java compiler as will be used to run it. i.e. install the appropriate JDK.
b) Compile your Java sources with the newer version of the Java compiler but in compatibility mode. i.e. use the -target parameter.
c) Run your compiled classes in a JRE that is the same, or newer, version as the JDK used to compile the classes.
You can check the versions you are currently using with
javac -version for the compiler, and java -version for the runtime.
Should I install the JDK, and setup my PATH variable to the JDK
instead of JRE?
For compilation, certainly, install and configure the specific JDK that you want.
For runtime, you can use the one that comes with the JDK or a standalone JRE, but regardless, make sure that you have installed the right versions and that you have configured your PATH such that there are no surprises.
What is the difference between the PATH variable in JRE or JDK?
The PATH environment variable tells the command shell where to look for the command you type. When you type java, the command shell interpreter will look through all the locations specified in the PATH variable, from left to right, to find the appropriate java runtime executable to run. If you have multiple versions of Java installed - i.e. you have the java executable in multiple locations specified in the PATH variable, then the first one encountered when going from left to right will be the one that is executed.
The compiler command is javac and only comes with the JDK. The runtime command is java and comes with the JDK and is in the JRE.
It is likely that you have one version (51.0 = Java 7) of javac installed, and you also have the same version of java installed, but that another previous version of java is appearing earlier in the PATH and so is being invoked instead of the one you expect.
Had this problem when I reverted to Java 6 and tried to run classes previously compiled with Java 7. What worked for me was Preferences > java > compiler --> set compliance level to 1.6 and crucially "configure project settings"..
Today, this error message appeared in our Tomcat 7 on Ubuntu 12.04.2 LTS (Precise Pangolin):
/var/log/tomcat7/localhost.2014-04-08.log:
Apr 8, 2014 9:00:55 AM org.apache.catalina.core.StandardContext filterStart
SEVERE: Exception starting filter struts2
java.lang.UnsupportedClassVersionError: controller/ReqAccept : Unsupported major.minor version 51.0 (unable to load class controller.ReqAccept)
The Struts application is compiled with Java 7.
It turned out, someone uses "service tomcat [stop/start]" to restart Tomcat 7,
$ ps -ef | grep java
tomcat7 31783 1 32 20:13 ? 00:00:03 /usr/lib/jvm/default-java/bin/java...
$ /usr/lib/jvm/default-java/bin/java -version
java version "1.6.0_27"
Which causes the "Unsupported major.minor version 51.0" error.
When we used "/etc/init.d/tomcat7 [stop/start]" to restart Tomcat 7, the problem was solved.
$ ps -ef | grep java
tomcat7 31886 1 80 20:24 ? 00:00:10 /usr/local/java/jdk1.7.0_15/bin/java
$ /usr/local/java/jdk1.7.0_15/bin/java -version
java version "1.7.0_15"
I solved it. I ran:
JAVA_HOME=/usr/lib/jvm/java-7-openjdk-i386
The error is misleading, Unsupported major.minor version 51.0. This gives the impression that version 51 (Java 7) is not supported. And we should use Java 6.
The error should have been:
The current Java version, 50, is unsupported. Use Java version 7 (51:0 and greater) instead.`
Your Java file is compiled with a different version (higher compiler version) than the version (lower runtime version) you are trying to run it with.
It is basic understanding that classes compiled with lower versions are expected to run in the later higher versions. But the opposite (compiled with higher compiler version and trying to run it with lower runtime version) is quite not possible sometimes.
Hence you are shown this error, when trying to execute your program. Unsupported major.minor version x.x
Q: I have created an application in Java 7, but when my users try to
run it they get an Unsupported major.minor version 51.0 error. What
does this mean and what can I do about it?
A: If you compile an application using javac in Java 7, the resulting classfiles will have the 51.0 version number. Versions of
Java prior to 7 do not recognize this number, so your users will have
to upgrade to Java 7 prior to running your application. If you are not
using any Java 7 APIs you can try to compile your application using
javac -target 1.6 to create a 1.6-compatible classfile. If your
application is deployed using webstart you can specify the minimum
version required. For more information, see the docs on Java Web Start
and JNLP here. This issue will go away once we trigger autoupdate to
Java 7 for end-users currently having Java 6 on their desktops. The
timeline for this is not yet determined, we want to give developers
time to work out any issues between their code and JDK 7 first.
(Source: oracle.com.)
Oh Mac OS X I was able to solve this problem by setting the JAVA_HOME variable:
export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.7.0_75.jdk/Contents/Home
First let's get some basics right...
JRE is a component in NetBeans/Eclipse/standalone that is going to provide you with libraries, JVM, Java plugins & Java web start. Note that it does not provide compliers or debuggers.
JDK is the superset of JRE along with compliers and debuggers.
So when you have your default library as a JRE instead of JDK, you are going to have a nice time importing stuff, but it won't compile.
Instead, set your path to JDK (I use NetBeans, and I set them using netbeans.conf in netbeans/etc/netbeans.conf and change the path).
In my case the problem was in the server runtime configuration:
Check the JRE is the version you need:
The project was in version 1.7 and the server JRE was set as 1.6, after changing to the proper java version it's launched fine.
I had the problem whereby I was having to run a Maven compilation on my project from the command line in order to run my unit tests; if I made a change to the test class and let Eclipse automatically recompile it, then I got the "Unsupported major.minor version 51.0" error.
I do have both JDK6 and JDK7 installed, but all my JRE settings were pointing at 1.6, both in the pom and from the project properties page in Eclipse. No amount of Maven Update Project and/or refreshing solved this.
Finally I tried closing the project and re-opening it, and this seemed to fix it! HTH
You have compiled your Java class with JDK 7 and you are trying to run same class on JDK 6 .
Install JDK 7.0.55 and set the Java for Eclipse for JDK 7.0.55.
Build the project with JDK 7.0.55 by configuring on build path JDK 7.0.55.
Set the compiler in Eclipse for JDK 7.0.55 by menu Windows -> Preferences -> Java -> Compiler - choose 1.7.
Related
Im moving to Apache Netbeans 11.3 and trying to install the C++ plugin on Windows 10, got the follow repos
http://updates.netbeans.org/netbeans/updates/8.2/uc/final/distribution/catalog.xml.gz
http://bits.netbeans.org/dev/nbms-and-javadoc/lastSuccessfulBuild/artifact/nbbuild/nbms/updates.xml.gz
but everytime it hits the 99% it simply give me a timeout error when unpacking org-netbeans-modules-cnd-dwarfdiscovery.nbm
The Plugin Installer found problem timeout of loading C/C++ Repository[org.netbeans.modules.cnd.repository/1.32.6.1] while install the following plugins:
already try versions 10, 11.1, 11.2, 11.3, got the same issue, i even got rid of the windows firewall to no avail.
Check the Java version
For me, I have Java version 14
So this version has no program
unpack200.exe
Problem was solved by copying the unpack200.exe file from Java version 1.8 to the bin folder in java 14
copy and paste pack200, unpack200 and unpack.dil from bin of jdk13 into the bin of jdk14. This worked for me and I assure you that it will work for you. I did this with openjdk.
I'm on Mac OS High Sierra and when I click on the installer to upgrade to Ballerina 1.1.0, it installs with no error messages but when I type in ballerina version , it still shows that I have the older 1.0.5.
ballerina version
Output:
Ballerina 1.0.5
Language specification 2019R3
When I type in which ballerina, I still get the following despite upgrading with the installer:
/Library/Ballerina/ballerina-1.0.5/bin/ballerina
How do I solve the issue?
When the installer is run, it should ideally set up the path to the new executable for you. Conflicts may arise because in the previous versions of Ballerina (1.0.0, 1.0.5 etc.) it was installed (defaults in Mac) under:
/Library/Ballerina/ballerina-1.0.x
Old (1.0.x) Bin Folder
/Library/Ballerina/ballerina-1.0.x/bin
So if you have manually configured the BALLERINA_HOME environment variable and added the bin directory to your path (when you had the old versions), it will still show that you have the old version of ballerina when you look for ballerina version
There seems to have been a small change in Ballerina 1.1.0 where it installs directly into /Library/Ballerina/ so the new bin folder location to find the ballerina executable is:
1.1.0 Bin Folder
/Library/Ballerina/bin
So once again, if you have made modifications in your bash script to manually configure the path in the previous versions it might break with the 1.1.0 version. Edit your startup script (I use ~/.bashrc) to add/edit the new BALLERINA_HOME variable to your path by doing the following:
BALLERINA_HOME=/Library/Ballerina
export PATH=$PATH:$BALLERINA_HOME/bin
Then source/execute your script (I use . ~/.bashrc) and it should now work.
ballerina version
Output:
jBallerina 1.1.0
Language specification 2019R3
Ballerina tool 0.8.0
I have installed the latest version of Weka(3.9.3). I have also ensured that both Java and MacOS are up to date on my machine.
When I double-click the Weka icon to open it, it bounces for a few seconds and never opens.
I have downloaded Weka 3.8.3 to see if that makes any difference, but the same thing happened.
Any ideas on why this is happening?
I was facing a similar issue but it worked for me when I start weka on the command line.
Change directory into the weka-3-8-0 directory
cd /Applications/weka-3-8-0
invoke the jvm with the weka.jar file located in the above directory
java -jar weka.jar
We have identified the issue with the WEKA 3.8.3 and WEKA 3.9.3 applications for the Mac that, for many users, caused them to fail to start up via double-clicking.
On December 13, we replaced weka-3-8-3-oracle-jvm.dmg and weka-3-9-3-oracle-jvm.dmg on SourceForge with a new .dmg compatible with older versions of OS X, based on the HFS+ file system. Unfortunately, this new “release" included a pre-17 December 2018 version of the Amazon Corretto JVM 1.8.0_192 instead of the Oracle Java VM we had used before. Unfortunately, that particular version of Amazon’s Corretto had a bug on Macs:
"The libfontmanager in Corretto is linked to the libfreetype in X11 and breaks when X11 is not installed."
See https://docs.aws.amazon.com/corretto/latest/corretto-8-ug/change-log.html.
We never noticed this problem and could not reproduce it because if, like us, you had XQuartz installed, or the libfreetype.dylib library was installed on your Mac via Homebrew, the WEKA application still worked in spite of this bug.
We have reproduced the problematic behaviour by removing XQuartz and Homebrew on one of our Macs. And, indeed, the WEKA macOS application no longer started when the bird was double-clicked.
We have just made new “releases” of the WEKA 3.8.3 .dmg and the WEKA 3.9.3 for the Mac that use the latest version of Corretto 8 (8.212.04.2). You can find these .dmg files at
https://sourceforge.net/projects/weka/files/weka-3-8/3.8.3/
and
https://sourceforge.net/projects/weka/files/weka-3-9/3.9.3/
respectively.
They are called
weka-3-8-3-corretto-jvm.dmg
and
weka-3-9-3-corretto-jvm.dmg
respectively.
We have also replaced the links for the Mac applications on the main WEKA downloads page at
https://www.cs.waikato.ac.nz/ml/weka/downloading.html
I am using Mac OS X El Capitan, with Java(TM) SE Runtime Environment (build 1.8.0_65-b17). ColdFusion Builder 3 uses java runtime 1.6.
Is there a way to install CF Builder, but using the current JDK on my machine?
Too long for comments
I am running Windows but my version of ColdFusion Builder 3 is running Java 8 already. I did not make any changes for this.
When I click on Help > Product Details > Installation Details > Configuration (tab) this is what it reports. I am only including some of the java* information under system properties here:
java.home=C:\Program Files\Adobe\ColdFusionBuilder3\jre
java.runtime.name=Java(TM) SE Runtime Environment
java.runtime.version=1.8.0_25-b18
java.specification.name=Java Platform API Specification
java.specification.vendor=Oracle Corporation
java.specification.version=1.8
java.vendor=Oracle Corporation
java.vendor.url=http://java.oracle.com/
java.vendor.url.bug=http://bugreport.sun.com/bugreport/
java.version=1.8.0_25
java.vm.info=mixed mode
java.vm.name=Java HotSpot(TM) 64-Bit Server VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Oracle Corporation
java.vm.specification.version=1.8
java.vm.vendor=Oracle Corporation
java.vm.version=25.25-b02
I do have update 65 installed on my machine but Builder is using it's own JRE as noted above.
I asked a similar question (Install ColdFusion Builder 2 Update 1 Plug-in in Eclipse 4.3) for installing CFB 2x as an Eclipse plug-in. It seems that the requirements are fairly strict when it comes to CFB.
Here are the install specifications for CFB 3x on the Adobe site:
http://www.adobe.com/products/coldfusion-builder/tech-specs.html
It looks like this version is stuck with Java 1.7 or Eclipse 4.3.2.
Update: I was able to install Eclipse 4.3.2 (Kepler) with 64-bit JDK 1.7u80. I had to add the following to the eclipse.ini file:
-vm
D:/Program Files/Java/jre7/bin
The location of your JDK/JRE may be different.
Further Update: I was able to set up Eclipse 4.3.2 (Kepler) to use the latest 1.8u66 JDK. I modified eclipse.ini after I installed this JDK:
-vm
D:\Program Files\Java\jre1.8.0_66\bin
Eclipse Help > About Eclipse > Installation Details > Configuration has:
-vm
D:\Program Files\Java\jre1.8.0_66\bin\server\jvm.dll
So it looks like it is working with the latest 1.8.
No, it will specifically request Java 1.6 even if you edit the proper plist file (/Applications/ColdFusionBuilder3/CFBuilder.app/Contents/Info.plist). You can get Java 1.6 here https://support.apple.com/kb/DL1572?locale=en_US
You just need to find the eclipse.ini file located beside the eclipse program (or Builder as it were). In there it will have the path to the JDK. Change the path to the JDK on your system.
I installed the "Eclipse IDE for Java Developers" package from the Eclipse website. I work with C++ projects as well, so I used the "Install New Software..." menu option to install the "C/C++ Development Tools" package. After doing so and restarting Eclipse, the C++ perspective did not appear; clicking on the "Open Perspective" button did not show the "C/C++" option. I also found that I was unable to create a C++ project; the "C/C++" tree node did not appear in the New Project wizard. The Java perspective and new project options were available.
I verified that CDT was installed by going to the "Installed Installation Details" dialog - "C/C++ Development Tools" appeared in the "Installed Software" list. I tried uninstalling this package and reinstalled it again without success. I tried removing the Eclipse installation altogether and installing the "Eclipse IDE for C/C++ Developers". There were no C/C++ options in this installation either. I checked the .log file in the workspace directory and found nothing unusual.
Why are the C/C++ features not available after installing the CDT feature in Eclipse?
The path for this system Eclipse was installed on included a 1.3.1 version of the Java runtime environment and the Eclipse executable was using this version to run Eclipse. Unfortunately, there doesn't appear to be any indication of this in Eclipse, nor any indication that anything failed.
Using the instructions here, I changed the JVM to javaw.exe in a Java 7 installation. After doing so, the C/C++ perspective and new project options appeared in Eclipse.
I ran into the similar problem with Eclipse-Luna(4.4) on Yosemite(10.10).
- NOT able to get the C/C++ perspective with JRE (8u25) or java 1.6 on Yosemite.
But I manage to get C/C++ perspective with the installation of JDK(8u25).
I also had the same issue.
I just installed java7 and restarted eclipse:
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java7-installer
I had this same problem on Linux (CentOS 6.5 32-bit) with Eclipse Luna:
I installed standard Eclipse (eclipse-java-luna-SR1-linux-gtk.tar.gz)
In eclipse, under Help->Install New Software I added the p2 software repository to the list of sites: http://download.eclipse.org/tools/cdt/releases/8.5
I installed C/C++ Development Tools and C/C++ Development Tools SDK
In CentOS, I also installed OpenJDK Development Environment java-1.7.0-devel-1:1.7.0.65-2.5.1.2.el6_5 (i686).
I edited eclipse.ini to increase the Xmx setting to 1024m from 256m, but I did not add a -vm property. In the Eclipse preferences after restarting, I verified it was using JDK 1.7.
The C++ perspective was not contained in the list of available perspectives.
But C++ Project was an option in the File->New menu, and when I chose it, Eclipse asked me if I wanted to use the C++ perspective. I said yes, and it appeared, and is now available in the perspectives list as well.
The fix for me was to install the latest JDK from Oracle. I had a fresh install of Yosemite and the Eclipse for Java developers. The C/C++ option showed up after the install and restart of Eclipse. Hope it helps!