Simple as that - my eclipse (Mars Release (4.5.0) EDIT: Oxygen.2 Release (4.7.2)), when exporting a runnable JAR using the correct run configuration, keeps releasing a version of one of my classes as a version approximately 2 days old instead of the latest. I noticed as the functionality has changed rather drastically, yet the JAR keeps acting the same.
Yes I'm definitely overwriting the previous version.
Thanks for suggestions.
It appears this is a known bug, as reported on the Eclipse forums here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=525711
Here is the full answer:
The easiest workaround at the current moment is to use an older
version of the jdk for eclipse. This can be done by going into
Window->Preferences->Java->Install JREs and adding the older jdk
folder.
I've rolled back to jdk8 and the eclipse's export jar works fine, in
most cases.
If you really need to use Java9, then you're best bet is to manually
create the jar using javac or using another build system like Gradle.
Related
This question is similar to this one. I know you need to have this plugin to support Java 15 in eclipse 2020-09, however, it doesn't seem to be available any longer.
When I try to install it via the marketplace, I am getting this error:
No repository found at
https://download.eclipse.org/eclipse/updates/4.17-P-builds/.
Is there a way to install it from other sources?
I know that eclipse 2020-12 has been released, but we cannot use it due to bug #569498 (which didn't happen in eclipse 2020-09). So we would really need a way to install Java 15 support in eclipse 2020-09.
Because of regressions in 4.18, I decided to recreate 4.17-P-builds repository.
Please note this will be available till 4.19 is released or we decide to create a patch for 4.18 release.
I got a answer from the eclipse forums
Java 15 support is included in eclipse 4.18(2020-12). As part of
cleaning old releases we removed 4.17-P-builds repo as it is not
supported anymore.
Please upgrade to 2020-12 to continue work on java 15
I am fully aware that there are pages on the Gradle website that say how to upgrade, but only from 4.x and up.
I am trying to follow a tutorial in making a simple 'my first' Minecraft mod. In it, you are told to install forge 1.7.10, which, from what I understand runs on Gradle 2.0.
In order for me to continue with the tutorial, after some digging, it appears that Gradle 2.0 is not compatible with JDK 12.0.2, but I'm not entirely sure how to solve this.
any help is much 'preciated.
extending the answer from Chriki, you can change the gradle version in $projectroot/gradle/wrapper/gradle-wrapper.properties
here you can change the path to point to already downloaded gradle-bin,
something like this (distributionUrl=../../../build/tools/gradle-4.10.3-bin.zip)
or directly to gradle repository
(e.g. distributionUrl=https\://services.gradle.org/distributions/gradle-4.10.3-bin.zip)
I’m afraid, you have a chicken and egg problem here: your JDK 12 requires a recent Gradle version (at least 5.4, if I’m not mistaken). At the same time, the forge plugin that is used in your build doesn’t support Gradle 5, yet.
Maybe you can install and use JDK 11 instead? In that case you could work with Gradle 4 with which the forge plugin also seems to work. With my JDK 11 installation I could get the build to work as follows:
sed -i 's/gradle-2.0/gradle-4.10.3/' gradle/wrapper/gradle-wrapper.properties
This changes the Gradle wrapper version to 4.10.3 in gradle/wrapper/gradle-wrapper.properties (can also be done manually with a text editor). When I now run
./gradlew project
the build seems to generally work fine. It only complains: “You must set the Minecraft Version!” That’s a different matter, though.
For anyone here from Google, Minecraft Forge versions below 1.12 DO NOT SUPPORT any java version besides JDK8. You need to install JDK8.
The maximum version you can update your Gradle to is therefore 4.8.1, as any versions above that require JDK9.
To preface, I am a student and have limited experience with IDEs. My situation is that I currently have two versions of Eclipse on my machine (OSX El Capitan), one being a C/C++ IDE (Mars) and the other is a Java IDE (Mars.2). I am interested in upgrading to Eclipse Neon for my Java IDE.
Would it be a good idea to uninstall my current Mars.2 version, or just install Neon on top of what I have?
Or, is there a another simple way to upgrade?
If the solution involves uninstalling my Mars.2 version, what files/directories do I need to delete so that my C++ IDE remains functional?
I apologize for the newbie question, but I wanted to get an expert's take that I can bring into my (hopeful) career.
Thanks.
No need to uninstall existed Eclipse since it's allowed to let multi eclipse run on the same machine.
If no big change has been made from original eclipse, I suggest just download a new version eclipse and unzip it to a different folder from existed eclipse folder based on instructions from FAQ How do I upgrade Eclipse IDE?
We strongly recommend against unzipping over your existing Eclipse
version as unexpected side effects may occur, including (but not
limited to): nausea, vomitting, shortness of breath, corrupt
installation.
You can then point the new Eclipse version to your existing workspace(s) and it will load with all your projects and preferences intact.
If your you have added many plugins and preferences to current Eclipse, please follow Easiest way to upgrade eclipse 3.7 to 4.2 (Juno) to migrate the plugins and preferences. Although that's a bit of a dicey process, since many plugins would be incompatible or need to be updated themselves. Better to just install whatever third-party plugins you use into the new Eclipse installation.
This question is more of an Eclipse question, but those who have worked with Hadoop may know the answer.
Last year, I wrote some Hadoop MapReduce jobs in Eclipse. To access the libraries and packages I needed to compile the code, I installed an Eclipse plug-in off the Apache website (http://wiki.apache.org/hadoop/EclipsePlugIn). Unfortunately, that plug-in isn’t compatible with the latest version of Hadoop (the 2.0.0-alpha version). I was wondering if anyone had done any work with writing Hadoop jobs within the past few months, and knows how I can get Eclipse to recognize the most recent Hadoop (2.0.0-alpha) packages.
The plug-in still works for Hadoop 0.20.203.0, but I was hoping to be able to use the newest version.
I'm running Eclipse in Windows. I tried right-clicking on the name of my project, going to Properties then to Java Build Path and finally selecting Add External JARs
I added all the JARs from the hadoop-2.0.0-alpha/share/hadoop directory and subdirectories. At first, I thought this had worked, but when I try to use methods and constructors unique to the Hadoop 2.0.0-alpha API, the code does not compile. The libraries it is recognizing are definitely more recent than those from Hadoop 0.20.203.0, but not as recent as the current alpha version of Hadoop.
Does anyone know how I can fix this problem?
I am getting this bad version error as shown below. How to fix this. Do I need to have a separate jar file for each version of java?
(source: sourceforge.net)
How to fix this.
Is this a plugin that you created, or did you download it from somewhere?
I've never seen this myself, but I suspect that you are running Eclipse using an older version of Java (e.g. 1.5) and trying to use a plugin that was compiled for Java 1.6. Assuming that is the case you can:
upgrade the JDK used to run Eclipse to 1.6,
try to find a version of the plugin that was compiled for the Java 1.5 platform, or
download the plugin sources and build it for Java 1.5 yourself.
Do I need to have a separate jar file for each version of java?
No. A JAR file built for a Java 1.5 target platform should also work on a Java 1.6 platform. (Just not the other way around ...)
I got similar kind of error once and I was not able to fix it. And I ended up removing the plugin (EMF Plugin) and installing it on a new setup of Eclipse.
Now, I use Yoxos On-demand where you can create/add/remove Eclipse plugins with no effort. This is the best Eclipse customizer I have seen.
You are running on an older version of Java than the code was compiled for.