Jakub Chrzanowski

Starting with the IntelliJ Platform Gradle Plugin 2.0, all repositories used by the plugin have to be explicitly defined within the `repositories {}` block, which makes it clear what is...

Patching the since/until the build has been revisited with the IntelliJ Platform Gradle Plugin 2.0, and the reported issue became obsolete. The presence of `` tag is necessary, however it...

To use Amper, rely on a dedicated fork project linked in README: > [!NOTE] > > There is a fork of this repository available that utilizes the Amper tool for...

Note, for Amper, there's a requirement of using the latest Fleet/IntelliJ IDEA: > [!WARNING] > > Amper is supported since IntelliJ IDEA `2023.3` and Fleet `1.26` releases. No extra configuration...

This template provides a minimal setup for running Advent of Code solutions via IDE. Using @MaaxGr suggestion, we can go further and parametrize the `mainClass` with: ``` plugins { kotlin("jvm")...

Basically, the square brackets are added to the header (they surround the version part) only when there's a `repositoryUrl` provided, so section URLs are generated.

As a workaround, please add to the Gradle build file: ``` tasks { withType { classpath(setupDependencies.flatMap { it.idea.map { idea -> idea.classes.resolve("lib/opentelemetry.jar") } }) } } ```

The suggested solution is not possible to implement ATM. The hotfix with hardcoded `opentelemetry` entry was just published as `2022.3.2.2`.

That's a valid question, Danil — thanks for asking. I plan to send a PR to `actions/setup-java` to make them aware of JBR, but this has a low-priority ATM. Also,...

Note: the IntelliJ Platform Gradle Plugin 2.x changed the approach and is using now IDE Installers as a target IntelliJ Platform in the first place, which have JBR bundled.