Today I've install IntelliJ Ultimate version 2016.1.1 build 145.597. What I did later, was import of may project from IntelliJ Community Edition. This project is based on spring-boot 1.3.3. The problem is that when I want to run my application in IntelliJ Ultimate somehow application.properties file is ignored and it starts with default spring settings. When I'm running the same project in IntelliJ Community Edition or from command line everything works fine. Problem exists only in Ultimate edition when I'm adding and running spring boot run configuration, if I use gradle configuration and bootRun task it works.
I didn't use before IntelliJ Ultimate.
Does anyone know what could be wrong? I wasted 2 hours googling for solution of my problem but I didn't find anything.
Content of src/main/resources/application.properties:
server.port=2081
server.ssl.key-store=cfg/certs/keystore.p12
server.ssl.key-store-password=dev
server.ssl.key-alias=alias
server.ssl.key-store-type=PKCS12
spring.datasource.url=jdbc:h2:file:./cfg/db/app;DB_CLOSE_ON_EXIT=FALSE
spring.datasource.driverClassName=org.h2.Driver
spring.datasource.username=sa
spring.datasource.password=
spring.jpa.database-platform=org.hibernate.dialect.H2Dialect
spring.jpa.hibernate.ddl-auto=none
Project structure:
I had same issue for IntelliJ Ultimate 2016.1.1
Reimporting the project and deleting existing project worked for me.
I believe the issue is pertinent with 1.1 version. Didn't had issue with IntelliJ IDEA 2016.1.4
check if file application.properties is directly under target/classess after compiled, maybe the wrong settings copy it to other directory that spring boot cannot know
one simple thing to fix the problem.
If you already open the IntelliJ idea, close the project and remove it from IntelliJ
idea.
navigate to your project directory (ex: F:\dev\my-project) and remove the .idea
folder from it.
then open the IntelliJ idea again. open your project from File -> Open.
then run the project.
this is the simplest solution.
thanks!
I had a similar problem with my spring boot application running from IntelliJ Ultimate Version 2020.3 . I had a Connection.properties configured in spring-config.xml file as below and got the FileNotFoundException for my Connection.properties file even after placing the file under src/main/resources folder in my gradle project
<context:property-placeholder location="file:Connection.properties" />
It worked after changing it to
<context:property-placeholder location="classpath:Connection.properties" />
Note the "file:" to "classpath:" in "location" attribute
Related
The similar issue was report in this post without any solution.
--
My IntelliJ Version is IntelliJ IDEA 2022.1.2 (Community Edition)
For over an year, I have been working on a maven project which uses a customized ibm-jdk8 and a customized maven installation.
So I've configured global maven runner & import settings & project & module SDK settings to use this custom JDK.
All this setup had been working fine for over an year.
Yesterday, I updated IDEA to newer version, I'm not sure what was the reason but I started getting wired IDE errors.
So I invalidated the cache and restarted the IDE,
When that did not solve the issues, I manually deleted following folders
All ~/AppData/*/JetBrains folders .
.idea folder inside project root.
project-name.iml file inside project root.
After that I updated all intelliJ setting same as above, but
Since then I've been getting Cannot resolve symbol 'String'
Strangely all other JDK classes are detected, but in whole code String is not working.
It's a known issue specific to IBM JDK.
The workaround is to manually add vm.jar file from JDK_HOME\jre\bin\default\jclSC180\vm.jar to the SDK classpath tab in IntelliJ IDEA.
I created a new project from VCS (Kotlin and Gradle). I added three testImplementation() calls to the build.gradle.kts. IntelliJ didn't pickup the changes so I did File -> Invalidate caches / Restart and now Intellij shows every implementation() call and every testImplementation() call in red. In fact every line in every build.gradle.kts in every module is red.
Intellij has lost its mind. What do I have to do to restore IntelliJ's intelligence when it comes to kotlintest in Gradle?
I started seeing this with AS 4.2.1. Invalidating caches and re-importing the project didn't work for me. I found this article on the JetBrains issue tracker where people found that they had an extraneous JDK set in the project settings. While I did not have an extraneous JDK set in my project structure, I tried changing the JDK from the AS embedded version to an alternate AdoptOpenJDK 1.8 version I had installed. After switching to that version all the red went away and everything is resolving as expected. I was then able to switch the SDK back to the embedded version and everything continued working as expected. When switching back to the embedded version I did notice a brief message in the progress bar at the bottom of AS saying that it was processing a JDK 11. I'm not sure where that's coming from, but it does seem to be in line with what others in the JetBrains issue were talking about.
The way I was finally able to solve this was with File -> Invalidate caches / Restart. It must have been cache corruption.
What do I have to do to restore IntelliJ's intelligence when it comes to kotlintest in Gradle?
Re-import the project: File | New | Project from Existing Sources action and select build Gradle file to load the project from.
Change your jdk.
Go to File>Project Structure > SDK Location > GradleSettings
Change the Gradle JDK to use the embedded or a compatible JDK (Azul JDK) if you're using a MAC.
Then Invalidate and refresh cache after deleting the .idea and .gradle files.
I wanted to debug my project under Open JDK 11, so I tried to switch boot jdk to the OpenJDK11 path. I am using the community version on Windows 10.
The suggested restart didn't happen, I only got the following error:
JDK needed
How can I reset the boot jdk without Intellij starting?
Thanks in advance and kind regards
The IntelliJ Advanced Configuration docs say the configuration directory on windows is:
Syntax
%HOMEPATH%\.<product><version>\config
Example
C:\Users\JohnS\.IntelliJIdea2019.3\config
Then, just delete the studio.jdk file in that directory, and IntelliJ will boot with its default.
I have a related answer about Android Studio
For MacOS(checked on Catalina) just run the "repair" binary located in:
/Applications/IntelliJ IDEA CE.app/Contents/bin
you can just delete this config file /Users/xxx/Library/Application Support/JetBrains/IntelliJIdea2022.1/idea.jdk
I have updated my IntelliJ IDEA Ultimate to the 2016.2 version.
I had a Grails 3 project and now when I open the IDE I get the following error when trying to run my project:
Error running Grails: My_Project: Grails application is not found
I can still open the terminal and run the project manually, but it seems that IntelliJ IDEA no longer recognises my Grails application. When going to "Edit configurations...", in "Application" it says "[none]" and I can't select anything.
Grails Version: 3.1.9
Groovy Version: 2.4.7
JVM Version: 1.8.0_66
A Simple solution to this is to refresh the gradle projects.
You can do this by popping out the little gradle tab and hitting the "Refresh All Gradle Projects"
I run into the same problem always when i restart intellij. Running grails clean command from the terminal fixed it.
First, re-import the project into IntelliJ 2016.2. Choose the build.gradle file for the import. Use the gradle wrapper or a local gradle installation, where you have given IntelliJ the path to the locally installed Gradle. Let IntelliJ re-index everything. Wait until you see no further indexing on the bottom of the screen.
Second, run the application once, with no edit configuration. After this completes with error, you should be able to choose Run -> Edit Configuration / Application.
Third, you can go into the project pane to the grails-app/init/app-name/Application.groovy file and right-click on that and choose Run. After that, an edit configuration will be created.
Finally, you can try to invalidate cache and restart. (This has nothing to do with Edit Configuration, but sometimes the gradle and/or .idea caches get out of sync.)
I had the same problem after updating to IntelliJ Ultimate 2019.2.
It seems that the "little gradle tab" of the accepted answer no longer exists.
The reason in my case was that the Gradle Plugin had been disabled by the update process.
Resolution: Hit Help > Find Action > Type gradle. You should see a line "Gradle" and a ON-OFF switch at the end of that line.
Enable it and restart IntelliJ solved my problem.
I'm using IntelliJ IDEA to build a non-java project, it is just a PHP + Javascript project, everything is working just fine but when I try to Inspect all the code in the project (Analyze -> Inspect Code) I get an error:
The JDK is not configured properly for this project. Inspection cannot proceed.
Am I doing something wrong? Do I have to configure an SDK even though the project is not java?
Note: The automatic code inspection for working files opened in the editor is working fine, the only problem is when I try to inspec all the code in the project.
Note 2: I cannot use PHPStorm neither Webstorm.
Thanks.
In my case, I didn't wanted to delete the module since I have a bunch of stuff configured (data sources, dictionaries, http requests) and a lot of code in the shelf (which I believe it's stored along the project/module). I found that you can skip the "delete your module" part and instead just update the module config:
Find the $module.iml file (in my case it's inside the .idea directory) and at the top there's was a line:
<module type="JAVA_MODULE" version="4">
which I changed to:
<module type="WEB_MODULE" version="4">
The issue was fixed and I haven't seen any side-effects but, just in case, you might want to backup the .idea directory.
I raised this over at https://youtrack.jetbrains.com/issue/IDEA-188017 - after some back and forth, the Jetbrains employee helped me figure out that I had a Java module in there.
If you are not using Java, please crate a module of a Static Web type. Now you have a module of a Java type, that is why the error is reported, so such behaviour is expected.
Delete your Java module.
Once you enter in the menu in the screenshot below, find the Static Web type and create your module like that.
Seems like adding a SDK the code analyzer works just fine, even though the project has no single java module.
Maybe it is a bug, so I will report it.
My project's .idea/<project>.iml file had an entry:
<orderEntry type="inheritedJdk" />
I quit Idea, removed the line above from the iml file, restarted Idea and the next Inspection ran without any issues.
I recently ran into this issue with my purely Python project.
After much frustation, I bumped into a rather bizarre solution:
When IntelliJ complained that JDK is not configured, in the following dialog box, I just selected JDK8 (instead of Python 3.7.2 path) and viola! its gone.
My environment was
IntelliJ IDEA 2018.3.4 (Community Edition)
Build #IC-183.5429.30, built on January 29, 2019
JRE: 1.8.0_152-release-1343-b26 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.14.2