I am using the Eclipse compiler and have enabled 'Build Project Automatically'. I am not using the power saver mode as well.
This should be a trivial thing to solve for IDEA, but for some reason, they decided that they shouldn't. Suppose I have a class A that uses a field from class B. Now if I make a syntax error in B, it highlights that class in the project windows. But if I delete the field that is being used in class A, no highlighting is done in class A, until I actually open it.
Eclipse does it so well. Am I missing something or is this feature really not present in IntelliJ?
Related
For Java, in the editor of a class, I am used to hovering over an unknown class to bring up the quickfix menu which suggests imports to resolve the problem quickly.
Is there any such feature in the Scala IDE for eclipse? Hovering over an unknown class in a scala file does not bring up anything for me, so I end up typing imports manully. That is pretty annoying.
On a mac: CMD+shift+O adds imports as necessary and putting the cursor on a class name and doing CMD+1 does it for that one thing. Non-mac I'm sure has similar.
I'm using IntelliJ 13 and the Scala plugin. In one project if I make an obvious type error I get a visual indication, like this:
But I just started a new project and a similar thing is not highlighted, even after I compile.
I'm giving a presentation on some Scala code and I'd like it if the type errors highlighted like in the first one, but I have no idea where the setting is.
One reason could be that the level of highlighting is set to a lower setting. Check your lower right corner for a button which adjusts this setting with a slider. It looks like (at least to me) a policeman face :)
Another thing is that you might not have declared what additional languages you're using besides the primary one. You can configure this in the project settings.
Also if you are using a tool to build a project (like Maven for example) try rebuilding or reimporting your project.
edit: One last thing. Make sure IDEA isn'currently reindexing or running some background tasks, this really messes up code correction.
There seems to be a bug in netbeans 6.9.1 when it generates the ResourceMap code. My project is called ScriptedResponseApp and the main entry is ScriptedResponseAppView. So, for all the dialogs, I should get something like
org.jdesktop.application.ResourceMap resourceMap =Application.getInstance(ScriptedResponseApp.class).getContext().getResourceMap(SomeDialogClass.class)
but instead I get
org.jdesktop.application.ResourceMap resourceMap = org.jdesktop.application.Application.getInstance(scriptedresponseapp.ConsoleView.class).getContext().getResourceMap(SomeDialogClass.class);
Where ConsoleView is another unrelated class in my project. Why is netbeans picking ConsoleView up as my main class and how do I fix it? As a work around, I've been closing netbeans, editing the code in a text editor, and reopening netbeans. It work until I make a change to anything involving a resource file, which generates out this same wrong code.
Any ideas on how to fix this annoying bug?
I dont know if it's a bug. In my case, I refactored the main class, but Netbeans don't change the project.xml (nbproject folder).
I mannualy change and it worked.
I'm using Scala plugin for IntelliJ IDEA and my project has a few thousands lines of source code.
Unfortunatelly, when I'm typing the code IDE freezes frequently(i.e. on code completion etc.). I tried to switch off inspection, but there was no effect.
Is there a way to turning off all plugin's features for using it just as syntax highlighter and build tool?
Try closing or reconfiguring all views that show detail at the level of individual class members (methods, vals and vars, basically). Specifically, that's the Structure view and the Project view when the "Show Members" option (in the "cogwheel" menu at the top right) is enabled. It is reported that maintaining these views slows the Scala plug-in appreciably.
You should also get the 9.0.4 EAP of IDEA (currently #95.538) and stay up-to-date with the Scala plug-in nightly releases. There sometimes bugs, but as a rule, quality is good and progress is sufficient to warrant doing this.
Edit:
The two views that do (or can) present information at the class member level of detail and which can slow the plug-in substantially are:
The Structure tool window (Window -> Tool Windows -> Structure / Alt+7)
The Project tool window (Window -> Tools Windows -> Project / Alt+1)
The Structure tool window always shows the class member level of detail, so if it's open, you're susceptible to this slow-down. The Project tool window only shows class members if you configure it to do so. The way this option is controlled is in the menu that is attached to the "cog wheel" or "gear" icon in that window's upper-right corner. The option to disable in that menu is "Show Members."
Try IDEA X EAP plugin version. It's much faster.
I have what appears to be a very annoying problem. When compiling a project in Eclipse, I see no Console that shows the invocation of the Java compiler and the build results (as in NetBeans).
If I, for instance, import an existing project into Eclipse and invoke Project->Build Project, is there a view that will show me results of the compilation? While I know that my project contains a number of files that have errors, invoking Build Project shows no visual result/progress of the compilation. It does not show the list of errors so that I can quickly jump to them.
I'm aware that there is a "Problems" view, which shows a list of problems (and not just compiler errors) in all projects and not the particular project that I am working with, which makes it very inconvenient to locate and jump to source of the problem.
You can configure the problem view to show only problems in the current project:
Click on the small triangle at the far right of the view.
In the popup menu, select "Configure Contents..."
Select each item in the "Configurations" list and click on "Scope: On any element in the same project"
If you want to see the compiler working, you need open the "Progress" view.
Since Eclipse JDT provides its own built-in Java compiler, you generally do not see the invocation of Java Compiler.
The built-in Java compiler is tightly integrated with Eclipse and JDT, and provides the source indexing that enables powerful IDE features such as refactoring and quick fix.
Plus, it enables incremental build in background after each file modification, hence no visible "java" invocation.
You can replace/complete the java compiler with a javac` call of your own:
For instance, Using Alcatel-Lucent nmake with Eclipse JDT does precisely that, and uses a configuration launcher (which you can instruct to show a console):
You will need to add that special builder in the "builder" section of your project.
Do not forget you can create many "Problem view", and set one of them to show only problems for your current project.
Select: "on any element in same project"
Goto Windows->Show View->Console
or
Alt+Shift+Q,C
Console appears in tab with Problem view
Your question contains a couple of assumptions that you might want to re-think.
It does not show the list of errors so that I can quickly jump to them.
Errors are flagged in the edit window while you are editing. You can fix them on the spot, without having to "jump" anywhere.
If you drop an entire source file into your project, you may not be in an edit window on that file. (And, of course, that's not standard Eclipse usage.) The simplest way I know do deal with that is simply to "Refresh" the project and look in the Package Explorer view to see whether there are any errors detected (which will happen immediately if you "refresh" a file into a source folder). Double-click on any files which show an error icon and look at the right-hand side of the edit window to see exactly where the errors are.
I'm aware that there is a "Problems" view, which shows a list of problems (and not just compiler errors) in all projects and not the particular project that I am working with...
Unless you are using multiple projects, with inter-project dependencies, I find it useful to close all but the current project on which I'm working. Then the "Problems" view is specific to the current context.
Finally, I'd recommend looking at the Mylin "getting started" page for other hints on how Eclipse can help you focus on the current task.