Open hohwille opened 7 months ago
If IDEA_PROPERTIES
is not set or no additional argument (workspace path) is given to idea the error does not occur.
I've tested this behavior with intellij
community edition 2023.2.4
and 2023.2.5
.
I've used the plugins you've encountered issues with e.g. sonarlint, mapstruct, eclipseCodeFormatter, FolderCompact
etc.
Testing method was the following:
workspaces/main
intellij
version to previous version in conf/devon.properties
plugins/intellij
intellij
using devon intellij
I was not able to reproduce this issue using the community edition, so it seems that this only occurs with the ultimate edition.
As we've found out that the issue only occurs for a pre-installed sonarlint
plugin in the ultimate edition, it seems like this issue is way too special to address for now.
We need to wait for other users to report similar issues
Seems to only happen in ultimate edition with specific plugin combination so not a major blocker. Therefore lowered priority.
Expected behavior
As a devonfw-ide user, I want to be able to use the latest version of IntelliJ so that I can efficiently do Java coding.
Actual behavior
I just got an update to the latest IntelliJ version
As soon as I hit OK IntelliJ immediately closes down.
2023.2.5
. When I open it with devon intellij I get this popup:IMHO this is due to our workaround we build for the workspace management (see issue #1305) so we are fighting against windmills again and might have to find a totally new approach to tame IntelliJ. However, maybe this is just a stupid bug in the product and we need to report it to JetBrains to get it fixed...
When I directly run
software/intellij/bin/idea64.exe
and select the project workspace manually, all is working fine.Steps to reproduce (bug) / Use Case of feature request (enhancement)
Related/Dependent Issues
1305
1358
Comments/Hints:
Why must simple things always be so hard ;) We also always see that "latest is greatest" would in theory be a nice approach but the only way to get a reliable and stable IDE setup is by explicitly configuring product version up to the last digit. Due to security reasons we always wanted not to do that so developers get latest updates and security fixes. But as product vendors like Eclipse, JetBrains, etc. are pushing out new releases that break everything projects are forced to maintain the versions.
Affected version: