In this case we have an invalid project with EE8 specified in the build file (pom.xml or build.gradle) and with a generated-features.xml file in src/main/liberty/config/configDropins/overrides dir where the features specified are for EE7. E.g. demo-devmode.
When we start dev mode with clean task/mojo and no options, generate-features is on by default and generateToSrc is off by default. Dev mode compiles the source files for EE8 and generates the features for EE8 in the server dir as normal. Then deploy runs and copies all the config files from the src dir including the invalid generated-features.xml file.
When generate features runs it ignores the existing generated-features.xml file by design so it is not considered by the binary scanner's error detection algorithm.
Possibly related to #1976.
In this case we have an invalid project with EE8 specified in the build file (pom.xml or build.gradle) and with a
generated-features.xmlfile insrc/main/liberty/config/configDropins/overridesdir where the features specified are for EE7. E.g. demo-devmode.When we start dev mode with
cleantask/mojo and no options, generate-features is on by default and generateToSrc is off by default. Dev mode compiles the source files for EE8 and generates the features for EE8 in the server dir as normal. Thendeployruns and copies all the config files from thesrcdir including the invalidgenerated-features.xmlfile.When generate features runs it ignores the existing
generated-features.xmlfile by design so it is not considered by the binary scanner's error detection algorithm.Possibly related to #1976.