I have just seen that new major release (3.6 Helios) of eclipse is available for download. I want to try it, but before that I want to know if anybody experienced any major problems.
I want to determine If I could try this or not, since my project setup is complex and easily takes 2, 3 hours normally; I don't want to take any risk.
No major issue sp far.
The main problems I have seen are platform specific, like this crash in Ubuntu.
Small differences are noted in this blog post.
As usual, I always prefer a full Eclipse installation beside the ones I already have.
And for major update, I like to recreate a workspace dedicated for that release, just to be on the safe side.
That way, my old Eclipse release still has its own workspace fully functional.
I also test the plugins in both version by using a shared dropins folder.
Yes i experienced a major problem with helios, but only in WTP context. If you work with WTP you should immediately update to WTP-M-3.2.1. This should fix the issue of taking up to a minute for hot deployment (re-publishing to the server). The eclipse bug issue.
The most disturbing thing for me was the way j2ee projects are configured: there is no more j2ee dependencies, and it is not obvious at the first glance to see you have to use resource assembly (but it does not resist a few minutes searching the web).
Apart for that, I had no real issue in updating: everything went smooth, and plugins I use work well under helios.
Nothing so major, but some suggestion features are a bit buggy:
sometimes instead of suggesting to create a method, it suggest a cast, and inserts a cast to Object
when there are interfaces methods with generics, some of them are added as unimplemented even though they exist in the parent class.
These are two things I encountered for the past week.
On Windows, Helios does appears to have a pretty critical conflict with the latest oracle JDK patch (JDK 1.6 update 21):
https://bugs.eclipse.org/bugs/show_bug.cgi?id=319514
Any version before that is ok.
There is an issue with Helios and Oracle JVM 1.6.0 update 21. Eclipse launcher sets permgen size using Sun-jvm-specific command line option, but Oracle changed vendor string from "Sun Microsystems" to "Oracle", and Eclipse now fails to detect Sun-JVM, so it is not setting right permgen size. Quick solution is to set permgen by yourself in eclipse.ini.
I'm getting incredibly slow autocomplete. The bug , with a workaround, is here https://bugs.eclipse.org/bugs/show_bug.cgi?id=317979
We switch to 64bits Helios under Windows 7 recently. We saw a major improvement in memory management no more Out Of Memory errors inside Eclipse. Much better performances as well. But we have a big issue with SVN and SVN Kit plugins they are constantly displaying Malformed Network data errors or Handshake fail errors when synchronising with our repository under svn+ssh. Was perfectly running under 32 bits Indigo or Galileo.
Related
I recently switched from Eclipse to Netbeans 7.3 and experiencing a lot of quirks and i'm wondering if anyone else experienced them and/or got a solution. Because of these 'problems' i'm considering switching back to Eclipse again but i'm in doubt because NB has a lot of good things too !
These are the quirks:
when creating a new Java class, and make some typo's e.g. somewhere in a method, NB does not recognize / display the errors directly, but after a very long wait or a restart of NB.
This also happens to existing classes.
background scanning tasks is sometimes stuck at 100%
code completion does take forever. Don't even think about refactoring or renaming a class because it takes >3 minutes to scan the classpath (why, it's a new class for crying out load)
hot-deployment: changes are not always synchronized correctly with the (Glassfish) server.
Sometimes a complete undeploy and deploy is needed to reflect the changes made in the source.
NB manipules my pom.xml and glassfish-web.xml: it adds a deploy hint to the pom.xml and also changes or removes the context-root in the glassfish-web.xml. Please stop doing this!
Why o why can't i do a 'Fix imports' on my entire project. You can do a 'organize import' on the entire project, but this won't add the missing imports. See http://netbeans.org/bugzilla/show_bug.cgi?id=167031#c2
Running NB 7.3 on Windows XP, 3GB RAM, 2+GHz cpu
The project is a Java 7 maven project containing 12 modules / sub projects
I strongly recommend that you DO NOT attempt to install the ScanOnDemand plugin. It completely trashed my Netbeans, forcing me to use the Task Manager to kill the process. No existing projects were found; they were all listed as "unrecognized project; missing plug-in?". I had to re-install Netbeans.
One thing to look for is max heap allowed. Try adding "-J-Xmx2000M" to the Netbeans startup.
ref: Setting Heap Size
I suggest stick to your favourite IDE. Eclipse is still popular and Juno packages are doing good and Kepler is already available. You can try around latest packages.
IntelliJ IDEA looks better than other Java IDEs (light weight, faster, nice integration with SCM(source configuration) tools, possibility of easy cloud deployment, except that if you have freedom to choose your IDE whether you are part of a big/small teams, Otherwise there is no need to shift from one to other.
IntelliJ is the first IDE to give nice in-built support to Play framework
Google Android ADT is completely moving towards AndroidStudio based on community version of IntelliJ IDEA for faster and better GUI and app development.
As a Java developer it is not bad to try the other IDE to do some experiments or for any reason it strikes your mind.
Eg: Netbeans comes with sample apps in Java EE,Java7/Java2EE which looks better, nice examples for websockets, Servlet3.0, NIO examples etc,...but just try it or just ignore if it does not work. It is very easy to generate Entities from Database Tables, creating REST Endpoints in NetBeansIt may come with lot of in-built plugin-support for various java frameworks like RESTful webservice frameworks, JSF2.x, Primefaces3.x, SpringMVC, Struts but you may not sure to use the same version of framework. Some plugins may not work sufficient according to your business needs. Even if you okay with existing version it is not very friendly to develop Rich real-time UI development because Netbeans with Primefaces, instead you need to manually create XHTML templates.
Netbeans comes with nice support for Glassfish and tomcat, (other servers I am not sure but support is in-built). You can remote deployment with ease. Netbeans learning tutorials on JavaEE nice for beginners in the subject.
Netbeans also available as zipped bundle, hence no need to install even on Windows machines.
Eclipse has got better support with Java RoboCode learning tool (initiated by developed by IBM long ago.).
Also Netbeans comes with nice support for HTML5, Groovy, PHP, C++ as well (according to posts by users community, because I did not use them).
I have been running eclipse properly. After it loads I get:
"Initializing Java Tooling".
Incompatible magic value 0 in class file org/eclipse/jdt/internal/core/search/BasicSearchEngine
I have been looking, and what I have found is Eclipse hanging initializing java tooling
I have set JAVA_HOME and -vm in eclipse.ini
Still, no success.
Any ideas would be appreciated
=======
Added after I solved the issue
(Stack Overflow won't let me post this as an answer cause I am of ill repute.)
Never mind.
It may be important to have the answer to what I did so that people that have the same issue does not have to go through the hoops I went.
First, I went to the Help/About Eclipse/Installation Details. In the Installation History, with using compare and revert, I started reverting what I had installed (Compare and Revert are pretty cool BTW.) I finally detected which was the latest stable version, and the installation that broke it all
Spring Source at http://dist.springsource.com/release/TOOLS/update/e3.7
Initially I selected some extra components that sounded cool, but the second time around I pretty much went for the required, plus support for AOP, Web Tools, and Flex and WebServices. Other than that I ignored all the rest of the stuff. That worked.
I had selected before (one of the ones that killed it, do not exactly which one), in addition to what I left installed: Spring Mylyn Integration Spring Tool Suite AWS Integration Spring Tool Suite Maven Support Eclipse Weaving Source
I also had the "Mylyn Builds Connector: Jenkins/Hudson integration", which had worked for me in the past. I still suspect that it was one of the Spring components.
I hope this helps
Usually, a restart will solve this issue. As #Carsten mentioned, close all open files and terminate eclipse then re-launch the application. I have encountered this problem many times. The causes of this range from:
Low memory assigned to eclipse. You could increase the memory by editing the eclipse.ini file and change the options -X* JAVA_OPTS
Loading large files (XML is always a culprit in this case).
Attempting to format large XML files
Immediately after installing a new plugin and not restarting eclipse right away
etc
Clean \Workspaces\MyEclipse 8.5 M2.metadata.plugins\org.eclipse.core.resources.projects folder after closing eclipse/myeclipse .That's it.
This is an STS issue however they blame it on an Eclipse bug which has been fixed:
https://issuetracker.springsource.com/browse/STS-696. If you look at the dependencies of the STS plugin you will notice that the Eclipse WTP version is way passed the one that is mentioned in the Eclipse Bug..
For the last few years, we've used m2eclipse without issue, however it seems that the "new" version (ie. m2e) has broken backwards compatibility - something that I really hope that I've just misinterpreted.
My problem is this: I'd like to be able to build my existing project with the minimal amount of fuss. I don't have the time to write connectors for the 3 plugins that don't have them - my understanding of 2 of them is quite limited in the first place, and I have no understanding of the Eclipse plugin mechanism - but I'd still like to be able to use Eclipse to build the project.
Can I achieve this without reverting back to the old (working) version m2eclipse?
Am I correct in my understanding that there is no way to upgrade without having a connector for each plugin?
It seems as if my understanding was correct if this blog post is anything to go by:
http://grumpyapache.blogspot.com.au/2011/08/mess-that-is-m2e-connectors.html
M2E can invoke a plugin as part of the automatic build process if, and only if, there is a connector for the plugin, or you specially configure the plugin
... which means that:
You can no longer use your own plugins in the Eclipse automatic builds, unless you create a connector for the plugin, or create a project-specific configuration
The post goes on to list the issues with this approach. These are many of the same issues I have with the approach.
RANT: So there you have it - the m2e approach does suck as much as I feared it did! I was beginning to think it was just me!
I've been using STS (just started to use and learn it slowly) but some users here where I work use IntelliJ. I was wondering what exactly STS comes with that can make it better/easier to use vs. IntelliJ and vice versa. Also I was wondering if there are any plugins or ways to make IntelliJ feature equivalent to whatever could be possibly missing vs STS and vice versa so I can do an equal and fair comparison.
Thanks!
Edit,
I will say that STS takes AGES to load vs IntelliJ for some reason so if someone knows how to tweak STS to open faster I'd love to know. Even on this new MBP 15" with i7 and 4GB of ram it feels way too slow opening up and is excruciatingly frustrating when it hangs.
It's 2016 and STS has come a long way. I favor it over IntelliJ for many reasons. Some are Eclipse specific and others are pre-packaged with STS (but can be installed into an Eclipse distro).
The most valuable is the Quick Text Search. STS will index all the text in all files in your project. Ctrl+Shift+L opens the dialog and you can type any text in the bar. All occurences of the string instantly appear across all files.
I like the ability to organize imports in over IntelliJ and greatly favor the look and feel of the IDE. I've used Eclipse/STS for much longer than I have IntelliJ so I am a bit biased here.
The ability to natively handle different file types and frameworks is IntelliJ's greatest strength. I work on Grails projects from time to time and support for the latest and greatest with Grails is non-existent anymore within the Eclipse/STS family, whereas IntelliJ provides good support.
BTW: STS is free(!) whereas you can't even buy IntelliJ anymore. You merely lease the software for a year under their new subscription model.
Go to Window->Preferences->Validation
Uncheck what you don't need. That will speed up the loading a bit.
Modify eclipse.ini to set the Xmn(new generation size), Xms and Xmx, enable parallel GC
-Xmn128m
-Xms1024m
-Xmx1024m
-Xss2m
-XX:PermSize=128m
-XX:MaxPermSize=128m
-XX:+UseParallelGC
I used STS for around 2 years, and recently tried Intelij [Community] for spring web development.
I found IntelliJ much better in
performance
usability
features
Keyboard shortcuts save a lot of time (No need to use a mouse at all)
File formats supported
Debugging window
But web development and spring development is not supported in community version of Intelij, so you need enterprise version, which costs a lot [At least for Indian customers]
So, for spring development I always prefer STS and for other development (I work on Vertx as well) I prefer Intelij
I have used both STS and Intellij community edition.Here is my personal experience.
Intellij has more handy shortcuts than STS
Auto completion feature of intellij is awersome (not my priority)
Itellij has caching issues.(Major and critical). You may need to restart the IDE by clearing the cache. I have never faced such issues in STS.
Some provided plugins does not work at all (e.g Smart Tomcat).Where as STS never fails here.
I felt intellij slower than STS.
Every time I restart intellij it starts indexing which I really dont like.
When I try to import multiple projects each opens in separate windows.When you try to import as module certain configuration does not work.
All the above listed points are from my personal experince. One may disagree with this. As of now I would choose STS over intellij.
In the past I have had problems upgrading from release to release of Eclipse. I was wondering how the Eclipse users on StackOverflow dealt with upgrading from release to release of Eclipse.
Is using a Distro the solution?
Staying on a past release point until you are forced forward, a good idea?
Lately I have just reloaded from scratch; renaming my root Eclipse dir and downloaded the latest release, plus an update cycle. I have only lost my workspaces (no code was lost) once using this method.
Thanks in advance
I usually just rename the old one to something like eclipse3.3 and install the new one in the same place. Since a lot of plugins usually break with a new version anyway, in my experience, I find that to do this and then reinstall my plugins is the easiest solution. There are rarely any problems with the workspace itself.
Starting with Eclipse 3.5, it should be possible to update in-place to new major versions...but only if the update will leave you with a clean/working install.
The key thing you will need for this to work is to add the update site for the new eclipse release. The most comprehensive list of updates I've seen is at http://ekkescorner.wordpress.com/eclipse/update-sites/
I always use the built-in update system. Go to Help -> Software Updates
I use Yoxos on-demand. I've found it a lot easier to upgrade this way. It allows you to pick up the plug-ins you need and then it resolves the dependencies automatically. That way I can quickly build a new Eclipse version that contains all the features that the old one had with less hassle.