Closed roy-ackermann closed 6 months ago
Hi Roy, thanks for reporting this issue. Maybe a firewall is blocking calls? I'm trying to reproduce the issue so I can start analyzing.
SOLVED -- see 2nd Edit (TLDR -- run mvn clean package)
Hello!
I really appreciate the work that you have put into this plugin! It has worked very well for our team's needs!
IntelliJ IDEA 2023.2.4 (Ultimate Edition)
If you don't mind, I would like to add my own experience with this 'bug'. While running version 1.8.1 of your plugin, I was able to read the dependencies of one of our projects, a multi-module Java program. I would run the checker against each pom, no issue.
After the 1.10.0 update, I am also receiving this error, on each pom.
Prior to updating the plugin, here is a snippet from one of the modules:
On another project, I will show you a 1.10.0 dialog
version 1.10.0 :
Prior to updating the plugin, on this same project, I got this that I copied to my clipboard:
com.azure.spring:spring-cloud-azure-starter-active-directory:5.7.0 > 5.9.1 com.github.eirslett:frontend-maven-plugin:1.13.1 > 1.15.0 com.ibm.db2:jcc:11.5.8.0 > 11.5.9.0 com.microsoft.sqlserver:mssql-jdbc:11.2.3.jre17 > 12.6.0.jre8 org.projectlombok:lombok:1.18.28 > 1.18.30 org.springframework.boot:spring-boot-configuration-processor:3.1.3 > 3.2.2 org.springframework.boot:spring-boot-devtools:3.1.3 > 3.2.2 org.springframework.boot:spring-boot-maven-plugin:3.1.3 > 3.2.2 org.springframework.boot:spring-boot-starter-jdbc:3.1.3 > 3.2.2 org.springframework.boot:spring-boot-starter-mail:3.0.4 > 3.2.2 org.springframework.boot:spring-boot-starter-oauth2-resource-server:3.1.3 > 3.2.2 org.springframework.boot:spring-boot-starter-security:3.1.3 > 3.2.2 org.springframework.boot:spring-boot-starter-test:3.1.3 > 3.2.2 org.springframework.boot:spring-boot-starter-tomcat:3.1.3 > 3.2.2 org.springframework.boot:spring-boot-starter-web:3.1.3 > 3.2.2
Please let me know if I can provide any more information to help clarify!
Thank you again for all your hard work!
Edit: I have upgraded my IntelliJ version to 2023.3.4 (Ultimate Edition) -- no changes in behavior. Though I should mention that before, while running the checker, the dialog result would appear much sooner. Now, the 'everything's up to date' dialog mentioned above takes a solid 50 seconds, where as before, it would be nearly instant / 2 - 3 seconds.
Edit, the Sequel: I was looking for some kind of internal logs to send for better data, and to kill time, I decided to run the Maven clean / package process. Just for kicks, I re-ran the plugin and it worked!
This behavior was 100% reproducible among all of our team's projects. The 'bug' would occur after running the plugin; I could clean / package, and the plugin would work as expected. It's really odd behavior to a non-expert like me, especially considering that the project re-indexes and scans packages upon starting up the IDE. But no complaints here. Please keep up the great work!
I have the same problem in one project, in the other it works like a charm. Unfortunately, I was unable to resolve the issue by running mvn clean and package again.
Hi guys, thanks a lot for sharing your issues with the plugin. I'm happy you could fix the problem, @Michaelafuller!
I'm not quite sure but the problem seems to occur in multi module Maven projects only. I created a multi module project for testing purpose but the issue didn't show up.
Are you using a Maven parent POM module in your projects which is referenced from other modules? Maybe that is causing the issue. I'll try that out.
@jack-geronimo, did you try to invalidate the caches in IntelliJ? The dependency index will be built from scratch so maybe this will solve the problem.
Sorry for the inconvenience!
Hi guys, thanks a lot for sharing your issues with the plugin. I'm happy you could fix the problem, @Michaelafuller!
I'm not quite sure but the problem seems to occur in multi module Maven projects only. I created a multi module project for testing purpose but the issue didn't show up.
Are you using a Maven parent POM module in your projects which is referenced from other modules? Maybe that is causing the issue. I'll try that out.
@jack-geronimo, did you try to invalidate the caches in IntelliJ? The dependency index will be built from scratch so maybe this will solve the problem.
Sorry for the inconvenience!
Hi @mwalter, I have recently invalidated the caches in IntelliJ, and now I also get the message "no project dependency information found" in the old project, which was still working before the invalidation. Both of these projects are multi-module Maven projects that refer to the parent POM.
Thanks for your effort
Hi all! Good news. I've found the issue and provided a patch. Please upgrade to the newest version of the plugin.
@jack-geronimo and @roy-ackermann: Let me know if you still encounter this issue or not. If everything's fine for you now, I'll close this issue. Waiting for your feedback.
Intelij version: 2023.3.3 Plugin version: 1.10.0
When i run the dependency check, the plugin cannot read the dependency information. The message is "no project dependency information found".
The plugin still worked a while ago.