In IntellIJ not long ago I was able to make changes to my html/thymeleaf files and hit 'Build Project' and Spring Boot didn't have to restart the entire app. It would showcase the changes in my web browser (Firefox, Chrome). I have researched and tried a variety of changes and can't seem to find the issue/error to get me back to faster, efficient frontend productivity.
It's only a setting inside of IntelliJ Idea. You can see here what you need to set, and to have in a build.gradle or pom file.
So my understanding from the documentation to perform a publish is I need to call 'electronize build /target win'. This builds the project. However, there are some issues I'm unsure how to address.
The content path when I try to run it says the content root is C:\Windows\system32 instead of the actual working directory where the .exe resides. That isn't correct. Any ideas why? I think some of the other issues are caused by this.
Edit: I found out #1 uses the correct directory if it is ran as administrator. Unsure why.
How does one hide the command menu that comes up? all i want is the electron window to show on publish.
I see an electron window come up like when i run 'electronize start' but not after publishing. Any ideas?
Please try the latest version of Electron.NET. During development, a development menu is displayed. A standard behavior of Electron if you not have your own menu. With a build, the development menu is hidden again.
I am currently working with IntelliJ IDEA and I try to debug gwt components directly in the IDE.
I know I can use Chrome DevTools to debug, but it's always a pain, when the variables names change and it takes quite a long time to debug.
I thing I have seen somewhere the fact that you can directly debug your component in IntelliJ but I am not sure where I have seen that.
I am in superdevmode but when I add a breakpoint in my java class in IntelliJ it does not get validated and does not stop in IntelliJ. It only works in Chrome.
Here is my gwt configuration
Thanks a lot.
Thoma
It sure does work from within IntelliJ.
One thing I noted in your screenshot : Set a checkbox with "with JavaScript debugger".
That is the only thing I see different with my setup, in which breakpoints work in IntelliJ, and in the browser.
I am trying out GoLand and hear that the debugger is supposedly awesome, but I can’t find any documentation explaining how to set it up (GoLand is in preview stage, so that’s not really surprising). My use case: I am writing a REST API to which I send requests using curl. Could someone please tell me, step by step, how to get started with the debugger ?
[edit 1] (moved from comment) When I click Run/Debug (or Run/Run), a window is displayed, asking me to edit configurations. I am given a choice of several kinds of configurations, I try to choose "Go application" but the Debug button never is grayed and I can't get it to become clickable. I am very new to GoLand, I may be missing something obvious, but I can’t find whatever settings are missing.
[edit 2] It turns out that my workspace did not conform to the Go specifications : my code was not in a directory named src. Now that it is the case, I can click Run/Debug and GoLand seems to be doing the right thing, except it doesn’t stop at breakpoints or otherwise behave like a debugger, my code just runs.
[edit 3] Tried again, and it works. Sort of. I have no idea why it works now, even though it didn’t previously and I didn’t change anything. Now breakpoints work at some lines, and not at others. Or the debugger stops at the breakpoint, but I wait forever for the list of variables to be loaded. Well, it is a preview, after all...
[edit 4] I was notified just today that a new version of GoLand was available. I upgraded, and debugging is working well for me now.
GoLand will not enable the debug action (although run is available) if your code does not reside inside src. There is no warning about this, so it might be really a pain to solve this.
Additionally, depending on your project’s structure it might be possible, that debugging is still not working. In that case, it might help to remove all run configurations and create a new one. There’s is a bug report about this behavior.
PS: Although the OP mentions the first part in an edit of the question, but it think it’s worth mentioning in an answer.
Things changed in goland since #Jamillo Santos added his reply.
To start with, there's no more "Go Application".
The easiest way is to locate the file containing the main() function.
There should be a small triangle pointing to it, like in the attached screenshot:
When you click on the small green triangle, you get a menu with Run/Debug options.
Each will create a go build configuration.
You can edit that go build configuration and add the program arguments for your application.
For example, if your program have a command line argument of --arg=value you can add it like this:
I was facing this same issue and I solved by using the "Go Application" configuration (at the Run/Debug Configurations window), instead of the "Go Single File" configuration.
So, go to the upper right corner of the Gogland and "Edit configurations".
Then, add a new configuration using the "Go Application" profile.
After saving, you should be able to debug your code. o/
An easy way to enable this configuration is to use the #user1793301 method and right click on the file you want to run and select "Debug 'go run .go'".
POSSIBLE EXPLANATION
NOTICE: I did not look any further details about it.
Fact: "Go Application" configuration does build the binary executable before running it.
Fact: I could see looking at the console output (inside of the Goglang) is that the IDE uses the DLV as debugging tool.
Fact: I found a dlv debug at the DLV documentation and it seems to compile and debug the code.
Hypothesis: The guys from Jetbrains did not implement it. Or at least not YET.
On version 2019.1.1 there's no more Go Application. Use Go Build instead. Here I am debugging a single script file, but if you have a server app or smth, just point to the main app file:
Notice that in the Files field you have to specify the actual file path. You can put more files (if you want to have more starting points) by separating them with a pipe |. For each file you want to be able to debug, you need to specify the full path.
Again, if you are debugging a server app or something else, that has a single starting point, you only need the startup file specified in the config. :)
I had this exact problem.
Deleted and recreated the Debug run configuration. Debugging then worked perfectly.
I followed the following procedure to start my golang server in debug mode. (You might want to use some other method than creating a makefile for starting your server maybe)
Create a makefile
Define your server/worker startup command in the file
Run it by creating a new configuration for Makefile
Go to Run -> Attach to process -> choose your running server
This will attach the debugger to your process.
Note:
You might need to restart your server for this to work.
The IDE will ask you to install gops, do install it. Without installing gops you won't see any running process.
I right click on project (main.go inside) and choose "Debug ..." and it work
Env:
Mac OS
IDEA Community Edition 15
Hi,
I am currently facing two issues while remote debugging. Googled around but haven't been able to fix'em.
Despite the source code being available within the project, the
debugger always stops in the maven sources. Question : Is there a
setting/workaround that boils down to "Prefer project modules over maven sources while debugging" ?
Idea showed a popup showing the alternate sources initially. After selecting local module i disabled it. Now i can not re-enable it (for other local modules). The intended behaviour was that it automatically goes to local module source but that not working. Not irritating enough, Preferences -> Build -> Debugger -> "Show alternate source switcher" is not working. It always keeps disabled no matter what i do.
Any inputs are much appreciated.
Rakesh
Update
Solution for #2 is to do it the hard way. Open up
/Users/user-name-here/Library/Preferences/IdeaIC15/options/other.xml
and set 'SHOW_ALTERNATIVE_SOURCE' to true i.e.
<option name="SHOW_ALTERNATIVE_SOURCE" value="true" />
and restart IDEA
Even I had the same problem. I had external jars files attached in the Project_Structure -> Modules -> Dependencies. I did the following trick, it worked for me and it is not the remote debugging. I attached the source code of those jar files in Project_Structure -> Libraries and click the + in the second window pane (I am using Intellij Idea Ultimate 2018.2) then java option in the drop-down list. After selecting java option, a file browser window will open up, choose the source code directory you want to attach during the debugging.