SVT: LMP 4.0.0-SNAPSHOT - Feature Gen generates conflcting features using ACME App

[rumanaHaque]

While testing the ACME application for the LMP Generate Features using this TER - https://github.ibm.com/websphere/system-test/issues/1806 - when I comment out the features in my server.xml, and start Liberty using Liberty Tools - using the flag -DgenerateFeatures=true, after I use a specific jar file that does not exclude com.ibm, I get these errors:

[INFO] Running liberty:generate-features
Downloading from sonatype-central-snapshots: https://central.sonatype.com/repository/maven-snapshots/com/ibm/websphere/appmod/tools/feature-gen/maven-metadata.xml
Downloaded from sonatype-central-snapshots: https://central.sonatype.com/repository/maven-snapshots/com/ibm/websphere/appmod/tools/feature-gen/maven-metadata.xml (337 B at 1.0 kB/s)
Downloading from sonatype-central-snapshots: https://central.sonatype.com/repository/maven-snapshots/com/ibm/websphere/appmod/tools/feature-gen/0.0.1-SNAPSHOT/maven-metadata.xml
Downloaded from sonatype-central-snapshots: https://central.sonatype.com/repository/maven-snapshots/com/ibm/websphere/appmod/tools/feature-gen/0.0.1-SNAPSHOT/maven-metadata.xml (791 B at 2.6 kB/s)
INFO: CWMIG11001I: The following packages are excluded from the scan by default: ch.qos,com.cloudant,com.cognos,com.fasterxml,com.filenet,com.ibatis,com.informix,com.lowagie,com.mchange,com.meterware,com.microsoft,com.mongodb,com.mysql,com.sun,com.sybase,filenet,freemarker,groovy,jakarta,java,javax,net,oracle,org,sqlj,sun,twitter4j,_ibmjsp. Use the --includePackages or --excludePackages options to override the default scanned packages.
SEVERE: CWMIG12083E: The appSecurity-5.0 feature requires the io.openliberty.servlet.api-6.0 feature which conflicts with the io.openliberty.servlet.api-3.0 feature that is required by the jaxrs-1.1 feature.
SEVERE: CWMIG12083E: The appSecurity-5.0 feature requires the io.openliberty.servlet.api-6.0 feature which conflicts with the io.openliberty.servlet.api-3.0 feature that is required by the jaxrs-1.1 feature.
SEVERE: CWMIG12083E: The servlet-5.0 feature requires the com.ibm.websphere.appserver.eeCompatible-9.0 feature which conflicts with the com.ibm.websphere.appserver.eeCompatible-10.0 feature that is required by the jsonb-3.0 feature.
SEVERE: CWMIG12083E: The servlet-6.0 feature requires the com.ibm.websphere.appserver.servlet-6.0 feature which conflicts with the com.ibm.websphere.appserver.servlet-5.0 feature that is required by the appSecurity-4.0 feature.
SEVERE: CWMIG12083E: The appSecurity-5.0 feature requires the io.openliberty.servlet.api-6.0 feature which conflicts with the io.openliberty.servlet.api-3.0 feature that is required by the jaxrs-1.1 feature.
SEVERE: CWMIG12083E: The mdb-4.0 feature requires the com.ibm.websphere.appserver.transaction-2.0 feature which conflicts with the com.ibm.websphere.appserver.transaction-1.1 feature that is required by the jpa-2.0 feature.
SEVERE: CWMIG12083E: The servlet-6.0 feature requires the com.ibm.websphere.appserver.servlet-6.0 feature which conflicts with the com.ibm.websphere.appserver.servlet-5.0 feature that is required by the appSecurity-4.0 feature.
SEVERE: CWMIG12083E: The appSecurity-5.0 feature requires the io.openliberty.servlet.api-6.0 feature which conflicts with the io.openliberty.servlet.api-3.0 feature that is required by the jaxrs-1.1 feature.
SEVERE: CWMIG12083E: The servlet-5.0 feature requires the io.openliberty.servlet.api-5.0 feature which conflicts with the io.openliberty.servlet.api-3.0 feature that is required by the jaxrs-1.1 feature.
SEVERE: CWMIG12083E: The servlet-5.0 feature requires the io.openliberty.servlet.api-5.0 feature which conflicts with the io.openliberty.servlet.api-3.0 feature that is required by the jaxrs-1.1 feature.
SEVERE: CWMIG12083E: The servlet-6.0 feature requires the com.ibm.websphere.appserver.servlet-6.0 feature which conflicts with the com.ibm.websphere.appserver.servlet-5.0 feature that is required by the appSecurity-4.0 feature.
SEVERE: CWMIG12083E: The servlet-5.0 feature requires the io.openliberty.servlet.api-5.0 feature which conflicts with the io.openliberty.servlet.api-3.0 feature that is required by the jaxrs-1.1 feature.
SEVERE: CWMIG12083E: The servlet-5.0 feature requires the io.openliberty.servlet.api-5.0 feature which conflicts with the io.openliberty.servlet.api-3.0 feature that is required by the jaxrs-1.1 feature.
SEVERE: CWMIG12083E: The servlet-6.0 feature requires the com.ibm.websphere.appserver.servlet-6.0 feature which conflicts with the com.ibm.websphere.appserver.servlet-5.0 feature that is required by the appSecurity-4.0 feature.
SEVERE: CWMIG12083E: The servlet-5.0 feature requires the io.openliberty.servlet.api-5.0 feature which conflicts with the io.openliberty.servlet.api-3.0 feature that is required by the jaxrs-1.1 feature.
SEVERE: CWMIG12083E: The servlet-5.0 feature requires the io.openliberty.servlet.api-5.0 feature which conflicts with the io.openliberty.servlet.api-3.0 feature that is required by the jaxrs-1.1 feature.
INFO: CWMIG12084I: The features required by the  application:
jsonb-2.0
servlet-5.0
beanValidation-3.0
enterpriseBeansLite
jndi
messaging
appSecurity-4.0
pages
jaxrs-1.1
xmlWS
mdb-4.0
cdi-3.0
enterpriseBeansRemote
jpa-2.0
xmlBinding

SEVERE: CWMIG12085E: A valid feature list for the  application cannot be generated because of the conflicts between required features.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for acme-ee10 0.0.1-SNAPSHOT:
[INFO] 
[INFO] acme-ee10 .......................................... SUCCESS [  0.675 s]
[INFO] AcmeCommon ......................................... SUCCESS [  0.130 s]
[INFO] AcmeAnnuityCommon .................................. SUCCESS [  1.506 s]
[INFO] AcmeAnnuityJAXRSCommon ............................. SUCCESS [  0.519 s]
[INFO] AcmeAnnuityEJB3 .................................... SUCCESS [  0.095 s]
[INFO] AcmeAnnuityEJB3JAXWS ............................... SUCCESS [  0.085 s]
[INFO] AcmeAnnuityEJB3JAXWS_CDI ........................... SUCCESS [  0.093 s]
[INFO] AcmeAnnuityEJB3MDB ................................. SUCCESS [  0.037 s]
[INFO] AcmeAnnuityJAXRSWSes_jaxrs11_m1 .................... SUCCESS [  0.067 s]
[INFO] AcmeAnnuityJAXRSWSes_jaxrs11_m2 .................... SUCCESS [  0.053 s]
[INFO] AcmeAnnuityJAXRSWSes_jaxrs20 ....................... SUCCESS [  0.060 s]
[INFO] AcmeAnnuityPojoWSes ................................ SUCCESS [  0.065 s]
[INFO] AcmeAnnuityWeb ..................................... SUCCESS [  0.107 s]
[INFO] AcmeWebEjbEar ...................................... FAILURE [ 52.203 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  56.872 s
[INFO] Finished at: 2026-07-17T13:34:33-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal io.openliberty.tools:liberty-maven-plugin:4.0.0-SNAPSHOT:dev (default-cli) on project AcmeWebEjbEar: A working set of features could not be generated due to conflicts in the application's API usage: [jsonb-2.0, servlet-5.0, beanValidation-3.0, enterpriseBeansLite-4.0, jndi-1.0, messaging-3.1, appSecurity-4.0, pages-4.0, jaxrs-1.1, xmlWS-4.0, mdb-4.0, cdi-3.0, enterpriseBeansRemote-4.0, jpa-2.0, xmlBinding-4.0]. Review and update your application to ensure it is not using conflicting APIs from different levels of MicroProfile, Java EE, or Jakarta EE. To disable the automatic generation of features, type 'g' and press 'Enter' once dev mode is running or restart dev mode with -DgenerateFeatures=false. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :AcmeWebEjbEar

[rumanaHaque]

Before I ran the generate features, these were the actual features that I have tested this application with:

       appClientSupport-2.0
       appSecurity-5.0
       cdi-4.0
       enterpriseBeans-4.0
       ldapRegistry-3.0
       localConnector-1.0
       mdb-4.0
       messaging-3.1
       messagingClient-3.0
       messagingSecurity-3.0
       messagingServer-3.0
       pages-3.1
       persistence-3.1
       restfulWS-3.1
       xmlWS-4.0
       microProfile-6.0

And these were the features that were generated:

jsonb-2.0
servlet-5.0
beanValidation-3.0
enterpriseBeansLite
jndi
messaging
appSecurity-4.0
pages
jaxrs-1.1
xmlWS
mdb-4.0
cdi-3.0
enterpriseBeansRemote
jpa-2.0
xmlBinding

[turkeylurkey]

@rumanaHaque , when you say these are the actual features you test with does that mean that it is a working set of features accepted by Liberty? It would seem like you do not need any more features generated, could that be true?

[cherylking]

@turkeylurkey She commented out that set of features (that are known to work with the app). She expects a similar list to get generated by generate-features. It does not. She gets a very different set of features and all the failures listed in this issue instead.

[rumanaHaque]

@turkeylurkey - Yes, as Cheryl mentioned, the top list is the actual set of features that I had enabled in my server.xml, when I had set the generateFeatures set to false, and the application worked as expected.
As part of this test, I commented all these features from my server.xml, and had expected that the same features would have been generated using the generateFeatures function. But as you can see from the bottom list - they were very different.

All I had in my server.xml for this test was the empty feature list, with all the features commented out.

<featureManager>

       <!--
      .
       .
       
   -->
   </featureManager>