Facing a strange problem.
I recently moved my workspace to Java11. Earlier was using Spring Tool Suite 3.x but it was not working well with Java 11 so upgraded to 4.1.2 RELEASE.
The issue is I cant navigate (Cmd + Click) through dependencies code.
As shown in image below, I cant navigate through Objects below. However in my application code everything seems to be working. Also in earlier STS versions, didnt face any issues like this.
Can anyone help?
I think it is this bug:
https://github.com/spring-projects/sts4/issues/205
It is already fixed in the latest nightly builds of STS4 as well as the latest snapshot builds of LSP4E. If you don't want to wait for the STS 4.2.0 release (should be coming next week), you can install the latest version of LSP4E from their snapshot site.
Related
My application isn't running correctly with Java 9. In order to debug it, I upgraded to Eclipse 4.7 (oxygen) since Neon doesn't have Java 9 support, and applied the Java 9 support patch.
After doing so, eclipse was failing to load any of my pre-existing Java Applications. Thinking it might be a version difference thing, I deleted them, to try re-adding. But when I click the "New" button to add a configuration, nothing happens.
If I double-click "Java Application," I get the following error:
An error has occurred. See error log for more details.
tried to access method org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.getTabViewer()Lorg/eclipse/debug/internal/ui/launchConfigurations/LaunchConfigurationTabGroupViewer; from class org.eclipse.jdt.internal.debug.ui.launcher.LocalJavaApplicationTabGroup
I am able to add configurations for other types of applications (Java Applet, Eclipse Application) so it seems only to be an issue with Java Applications.
I also tried a fresh workspace, but that has the same issue. How can I fix this?
This is kind of a duplicate but since I experienced the issue and have seen a few others post about it, I'll post my answer of how I fixed it here.
If you go here: https://marketplace.eclipse.org/content/java-9-support-beta-oxygen/
You need to follow the step about updating Eclipse 4.7 from the link that ends in 4.7-U-builds. When you go to Install New Software and select Eclipse SDK, click Next until you get to the Install Remediation Page, and make sure that you are selecting the second option that says something like "update my installation to be compatible with the items being installed" instead of the option that says "keep my installation the same and modify the items being installed to be compatible."
The first time I installed Java 9 updates, I did it the latter way and ran into this problem. Now that I've gone back and chosen the former, I am able to add Java Application Run Configurations again.
Hope this helps.
Eclipse Oxygen.1a (4.7.1a) Release
Update as of 11 October,2017 - You shall upgrade to the latest eclipse package Eclipse Oxygen.1a (4.7.1a) which is marked as released and supports Java 9.
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.
This question has been bothered me for a long time, and I guess it's too general and basic so that a quick google can never point me to the right answer.
For example, 7.3.1 has just been released, and my currently installed NetBeans (7.3) notified me that there were some components to be upgraded. After I did the upgrade and restarted NetBeans, its title bar still shows 7.3.
So, are the new features of 7.3.1 included in my NetBeans now?
If so, can anybody give me the link of the official documentation that mentions this?
Version 7.3 is the same as version 7.3.1. You are talking about the same thing. Now upgrades to components is different.
Now by upgrading components you receive new functionality and fixes on the actual plugins and NOT on the IDE engine itself.
Bottom line, yes your IDE is up to date now despite the fact that the plugins might not be completely up to date.
I have around 5 projects in my Eclipse, all of them were working and compiling just fine but since last eclipse and sdk update I've got a strange bug with mobclix and admob libraries:
app is compiling fine without any errors but when I open any activity with ads it crashes!
Error:
E/AndroidRuntime(22504): Caused by: java.lang.ClassNotFoundException: com.mobclix.android.sdk.MobclixMMABannerXLAdView in loader dalvik.system.PathClassLoader[/data/app/com.rvanavr.app.apk]
I've spent a day trying to fix this bug:
- removed/added library
- cleaned project
- reinstalled sdk
- reinsalled everyhing
Did somebody face this bug? Really need you help guys!
Yes, I had the same issue yesterday, and found that the problem maybe related to how ANT builds the projects underneath eclipse. I too started seeing this problem right after I upgraded Eclipse ADT plugin, and also get the latest updates for Android SDKs (API versions 10 and 15). So, generally based on other stackoverflow questions, I upgraded eclipse as described below, and the problem went away. The way I understand is that Eclipse's build system wasn't including mobclix.jar in the final build, and did not report any errors or warnings to alert this fact. Here's how I upgrade eclipse:
Eclipse Help Menu -> Install New Software, pops up this window:
Select "The Eclipse Project Updates" - I'm using version 3.7 (Indigo). Then click on "Select All", and hit "Finish". All Eclipse components that aren't up-to-date, will get upgraded to the latest. And then it'll ask you to restart Eclipse. When I did that, and rebuilt my project, I didn't have any problems with mobclix.jar and undefined classes.
Btw, after the upgrade, here's my Eclipse version (in case you want to compare your current version to mine):
Version: Indigo Service Release 2
Build id: 20120216-1857
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