-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
- clone QS repository
- navigate to any microprofile QS application
- mvn clean install -Pbootable-jar
- check the target folder
-
---
-
---
The build of bootable jar of any QS application produce the jar file with unexpected name server-bootable.jar.
Please use the <bootable-jar-name>${artifactId}-bootable.jar</bootable-jar-name> in the bootable-jar plugin configuration.
- is blocked by
-
WFMP-265 Consider changing the default value for bootableJarName to artifactId-bootable.jar
-
- Resolved
-