Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repo level IntelliJ Platform settings via .ijwb/.idea #6787

Open
bric3 opened this issue Sep 24, 2024 · 7 comments
Open

Repo level IntelliJ Platform settings via .ijwb/.idea #6787

bric3 opened this issue Sep 24, 2024 · 7 comments
Assignees
Labels
awaiting-maintainer Awaiting review from Bazel team on issues P3 We're not considering working on this, but happy to review a PR. (No assignee) type: feature request

Comments

@bric3
Copy link

bric3 commented Sep 24, 2024

Description of the feature request:

Cannot commit .idea settings files within .ijwb/.idea, because the .ijwb "already exists".

Which category does this issue belong to?

No response

What underlying problem are you trying to solve with this feature?

The IDEA project folder is generated in .ijwb/.idea of the repository root. In regular non-bazel project, it is possible to commit some files of the .idea folder to help configure IDEA.
E.g.

  • Silly things like the .idea/icon.svg
  • Run configurations .idea/runConfigurations/*.xml
  • (Search) Scopes .idea/scopes/
  • External dependencies (like plugins) .idea/externalDependencies.xml

I was hoping that it possible to commit such files .ijwb/.idea/..., but it doesn't work because the .ijwb folder has to be re-created on each import. Otherwise we see the following error.

image

Related issues:

What operating system, Intellij IDE and programming languages are you using? Please provide specific versions.

  • macOs 15
  • GoLand & Intellij IDEA 2024.2.2
  • Bazel for Intellij 2024.08.27.0.1-api-version-242

Have you found anything relevant by searching the web?

Nope

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

No response

@bric3 bric3 added awaiting-maintainer Awaiting review from Bazel team on issues type: feature request labels Sep 24, 2024
@tpasternak
Copy link
Collaborator

Duplicate of #3326

@tpasternak tpasternak marked this as a duplicate of #3326 Sep 24, 2024
@tpasternak
Copy link
Collaborator

Hey @bric3 . I don't have capacity to work on it, but could experiment with checking some files in .ijwb/.idea and then using "File -> open -> .jiwb directory" instead of "import bazel project"

@bric3
Copy link
Author

bric3 commented Sep 24, 2024

but could experiment with checking some files in .ijwb/.idea and then using "File -> open -> .jiwb directory" instead of "import bazel project"

Actually, this doesn't work well, in the sense that the monorepo I'm working on has multiple "views" consisting each of a .bazelproject, there's about 100 in this repo. That's why the devx team suggest to import the project.

That says thank you for the suggestion and the feedback!

@tpasternak
Copy link
Collaborator

So just in case you missed that - it is possible to setup run configurations xmls via the project files https://github.com/bazelbuild/intellij/blob/master/examples/java/greetings_project/run_configurations/fragment.bazelproject

Maybe we could think of extending that

@tpasternak
Copy link
Collaborator

Oh, and theoretically, you could

  1. keep an empty projectview in .ijwb
  2. open int
  3. put import right_project_view there

@tpasternak
Copy link
Collaborator

Oh, and you can also start using the new plugin https://github.com/JetBrains/hirschgarten

@bric3
Copy link
Author

bric3 commented Sep 24, 2024

Yeah I'd like to test the new JetBrains plugin, but it's not yet "validated" by our "devx" team. I don't know stable it is at this stage.

I'll test the fragments approach, thanks for that.

EDIT: I misread I thought fragments could support any xml file. It only support run configuration and indeed that would be useful to extend that mechanism.

@tpasternak tpasternak added the P3 We're not considering working on this, but happy to review a PR. (No assignee) label Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-maintainer Awaiting review from Bazel team on issues P3 We're not considering working on this, but happy to review a PR. (No assignee) type: feature request
Projects
None yet
Development

No branches or pull requests

5 participants