I'm one of the developers of QxCompiler, a node-based javascript compiler and linter for the Qooxdoo project. Like any compiler, it outputs a series of errors and warnings with line numbers but at the moment this is only output to the console. As a developer, you can Alt-Tab round to read the output but it's easy to forget to do that and it would be very useful to use Eclipse's existing code marker system to show the list of errors and highlight them in the source code.
How do I output this to Eclipse so that it will incorporate the errors and warnings into the source code?
What would be really useful is if there is some kind of IDE-neutral standard for formatting the output of the compiler so that it'll work on more than just Eclipse...
here some thoughts:
LSP
If you are interested in bringing up output into multiple IDEs in a neutral way, you should refer to https://en.wikipedia.org/wiki/Language_Server_Protocol where LSP is described. As far as I know it can be used for code completion, outline support etc. Maybe it will fit your requirements.
Eclipse Log plugin
Another option is to send the output to a log file and use plugin for log files in eclipse..
Do as done in Jenkins Editor eclipse plugin
You could also provide a REST API and maybe even a CLI tool. This is how jenkins linter works. There is a jenkins editor plugin for eclipse which does use the CLI tool (REST API) to bring up messages and errors into the eclipse editor.
See https://github.com/de-jcup/eclipse-jenkins-editor/blob/master/jenkins-editor-plugin/src/main/java-eclipse/de/jcup/jenkinseditor/handlers/CallLinterHandler.java for an entry point to look into sources and how it was done.
Some addititional explanations can be found at https://github.com/de-jcup/eclipse-jenkins-editor/wiki/Validate-by-Jenkins-Linter
Related
In eclipse, for cucumber feature file using for selenium,
When a feature file was opened, the feature file used to show in cucumber/gherkin format which doesn't show anymore.
When a feature file is created, sample features used to be created
When a feature is executed using dry run, Step definitions used to be created.
src/test/java and src/test/resources are showing greyed out in eclipse which was not the case.
Above mentioned three things are not happening any more which used to work earlier. I believe it's related to the set up of eclipse. I know the issue, not sure what details might be required. So please do let me know what might be required so that I can share here.
Eclipse Version:
Version: 2019-09 R (4.13.0)
Build id: 20190917-1200
That means either your editor is disable or corrupted.
1)
Try to open your feature file again as below:
Select other if cucmber editor not shown.
2)
Uninstall the cucumber plugin and install again.
Refer below link to uninstall the plugin from eclipse
Correct way to remove plugin from Eclipse
When a feature file was opened, the feature file used to show in
cucumber/gherkin format which doesn't show anymore.
Changed the default editor to cucumber, Not sure how default editor
was changed
When a feature file is created, sample features used to be created
After changing the default editor to cucumber, this started working
When a feature is executed using dry run, Step definitions used to
be created.
Added this parameter in the
#CucumberOptions(plugin = {"pretty","summary"})
src/test/java and src/test/resources are showing greyed out in
eclipse which was not the case.
Not sure, but this is not creating any issues so far
Associating feature file type with cucumber in Selenium WebDriver
I don't know the reason but I am also having a similar problem occasionally. When you over the file name go to the file tab and choose properties and then choose Associate with File Type --> then choose cucumber. I hope it helps.
I am currently looking for the latest version of the decompiler plugin for Eclipse (Kepler). Does this tool still exist?
I have downloaded jd.ide.eclipse.feature_0.1.5.jar and placed it in my plugins folder for eclipse but it does not seem to work. I have also copied JAD.exe into my local file and I point to that location for Path to Decompiler in JadCliple preferences. I have also set File Associations to read *.class as JadClipse Class File Viewer to default. Is there something else I am missing here? I have read past posts on this website and I see that access to the website has been the main problem. If anyone can guide me in the right direction this would be great.
I keep getting this error, The Class File Viewer cannot handle the given input ('org.eclipse.ui.ide.FileStoreEditorInput').
Instead of using JD-GUI or other GUI based tools, you may want to consider command-line decompilers that are frequently updated like the ones below:
Procyon
CFR
Both of these (should) support new Java 8 additions and other things that JD-GUI usually fails on.
In the pydev liclipse editor how do add javascript folders so that it doesn't show errors in javascript files, such as $ is undefined (doesn't know jquery is also loaded when file is run).
I have tagged it with eclipse but this is a fork built around pydev "liclipse" so i don't see "javascript" as a project type.
TIA
Well, the LiClipse validator currently integrates JSHint internally (with Rhino), and there's no option to disable it...
Still, you can add a comment to the top of the file so that it knows that some symbols are expected to be undefined.
I.e.: if you add:
/*global $:false,alert:false*/
to the top of your file, the $ and alert symbols won't be triggered as not-defined.
I don't know anything about liclipse, so can't be certain my answer is correct. But I'd guess you will need to install some Javascript tooling in order to properly handle javascript code and projects. The options for Eclipse are not great, but there are JSDT and VJet.
I'm using Intellij IDEA/Android Studio.
I was asked not to make any commits unless my code doesn't trigger any warnings in Problems View of Eclipse IDE.
So, is there any quick way to port Eclipse's analysis configuration to IDEA?
Thanks.
There is not. There is the Eclipse Code Formatter third party plug-in for portng over code formatting definitions. Pehaps you can contact that developer and see if he would add problems/inspections definition syncing. Until then, I see two options for you...
Configure your IDEA inspections so they match the team's Eclipse settings. This of course would require some time to initially set up. But I think in the end, it's the best solution.
IDEA can export to files in eclipse format. As part of that it can keep its configuration linked to the eclipse files. This way you could pop over to eclipse to check for problems prior to committing.
I'm running IntelliJ IDEA 12.1.3 on Windows 8 with the Scala plugin 0.7.264. Scala is installed in C:\Apps\Scala\scala-2.10.1, and that directory is in my PATH. The Scala docs are in C:\Apps\Scala\scala-2.10.1\doc\scala-devel-docs\api. These are manual installs from the .zip files.
Everything seems to work fine except for two things:
First, if the "Run compile server (in external build mode)" settings is enabled (as it is by default), I get this error:
Turning off that setting fixes that for now, but there is another problem. I can run my code in the debugger and see values change in the debugger panel as I single step through the code, but it doesn't synchronize the source file view as I step through.
Normally I'd expect to see the current line being executed turn green, and the green highlight would follow along as I hit F10 or F11 to step through, but it doesn't. I can set breakpoints on source lines and let it run, and it stops at each breakpoint as expected. It just doesn't highlight the source line in green when it gets there.
Similarly, if a source file is not open (either my source code or a library file), and I step into that code, it appears to single-step correctly but does not open the source file at all.
Everything else works fine, like the autocompletes and Shift+F1 to view the Scala docs for the name the cursor is on.
The really odd thing is I had full debugging working briefly. At first I'd installed Scala from the .msi file, so it installed Scala into C:\Program Files (x86)\scala. When I set up IntelliJ to use that Scala installation I did get the green highlight on source lines as I stepped through the code.
The only problem with that setup was that IntelliJ complained about the missing doc\scala-devel-docs\api directory when I'd setup a Scala project, because the .msi installation uses a different subdirectory for the API docs. It was easy enough to fix that up manually in the Global Liraries settings, but I figured I'd try the .zip installation so I could use a directory layout more like what IntelliJ was expecting.
I should have left well enough alone! I even tried going back to that arrangement and still didn't get source line synchronization working again.
At one point I also tried letting IntelliJ do the Scala installation, but that also gave the same results: everything working except source line synchronization in the debugger.
There must be some obvious thing I got wrong, but I'm not sure what it could be. Does anyone have any ideas?
Here's a screenshot from a debug session:
The program is stopped on line 3, as indicated by the values assigned to x and y but not yet to z, and the <init>():3, Main$$anon$1 in the Frames panel. So line 3 should be highlighted in green but isn't.
Here are the relevant settings dialogs:
The above is with "Run compile server" on; as mentioned I ended up turning that setting off. The field values are the defaults, including the -server -Xss1m -XX:MaxPermSize=256m JVM parameters.
I am using the same version of IDEA and the Scala plugin (however on OS X and JDK 6), and I do not have this problem. Does this occur with any of your projects or only a specific one?
Assuming that the OS shouldn't be responsible, the difference is that I use sbt to build my projects. So if you are willing to set up a build.sbt and installing the SBT plugin for IDEA, this might be worth a try.
Although the fancy new compile server should in theory be as fast and smooth as sbt, I find it very pleasant to work with the sbt plugin. You can install it from Settings -> IDE Settings -> Plugins. Next step I also highly recommend is to use the sbt-idea plugin, which is like the complementary to the IDEA SBT plugin—this will allow you to generate the full IDEA project files from sbt (you can have as little as a single scalaVersion entry in build.sbt if you don't need to manage dependencies, so you don't need to learn much of sbt in the first place).
The final step then is to go into your Run/Debug configuration, and change in the "Before launch" section from "Make" to "SBT".
Finally you might get better support for your problem through the JetBrains online forum.