Details
-
Bug
-
Resolution: Done
-
Blocker
-
None
-
5
-
False
-
False
-
Undefined
-
+
-
https://gitlab.cee.redhat.com/red-hat-jboss-enterprise-application-platform-documentation/eap-microprofile/-/merge_requests/191, https://gitlab.cee.redhat.com/red-hat-jboss-enterprise-application-platform-documentation/eap-microprofile/-/merge_requests/198#0ef0b6cd65c82107d007f3e2b71ea881f164933e, https://gitlab.cee.redhat.com/red-hat-jboss-enterprise-application-platform-documentation/eap-microprofile/-/merge_requests/210
-
Jan 18 - Jan 29, EAP DOC Sprint 3: Feb 1-Feb 12, EAP DOC Sprint 5:March 1- 12
Description
Use mvn properties for artifacts versions in bootable jar documentations.
So far documentation provide part of pom.xml code with hard-coded versions (for wildfly-jar-maven-plugin and wildfly-galleon-pack) and ask users to update these versions manually (eg here). Better approach would be to use mvn properties for these artifacts versions.
