quarkus: Quarkus 1.6.0.Final does not resolve profile-scoped variables correctly in the configuration

the following configuration does not work on Quarkus 1.6.0.Final:

#----------------------------------------
my.application.http.port=8081
%dev.my.application.http.port=8082
%test.my.application.http.port=8083

quarkus.http.port=${my.application.http.port}
#----------------------------------------

when I use mvn quarkus:dev the service picks the wrong port: 8081 ( it ignores the %dev profile and resolves the wrong version of ‘my.application.http.port’ ), while it works perfectly with Quarkus 1.5.2.Final

This configuration, on the other hand, works fine with both versions

#----------------------------------------
quarkus.http.port=8081
%dev.quarkus.http.port=8082
%test.quarkus.http.port=8083
#----------------------------------------

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 15 (14 by maintainers)

Commits related to this issue

Most upvoted comments

Checking.