wglanzer / quarkus-intellij-plugin Goto Github PK

At first, thank you for your nice plugin, should be standard in IntelliJ!
The issue I have is the integration into the IntelliJ Service Tool Window.

Did I have to configure something to attach the run output to the servic tool window?

I'm using a multi project structure using maven. There is one main project and a few other projects as libraries. The main project is including the libraries as dependencies using the SNAPSHOT version in the pom.xml.
If I modify the libraries the changes are not picked up from the sources but instead from the local repository so for every single change to the libraries I need to recompile the code. How to handle that? This was working with no problem with the same setup using Spring boot.
I'm using the community version of intellij idea.

Hi there,
this seems exactly what I was looking for. A great Plugin! Is there already a way to make it work with Gradle projects or any plans to support Gradle ?

Hi,
I would say that current plugin name is slightly misleading:

May be change it to something related to debugger or run configuration? Let's say Quarkus Run Configuration or Quarkus Debug?

Also, two plugins with the same icon look suspicious. I'd recommend to change icon or add some detail that is associated with debug/run.

If compile before launch flag for Gradle run configuration is enabled the plugin runs clean and then build. In Gradle build triggers test so this could be a very long operation. It would be better to use assemble instead.

Typical build flow:

:compileJava 
:processResources 
:classes 
:jar 
:assemble 
:compileTestJava 
:processTestResources 
:testClasses 
:test 
:check 
:build 

Typical assemble flow:

:compileJava 
:processResources 
:classes 
:jar 
:assemble 

I believe test is not essential for Running the application.

Does not work on IC-2021.1 with "Complie before launch" flag

17:34:51: Executing tasks 'clean assemble quarkusDev -Ddebug=39327 '...

> Task :clean

> Task :quarkusGenerateCode
preparing quarkus application

> Task :compileKotlin
> Task :compileJava NO-SOURCE
> Task :processResources
> Task :classes
> Task :inspectClassesForKotlinIC
> Task :jar

> Task :quarkusBuild FAILED
building quarkus jar
7 actionable tasks: 7 executed

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':quarkusBuild'.
> java.lang.IllegalStateException: SRCFG00035: Failed to load resource

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 4s
17:34:56: Tasks execution finished 'clean assemble quarkusDev -Ddebug=39327 '.

After changing the property "Tasks" in the configuration dialog, the value will not survive IntelliJ restart.

Plugin version: 1.3.0
IntelliJ version: IntelliJ IDEA 2023.2 (Ultimate Edition)

Hi there!

Seems to be a great plugin. Intellij has not approved it yet. Is there a way to use it already?

Thanks
Gregor

I use Java 22 and "--enable-preview" is ignored with [io.quarkus.deployment.QuarkusAugmentor]

Issue Description:

The current version of the IntelliJ plugin for Quarkus development automatically executes the "quarkus:dev" profile in Run/Debug configurations. While this is suitable for many scenarios, it limits users from utilizing other Quarkus profiles they might have defined for specific use cases, such as "quarkus:test" or custom profiles. To enhance the plugin's functionality and provide developers with more flexibility, I suggest adding support for using custom Quarkus profiles in Run/Debug configurations.

Suggested Feature:

Support the use of custom Quarkus profiles in the Run/Debug Configurations window within the IntelliJ plugin for Quarkus. Allow users to specify the desired Quarkus profile for running their Quarkus applications in different modes, such as "quarkus:test," and any custom profiles they have defined in their Quarkus project configuration.

Benefits:

• Increased Flexibility: Developers can choose from a range of Quarkus profiles to match specific development, testing, or production requirements.
• Custom Profile Support: Users can leverage any custom profiles they have defined, providing more control and adaptability in their Quarkus projects.
• Streamlined Development: By supporting custom profiles, developers can seamlessly switch between different configurations directly within the Run/Debug Configuration, reducing manual adjustments and saving time.

This enhancement will empower developers to work more efficiently with Quarkus by enabling the use of custom profiles tailored to their projects' distinct needs. Thank you for considering this suggestion, and I'm looking forward to seeing this feature in future updates of the plugin.