bazelbuild / bazelbuild/intellij

import_run_configurations aren't automatically imported in CLion

Open
#4,635 2 comments 0 reactions 0 assignees View on GitHub
awaiting-maintainer product: CLion type: bug
Dominant language
Java
Stars
820
Forks
342
Avg merge
2d 16h
Merged PRs (30d)
6

Description

### Description of the bug:

I have two `.bazelproject` projects, one for IntelliJ and one for CLion. Both of these projects specify various entries under `import_run_configurations` in the same way.

When importing these projects into IntelliJ and CLion respectively, IntelliJ will correctly show the list of Run Configurations under the top-right menu once the project sync completes. However, CLion does not: CLion shows an `Add configuration` placeholder in the menu. Clicking on it shows me the pre-configured configurations in the left panel. When I select one and click OK, then all of those configurations are added to the IDE.

As I see it, the CLion behavior is broken. The Run configurations should show up automatically after a sync.

### What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

1. Create a `foo.bazelproject` file for CLion with a single `import_run_configurations` pointing to an `xml` file.
2. Import the project into CLion.
3. Wait until project syncing completes.
4. Notice that the run configuration wasn't populated.

Now do the same with IntellliJ and see that it is.

### Which Intellij IDE are you using? Please provide the specific version.

CLion 2022.3.2

### What programming languages and tools are you using? Please provide specific versions.

_No response_

### What Bazel plugin version are you using?

2023.02.07.0.1-api-version-223

### Have you found anything relevant by searching the web?

_No response_

### Any other information, logs, or outputs that you want to share?

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by tracing how import_run_configurations from a .bazelproject file is handled during project sync, comparing the IntelliJ and CLion paths. Reproduce the issue with a minimal project and an XML configuration; done means CLion automatically shows the imported run configurations after syncing, without selecting them manually.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.