In my old Eclipse (version 3.4.2) if I wrote an error in a java fragment inside a .jsp page (example a variable that doesn't exist) I automatically and immediately saw the problem (red line under
the word).
In Eclipse neon I have to manually validate the page (right click, validate) to obtain the same result.
Is it possible to configure the new version with the old feature?
You can try to go to Window > Preferences > Java > Compiler > Errors/Warnings
and set up your things here.
This feature is also included in Eclipse Neon, don't worry ;) but if you really struggle hard, I suggest an uninstall/reinstall
Related
I am working with Eclipse Photon 4.8.0 and I'm facing a weird behaviour when I'm working with Java files.
When I make a change in a file, usually Eclipse refresh the code reviewer automatically, marking errors and warnings on the fly in the code. This is not happening to me. The code marks appears or disappears only when I save the file.
I suppose there is some preference option to allow auto-refresh for this code checks, but I can't find it.
In Window > Preferences: Java > Editor check the checkbox Report problems as you type.
I think that actually it's not a fix for the problem, but I delete this Eclipse and downloaded Eclipse Oxygen. Now it works. I suppose it's a bug for the new Eclipse Photon.
I'm running an Eclipse Luna. Additionally I installed Nodeclipse.17.plus via the marketplace and checked all provied tools. This also includes the Nodeclipse Coffee-Script viewer:
CoffeeScript Editor let's you edit *.coffee files with some advanced features.
Highlights include
- syntax highlighting
- variable autocompletion in the current namespace
- correct autoindent
Additionally I activated XText Nature for that project.
But there is still no syntax highlighting for *.coffee-files.
Have I done anything wrong? (By the way, the Nodeclipse EditBox is working, but it is not sufficient to make CoffeeScript readable for me)
The Nodeclipse CoffeeScript Viewer seems to be installed:
But it does not appear in the List of internal editors:
I'm afraid that there is no satisfactory answer to your question.
On http://marketplace.eclipse.org/content/nodeclipse-coffeescript-viewer-editor-eclipse-431 it says:
There is problem since Eclipse 4.3.1 release https://github.com/Nodeclipse/coffeescript-eclipse/issues/19
Get 4.3.0, e.g. as Enide Studio 0.5.x http://marketplace.eclipse.org/content/enide-studio
Help us if you know Eclipse XTEXT.
and
We were looking for new owner familiar with XText technology.
To me it seems, that there are profound problems with this plugin.
I also had the problems with a missing entry in the list of internal editors after installing nodeclipse. I simply removed the plugin and reinstalled it. But than I ran into those XText-problems
and finally gave up,...
This plugin for Coffeescript in Eclipse is a little buggy but maybe you could try it - https://github.com/adamschmideg/coffeescript-eclipse/
Installation steps are given in the README.
Try this
1.Open "Window" -> "Preferences" -> Expand "General" and "Editors" -> Click on "File Associations" -> "File types:". Add ".coffee" to the list if it does not appear.
2.Look for "Associated editors:" in your "File Associations" dialog then click "Add"
3.Select "Internal editors"
4.Select "Coffee-Script Viewer". Click "OK" then "OK"
Eclipse Pluging For Coffee Script
Every time I start Eclipse and press Ctrl + Space I get the following 3 warning popups.
http://imgur.com/a/2pKdm
They are only appearing the first time I press Ctrl + Space.
I get these warnings since i reinstalled the jdk.
I already tried to re-install eclipse, but as soon as I import my old projects the warnings seems to reappear. I currently have the following java versions installed:
JVE 7_u7 32bit;
JVE 7_u7 64bit;
JDK 7_u7 64bit;
JDK 7_u7 32bit.
I added all of them in the PATH variable in the same order as listed above.
I also have eclipse set to use the JDK 7_u7 64bit (btw I'm using eclipse 64bit).
I hope somebody knows a solution for my problem and excuse me for my bad english, I am not an native English speaker. ;)
You can resolve this issue by turning off Subwords-Completion in:
Window > Preferences > Code Recommenders > Completions: ==> incheck(Subwords-Completion)
I got the similar type of warning is eclipse spring tool suite(sts) .I unchecked CodeRecommendors Proposals(addons) which is present 2 times in the above list and below list and it worked.To do it go to window-->preferences-->java-->editor-->Content Assist-->advanced.see the screenshot.
You can configure content assist and disable the triggers in content assist. This link provides information on setting content assist preference.
I would like to share my experience for those who have this problem in the future. If you changed the theme of your editor recently, first change it back to the classic theme and then restart Eclipse. Then switch back to the theme(maybe dark theme) you want to use and restart Eclipse again. This is how my problem was solved.
I'm using "Eclipse for Java Developers 7.2" and Scala IDE 2.1.0. The issue is "code completion"...
I have "Use Scala-compatible JDT" and "Enable JDT content assist" enabled under my Eclipse.
Are there any other options I shuold turn on?
re-enable all the following unchecked java content assist mechanism in the scala-ide preferences:
Preference window:
/Java/Editor/Content/Assist/Advanced
preferences to check in the 'default' content assist panel:
Java Proposals
also enable the Java Proposals in the content assist cycling panel thats in the lower part of the window
Finally I got luck to solve this.
The reason behind why this happens is because eclipse stores a .metadata file in , which acts as a cache to load auto-complete suggestions.
If you try Project->clean, and then try the auto-completion the required java class members can be found in auto complete suggestions.
So the SOLUTION IS:
go to your eclipse.ini, in case of mac located at:
/Applications/eclipse/Eclipse.app/Contents/MacOS/eclipse.ini
and add "-clean" in the ini file just before "-project".
This has a down impact of that now your eclipse might take a minute or two longer to start for the first time. But for me , it was acceptable.
I'm new to Eclipse and downloaded the following version:
Eclipse Java EE IDE for Web Developers.
Version: Indigo Release
Build id: 20110615-0604
[edit] Eclipse Platform Version 3.7
I have edited Java > Editor > Save Actions to do the following: Remove trailing white spaces on all lines, Correct indentation
When I save the .java file, those actions are not applied... is this a bug?
Found this that might be related: https://bugs.eclipse.org/bugs/show_bug.cgi?id=350475
Assuming that this relates to JavaScript files, then the related Eclipse bug could be helpful.
The problem (as I've just experienced) is that you can edit the JavaScript -> Save Actions preferences via the context menu when editing a JavaScript file, but the actions will not be run.
The solution is to right click on the project containing the .js file, and select Configure -> Convert to JavaScript project.
The bad news is that this will then will also enable Eclipse's not-so-great JavaScript validation, therefore telling you that libraries such as moment.min.js are broken.
Well for those of you who have found this topic... I did find 2 solutions, no thanks to Eclipse, other than the fact that it is open source and people can write plugins.
Eclipse Platform Version 3.7
AnyEdit - plugin that does it for you when you Save file (I believe this is what eclipse SHOULD be doing)
Go to: Window > Preferences. Then under General > Keys. Make sure drop down for Scheme: is Default and enter 'remove trailing' in the filter. You should then see "Remove Trailing Whitespace" under the command column. Bind it to your own key command.
The only drawback to #2 is that you have to actually press the key binding while editing the file, kindof like a cleanup action.
Too bad Eclipse hasn't taken the approach that ALL file types should be configurable in this way... sometimes I miss TextPad.
Old question, but at least for newer Eclipse versions there's a better solution: Go to the project properties, then to Project Facets. If it tells you that your project isn't in faceted form yet, then convert it. Afterwards (or if it already was faceted), just enable the JavaScript checkbox.
I had the same issue with Eclipse 4.4 (Luna) and this fixed it for me, the save actions are now executed on save.
Adding to jlh's answer, I also had to configure the JavaScript include path of the project to enable save actions. Before that even a manual "Clean Up ..." from the source menu wouldn't work.