-
Sub-task
-
Resolution: Unresolved
-
Major
-
2.6.0.Final
-
None
Most setup commands have a version parameter to choose which version you want to use :
cdi-setup --cdiVersion
ejb-setup --ejbVersion
faces-setup --facesVersion
jms-setup --jmsVersion
jpa-setup --jpaVersion
rest-setup --jaxrsVersion
websocket-setup --webSocketVersion
At the moment, the only Java EE component that misses this parameter is Bean Validation. The constraint-setup command has the following parameters :
[test]$ constraint-setup TAB --providers --providedScope
A parameter beanValidationVersion parameter should be added. The values would be 1.0 or 1.1. That will have an impact on the XSD of the generated validation.xml file and the dependencies in the pom.xml
- is blocked by
-
FORGE-1421 Move back to ShrinkWrap Descriptors
- Open
- is related to
-
FORGE-1530 Command constraint-setup creates a Bean Validation 1.1 descriptor
- Open
-
FORGE-2149 validation.xml doesn't have the version="1.1" in the xml
- Closed