EXECUTE: Create any CDI project (don't enable CDI support!)
EXECUTE: If there is no in .project yet then add it there:
<buildCommand> <name>org.eclipse.wst.validation.validationbuilder</name> <arguments> </arguments> </buildCommand>
EXECUTE: Enable CDI support for the project.
EXECUTE: Open .project
FAILURE:
<buildCommand> <name>org.jboss.tools.cdi.core.cdibuilder</name> <arguments> </arguments> </buildCommand>
is added to the end of <buildSpec> tag.
ASSERT: org.jboss.tools.cdi.core.cdibuilder should be declared after org.eclipse.jdt.core.javabuilder but before org.eclipse.wst.validation.validationbuilder
This is very important since if we have CDI builder declared after WST validator builder then CDI validation will be invoked before CDI builder completed building CDI model. It causes incorrect work of CDI validation.
- is related to
-
JBIDE-9055 Make sure all the JBoss Tools project examples have the correct order of CDI, Seam, KB, Validation builders.
-
- Closed
-
- relates to
-
JBIDE-8709 Removing class which there are still references too causes error logging/unrelated invalidation errors
-
- Closed
-
-
JBIDE-9028 Validator framework should create a problem marker w/ a quick fix if some required builder is registered in project after validator builder
-
- Closed
-
