I was using Eclipse CDT 3.8 (Indigo, I think) with a generated project from cmake, and everything went well to me. But recently I change to Eclipse CDT Kepler (same project, generated again to match the new Eclipse version, 4.3 ) and now the search functionality isn't working properly, some things I was capable to find in the older version, I cant find them now.
I did my homework, and I looked for some incompatibility issues. Without results.
Some one knows which can be the problem.
Related
So I have just installed the latest eclipse version (4.6.3) on my laptop which had 4.6.2 running before.
The problem is that all my eclipse plugin projects are now full of errors because it somehow can't resolve various bundles (swt, osgi, eclipse.core, eclipse.ui, etc).
Furthermore I have noticed that the target platform the PDE sets up as default (which is the running platform) complains that it can't find the respecive plugins either.
I don't know if these two issues are connected but it seems to me that eclipse can't find it's own plugins which would be very weird...
Does someone has an idea on how to fix this?
I am beside myself with this error and can't make any progress until I get past this issue.
I have the latest STS (Spring Tool Source) 3.7.1 specifically for Eclipse Mars 4.5.1. I deleted all my old versions of STS, and deleted my old .eclipse file as well since I wanted this to be a fresh install. I also went into my c:\Users\Tom Holmes\AppData folders and removed all traces of 'Spring Tool Suite'.
I installed the new latest STS 3.7.1 for Eclipse (Mars) 4.5.1 and pulled down the latest Subclipse for the Eclipse (Mars) 4.5.1. I opened to my old work space which was fine before, and now whenever I try to use STS to run a maven build I get the error listed below.
Error: Could not find or load main class Holmes.sts-3.7.1.RELEASE.configuration.org.eclipse.osgi.25.0..cp.;.C:.Users.Tom
I have tried everything I can think of to re-loading the projects into a new workspace, to deleting the projects and re-downloading them.
Ultimately I find in the workspace .metadata plugins directory under m2e.eclipse.core there are no lifecycle mappings? Does that matter?
How can I re-create this, or is this more of a maven/sts problem?
So, here is what I found ... Since STS 3.7.1, specifically for Eclipse (Mars) 4.5.1 was the issue ... I tried several other versions of STS.
I tried STS 3.7.0 for Eclipse (Mars) 4.5.1 which does work. When I installed this, I immediately got notified that there was an update ready. The update was specifically for the m2e Maven-Eclipse Integration.
I also tried 3.7.0 for Eclipse (Juno?) 4.2.2 which also does work, and again this was looking for an update, and again was for m2e Maven-Eclipse Integration.
My feeling is that, specifically STS 3.7.1 for Eclipse (Mars) 4.5.1 was broken as far as the m2e plugin. Since the m2e changes are embedded in this latest version, something must not have been right. The other versions that I downloaded and installed all worked fine. For any of these versions, there was this upgrade for the m2e (Maven-Eclipse) integration plugin ... but in this case, the update worked.
You know, I like STS, I think it works great. After updating several times, like anything else, it can get "jinky" and then I decide that maybe I should just download a new fresh copy of the tool which usually works great.
Clearly pulling this update into the latest version just didn't mesh well. But now I am up and running, and hopefully SpringSource will fix this issue.
I really hope this helps someone else out.
I would recommend installing a regular Eclipse distribution and then installing STS as a plugin. There should be plenty of instructions online that explain how to do it. I've been using this approach for years and never had any problems.
Moving from Eclipse 3.7(Indigo) to Eclipse 4.3 (Kepler). Have WTP installed on both, with JSP editor, different versions of WTP (3.3.2 vs 3.5.2)
Got a problem with javascript syntax highlighting in new version, in jsp. Javascript isnt highlighted if its within html comment.
Compared all possible settings but couldnt find how to solve this question. There's chance i didnt install something additional for that but have no idea what, would appreciate any suggestions.
Screenshots of both versions:
So I researched a lot about this problem and haven't found anything useful for me yet.
It is mainly about this bug with:
[Java CocoaComponent compatibility mode]: Setting timeout for SWT to 0.100000
Which seems to be related to a bug Eclipse know themselves.
I have tried running Eclipse Indigo, Eclipse 4.2.1 and Eclipse 4.3 with the same result. I tried starting the Eclipse on the second thread as suggested by somewhere "-XStartThreadSecond"<--- something like that, but Eclipse dont recognize that anymore it seems. So maybe someone found a solution to this after so long time?
I am running OSX Mountain Lion, JRE 6, above Eclipse's and I also tried making JRE 7 work in my Eclipse, but the JRE 7 VM dont exist in the folder it should be(I Haven't installed anywhere else).
EDIT:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=212617
http://www.eclipse.org/forums/index.php/m/809088/
I had the same problem when I was using JFreeChart, however none of the solutions worked. Every time I tried to run java application that created a JFrame it crashed on a Mac.
However, I had realized that I have had included all libraries that came with JFreeChart in the Project build path. If you have the same problem, check your library under:
Project -> Properties -> Java Build Path -> Libraries
All you need are: jcommon-1.0.17.jar, and jfreechart-1.014.jar
If you are not using JFreeChart, still check your build path if you are using some conflicting libraries.
Cheers!
I had the same problem using JFreeChart with Eclipse on OSX. It seems adding only jcommon-1.0.17.jar and jfreechart-1.014.jar into your JAR reference path instead of the whole list of libraries is the solution.
Thanks
I spent a couple of hours yesterday trying to get LunarEclipse to work with Eclipse 3.4.1 and DLTK 1.0
I looked at some bug reports at their sourceforge project page and they said that their 1.2.9 version was supposed to work with DLTK1.0. Problem being they hadn't actually released the 1.2.9 yet. You could get it at their SVN repository though.
I downloaded their svn repository. To my dismay I could not for the life of me remove all errors from the project. It kept saying it couldn't resolve org.eclipse.core.runtime.IProgressMonitor even though I added the org.eclipse.core.runtime external .jar file.
I guess the 1.2.9 isn't quite finished yet. So I wondered if anyone had some tips on what to do. Maybe I should just get an older version of eclipse and DLTK.
I have checked out LuaEclipse, but that didn't work either.
Summary:
Have anyone gotten LunarEclipse to work with eclipse 3.4.1?
Can you recommend any other Lua IDE or plugin for eclipse?
Beta release of LuaEclipse 1.3.0 does work for me and it is quite stable (except for the debugger plugin).
Grab it here:
http://luaeclipse.luaforge.net/preview/update-site