I do mostly google app engine coding, and a little bit of android development, and don't understand why I wouldn't want my Eclipse ide to always be at the most recent release, or version. It seems like there are some plugins that wouldn't be compatible, but couldn't you just install the missing features from an old release of Eclipse into the newest release?
I'd say that always having the most up to date version of program x really isn't necessary. I think the most important thing is having a set of tools that you know how to use well. Upgrade those tools when there is a reason to do so, not just because there is a new version of them.
By far the predominant reason for not upgrading is lack of support for the new release from the plugins that you require. You cannot just install "missing features". Most of the time, the incompatibility is due to changes in the new version of an existing feature. Plugins that ship from eclipse.org are tested together in coordinated releases. While in some cases, it may be possible to down-version a plugin and have that plugin still work in the new version of Eclipse, it is not something that you can depend on working. In fact, the odds of this working without issues are so small, that I wouldn't bother trying.
Stick with whatever version of Eclipse your required plugins support until those plugins upgrade their support. If they aren't moving fast enough, consider pestering the provider about this issue. If nothing else, knowing how big of a chunk of the community cares about support for the latest version of Eclipse will help the plugin provider prioritize their work.
You can do that. If you want to compile against an older Eclipse version, this can be done very easily.
e.g. if you want to develop with Eclipse 3.6:
download Eclipse 3.5 and extract it (e.g. c:\development\targetplatforms\eclipse3.5).
start Eclipse 3.6, choose your workspace where you want to use the Target Platform.
open the Menu Window->Preferences, type target in the search field, and add a new Target Platform (Nothing: Start with an empty target definition -> Add -> Direcotry -> choose the unzipped Eclipse 3.5)
There are some advantages of using a target platform. You have the newest IDE Features. You can build your product against older Eclipse Versions without having to port it to your newses IDE version. You can add Plugins to your Target Platform without contaminating your ide or add Plugins to your IDE withoud contaminating your Target Platform. ...
You should bundle your Target Platform with your Project, so you don't have to download it again. We have a TargetPlatform Project in our SVN Repostory. Every Project has a small readme how to setup the Workspace (targetplatform, deployment, ....).
Why wouldn't I want to use the newest version of Eclipse?
Because IntelliJ IDEA provides a Community Edition. :)
Related
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.
I'm not able to find the grails perspective in my latest release download of spring tool suite 3.8.2
I've created GRAILS_HOME varialble as C:\grails-2.4.4
path variable as %GRAILS_HOME%\bin
and similarly JAVA_HOME and its path variable.
Still not able to find the Grails perspective in STS.
The Grails support is no longer available for the Spring Tool Suite, at least not the Grails support that we worked on in the past. There was an announcement from Pivotal about the general topic a while ago: https://blog.pivotal.io/pivotal/news/groovy-2-4-and-grails-3-0-to-be-last-major-releases-under-pivotal-sponsorship. This also included to not working on the tooling for Eclipse anymore.
If you want to, you can download the final version of the Groovy-Grails-Tool-Suite from here: https://spring.io/tools/ggts/all. It is version 3.6.4, based on Eclipse 4.4.2.
The marketplace entry that is mentioned in another comment refers to this version of the Groovy-Grails support - and should not be installed on Eclipse versions higher than 4.4.2.
We also do not officially support and work on the Groovy support for Eclipse anymore, but there is still a version available that works with the latest versions of Eclipse.
If you are (or someone else is) interested in taking over those tooling projects, feel free to reach out to us. We would be more than happy to provide some support in taking over those projects.
Looks like this has been dropped some time ago:
http://docs.spring.io/sts/nan/v370/NewAndNoteworthy.html
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.
Do I understand correctly that the only version of Scala IDE compatible with Eclipse Luna is Scala IDE 4.0.0 Milestone 3?
I'm not familiar with this Milestone terminology. It seems to be something between stable version and nightly builds. Is it the same as Release Candidate? In old waterfall terminology would it be alpha or beta?
In other words: How safe is it?
If I already have Eclipse Luna and JDK 1.8, and want Scala support, do I really have a choice?
If someone already uses this combination, please share your experience.
And what is really confusing is that when I open Marketplace in Luna it offers 3.0x version.
Go figure...
Yes, 4.0 M3 is the minimum version that supports Luna. The upcoming versions will support Luna as well, but there are no plans to support older version of the Scala IDE on Luna.
Therefore, if you don't want to build an older version of Scala IDE, where you successfully included Luna support, there is no other way than to use 4.0M3+.
Milestones generally are equivalent to beta level I would say. M3 is the version before RC1 and RCs are not far away from final versions.
The milestones should be safe, even the nightlies are because they are already used to develop new versions of the IDE, but especially the nightlies could be broken for some days. For milestones it is more realistic that new features can be broken, but features that worked already in an older final version should be very safe.
The marketspace only offers the final version, if you want a milestone/nightly/RC you need to download it from the Scala IDE homepage.
Not really addressing the issue here, but I will anyways add an answer for people who wants to install Scala IDE(stable version) in Eclipse Luna.
Instead of going to marketplaces, go to
help -> Install new software
copy the version you want to install from
http://scala-ide.org/download/nightly.html
and paste it in the dialog box in Eclipse , press ADD.
It will list down the options,
select Scala IDE for Eclipse and finish.
Scala IDE will be installed in eclipse luna!
How do I find which Eclipse version I have on my Ubuntu system?
This is what "About Eclipse SDK" says.
Eclipse SDK
Version: 3.5.2
Build id: M20100211-1343
I am not sure if its the Eclipse IDE for Java Developers or the Eclipse Classic version.
What I would like to do is use Eclipse for
Java based Web Application Development
Ant Builds
Deploy using Tomcat
including HTML, CSS Editing
Please help me decide which version I should choose? I would like to upgrade my Eclipse setup from whatever version it is now to a version that supports all the above. Should I go for Eclipse IDE for Java EE Developers?
Should I download a totally new version from Eclipse site or can I just ADD necessary features/plugins to my current Eclipse setup.
Please suggest.
See Compare Eclipse Packages for a nice chart
What I would like to do is use Eclipse for (...)
The Eclipse IDE for Java EE Developers allows to do what you're asking for out of the box.
Should I download a totally new version from Eclipse site or can I just ADD necessary features/plugins to my current Eclipse setup.
Both would work, although it would be simpler to just get directly the Eclipse IDE for Java EE Developers (especially if you don't know exactly what plugin(s) you're looking for). Personally, I don't use the version you can get from the repository but download Eclipse from the official website and install it in user mode.
If you are using Eclipse for only Enterprise Development, then as everybody has recommended I would use the Eclipse Java EE version. If you plan on occasionally using it for other development purposes then I would consider downloading a separate classic version as well.
The reason for this is that everybody is well aware of eclipse's plugin capabilities. Unfortunately, Eclipse can get bogged down with too many plugins or add on tools. What I have experienced is that if you are using it for Enterprise Development(J2EE) it might be a good idea to keep that as a separate environment then your other Java Development. That way you can download the plugins,tools,libraries,etc for your enterprise development, and you can use your classic version for any other development you might need.
The downside is you will have two versions, but this is not a problem granted you do not run them simultaneously.
If you want to play with Web development, then the Eclipse java EE for Developers is for you. It is shipped with components to make Java Enterprise applications to create Enterprise Applications (and bundle it in an Enterprise ARchiver, known as EAR file or Web ARchive, known as WAR file).
The default Eclipse shipping with Ubuntu is the Classic version, and you can add more plugins.
I would recommend, however, to download th eJEE version manually and unzip it and run. Then you have a local installation outside the system files.