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..
Related
I am not an Eclipse/RAP developer, but over a year ago I was tasked with getting a particular application to run. The development environment was Eclipse/RAP using Java. The application was already almost done -- I just needed to make a few changes to get it to work the way we wanted it to work. I made the changes, stuck it into the Jboss app, and it worked. I saved away my source code.
Since then they upgraded my PC, so I no longer have access to my old development environment. We need to move the RAP application to another server, and for some reason it has quit working. Either I don't understand why it ever worked or I don't understand why it doesn't work -- it's all a bit baffling.
So now I'm trying to get this thing working again.
The basic problem I haven't been able to resolve is dependencies. Eclipse reports that the following three bundles can't be found:
org.eclipse.rap.draw2d
org.eclipse.rap.zest.core
org.eclipse.rap.zest.layouts
All three should be in the GEF package.
I have tried installing Eclipse Indigo. When I do that, Eclipse can't find GEF to install it, even though it's given the same URL as I give to Kepler. I've installed Eclipse Kepler. I can install GEF, but while Eclipse reports a valid install, and reports that it is installed, I'm still seeing the same missing dependencies.
Any ideas? It's baffled an Eclipse developer here, but then we don't really use RAP except for this one application.
Any help at all would be greatly appreciated.
Sean.
This is a dependency-related issue, and has nothing to do with RAP. Nevertheless, be careful that the notion of GEF has changed a bit. GEF4 includes: GEF, Zest, Draw2D. Rather than installing the whole thing, I suggest you download your dependencies (i.e. go to GIT and pull the GEF4 project), and then include those projects (or build them as JARs) and include them to be available at runtime, and of course as dependencies.
I was trying to set up GWT(Google Web Toolkit) on my system using it as a plugin for eclipse Indigo. I am currently on a Ubuntu workstation. Upon restart after the installation, eclipse simply crashes without any error info. I did look around here on stack overflow , as well as on google about what could be done, but the things which seemed to work for others do not seem to work for me.( deleting certain .jar files, deleting the metadata folder in the workspace).
Any help would be great.
Regards
Problem solved. There is a bug in Indigo , exposed by the plugin. All that needs to be done is to check for updates first and then install the plugin. The bug has been fixed in one of the point updates.
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 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.
If I start with a Eclipse IDE for Java Developers (85 MB) (Ganymede) installation. What plug ins do I need to install to be a able to:
See the Server tab and being able to add my Tomcat 6 installation.
Be able to create a Dynamic Web Project which I may connect to my server.
I want to be able to start and stop the server.
See the server Stdout-output in my Console tab.
Debug an application on the server.
I want to install as little as possible, as long as I can do the above things I am more than satisfied.
Especially since I have problems with the complete Web Tools Platform (WTP); according to me it's full of bugs related to validation. It sometimes says valid files are invalid, often it helps if you simply restart Eclipse. I have also found it to ignore exclusions as well as sometimes completely ignoring that I have disabled validation all together.
The problems I've experienced have made me uninterested in anything from the WTP project, except the plug ins enabling me to work more smoothly by fulfilling the above unordered list (because that part of WTP worked really well).
I have heard the some have had success with Sysdeo Eclipse Tomcat Launcher Plug-in together with Ganymede. But since it's officially not supported and there has not been a new release since May 2007 and running it with Ganymede involved changing the plug-in files to accept versions >=3.4 I don't see it as a long term solution.
Installing parts of the WTP but not it in its whole feels like a long term solution while at the same time skipping the error ridden parts of the WTP. But I need help with which parts I need to install, as the documentation on Eclipse.org does not explain. Of course, if there is another supported solution than using parts of WTP then that is of interest too!
When I display the "eclipse Plug-in Dependencies" view for org.eclipse.jst.server.tomcat.ui, I see:
org.eclipse.wst.common.emf
org.eclipse.wst.common.emfwrokben.integration
org.eclipse.wst.common.environment
org.eclipse.wst.common.frameworks
org.eclipse.wst.common.modulecore
org.eclipse.wst.common.project.facet.core
org.eclipse.wst.common.project.facet.ui
org.eclipse.wst.common.uriresolver
org.eclipse.wst.internet.monitor.core
org.eclipse.wst.server.core
org.eclipse.wst.server.ui
org.eclipse.wst.validation
So if you can select org.eclipse.jst.server.tomcat.ui through p2 and let that "update process" to pick the dependencies for you, you should end up with the minimal set of plugins needed for running/managing Tomcat on Eclipse (with WTP).