How to view console output in intellij 2021.2.3 community edition?
I am hitting debug button but the console just shows me the status of gradle tasks.
There is a similar question here (How to show missing Console output in latest IntelliJ update) but the button mentioned does not seem to exist any more in the latest version.
see screenshot
Related
I've installed IntelliJ IDEA Community Edition version 2018.3.6.
When I launch the shortcut it doesn't start and just do anything that is shown in refreshing (green circle). I've tired and I can't do anything.
I wanted to install Android Studio but my computer doesn't support it. Now, IntelliJ doesn't run too. Please help.
I am using IntelliJ trial version.
We used to relay on Debug console in Eclipse
.
But the same feature is not seem to be present with the IntelliJ 2018.1
Can anybody please suggest what needs to be done
You can use "Evaluate Expression" to run code fragments in a Debug session. Use Alt+F8 on Windows/*nix or ⌥+F8 on a macOs.
The window looks like the below image.
Any Log or SysOuts will be printed on the Console in the Debug window.
Ref: Evaluate arbitrary expressions
I followed instruction from following link to create a Play project in IntelliJ but IntelliJ doesn't show correct structure.
https://www.jetbrains.com/help/idea/getting-started-with-play-2-x.html
Snapshot attached
I ran into the same issue and found this: Building a Play 2.6 project from IntelliJ builds nothing
So now we're 3 people with the same problem. I haven't found any open bug report or issue anywhere.
I got it working using the workaround that OP from the other question suggested: "Build the project from SBT in your desired location first, and then import the project from IntelliJ as an SBT project and you should be good to go."
To do that just run sbt new playframework/play-scala-seed.g8 (assuming you have SBT installed and PATH configured), and import that.
I raised the issue with IntelliJ support. It seems to be fixed in the latest release of IntelliJ ultimate edition. If you run the default application and see 'no jdk error', go to edit configurations and select the top level project in play module (see pic)
I recently updated the Intellij-idea from 13.1 to 13.1.7.
When I try to open recently closed projects by right-click the Intellij icon in taskbar - getting this error in Event log
Unauthorized Operation: The command line launcher is outdated. Please refresh it (via Tools | Create Command-line Launcher)
It used to work fine with 13.1.
I have a libGDX project generated by the gdx-setup.jar tool, including core, android, desktop, and html modules. I hadn't touched any of the gradle files, and my build has worked fine for some weeks.
This morning when I opened IntelliJ IDEA (build 135.1230), it offered to update the Scala plugin, so I accepted and restarted, before trying to open the project. My libGDX project doesn't use Scala at all: I have the plugin for other work. When I tried to open the project, I got the infamous "Gradle project sync failed. Basic functionality (e.g. editing, debugging) will not work properly" message. Clicking "Try again" thinks for a bit before showing the same message. The Event Log window contains no output, and the Messages window says:
Error: (of class java.lang.String)
The Scala plugin isn't the only thing that might have changed: I've rebooted the (Ubuntu) machine since the project last worked, so it's possible that some package updates might have only just had an effect.
Following the advice of others, I've tried editing the root gradle.properties to change org.gradle.configureondemand to false, and that made no difference. I've tried performing "Build → Clean Project" and "Invalidate and Restart", with the same effect. I've also tried running git clean -X and reimporting the Gradle project into IDEA, but I just get a "Resolve error" dialog with the same message as above.
Running a build command like
./gradlew android:assemble
from a shell still works fine: only IntelliJ IDEA has a problem.
Even if you've never seen this particular problem, I'd appreciate any tips on where to start debugging it. The error message doesn't exactly give me a lot to go on.