You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when generating a 3.10 project via code.quarkus.io
the pom.xml still has; <quarkus.package.type>native</quarkus.package.type>
instead of <quarkus.native.enabled>true<quarkus.native.enabled>
and the readme.md still has ./mvnw package -Dquarkus.package.type=uber-jar
instead of ./mvnw package -Dquarkus.package.jar.type=uber-jar
I looked at the main branch and the 3.10 branch and it looks fine in terms of the above so unsure why this happens.
Expected behavior
new properties are used
Actual behavior
legacy properties are used
How to Reproduce?
1- go to https://code.quarkus.io/
2- click generate and download the app
3- observe the pom.xml and README.md
Output of uname -a or ver
No response
Output of java -version
No response
Quarkus version or git rev
No response
Build tool (ie. output of mvnw --version or gradlew --version)
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
when generating a 3.10 project via code.quarkus.io
the pom.xml still has;
<quarkus.package.type>native</quarkus.package.type>
instead of
<quarkus.native.enabled>true<quarkus.native.enabled>
and the readme.md still has
./mvnw package -Dquarkus.package.type=uber-jar
instead of
./mvnw package -Dquarkus.package.jar.type=uber-jar
I looked at the main branch and the 3.10 branch and it looks fine in terms of the above so unsure why this happens.
Expected behavior
new properties are used
Actual behavior
legacy properties are used
How to Reproduce?
1- go to https://code.quarkus.io/
2- click generate and download the app
3- observe the pom.xml and README.md
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: