Liberty plugin keeps adding jsp-2.3 back to server.xml

[dougbreaux]

I'm trying to use just the newer Jakarta levels. I have a simple server.xml with only

    <featureManager>
        <feature>localConnector-1.0</feature>
        <feature>servlet-6.0</feature>
        <feature>pages-3.1</feature>
    </featureManager>

But when I start that server under Eclipse, it always adds back

        <feature>jsp-2.3</feature>

to which Liberty correctly complains

[ERROR ] CWWKF0044E: The jsp-2.3 and pages-3.1 features cannot be loaded at the same time. The jsp-2.3 feature of Java EE 7 is incompatible with the pages-3.1 feature of Jakarta EE 10. The jsp-2.3 and pages-3.1 configured features include an incompatible combination of features. Your configuration is not supported. Update the configuration to use features that support either the Java EE or Jakarta EE programming models, but not both.

Eclipse version:
Version: 2024-12 (4.34.0)
Build id: 20241128-0757

Plugin version:
IBM WebSphere® Application Server Liberty Developer Tools 2024.0.100.v20240731_1210 com.ibm.websphere.wdt.server.tools

[dougbreaux]

Note also that the single project I've added to this server does not include any facets that should add it back. It only has Dynamic Web Module 6.0, Java 21, and JavaScript 1.0.

Further, if I let the server start and complain, then manually delete the unwanted feature from server.xml and save that, the server refreshes, and my app works normally. But on the next stop/start of the server, the feature gets added back.

[dougbreaux]

I created a brand new server, pointing it at the existing server directory that contains the server.xml I had manually deleted the jsp-2.3 from, and that doesn't seem to be re-adding it so far. But I have no apps added yet.

Further, the one I'm trying to add is complaining that:

The server does not support version 6.0 of the J2EE Web module specification.

that the application needs, and that clearly the server.xml and Java version 21 do support. That might be a different issue from the initial one. Will update after trying a few more things.

[dougbreaux]

Ok, the two problems might be related. When I go to the application in question and set its Dynamic Web Module Facet level from 6.0 to 4.0, then I can add the application to the server, and then jsp-2.3 gets added to server.xml.

At either 6.0 or 5.0, I can't add the application to the server. I also updated the server's feature list to include webProfile-10.0 instead of servlet and pages, in case something additional was necessary there.

So, clearly something in Liberty plugin isn't aware that the server is indeed capable of running this 6.0 app. It does run fine when I fake it to add it, then switch web.xml back to 6.0. Or when I build the same app into a Liberty container image and run that.

[dougbreaux]

Republishing the app also re-adds the feature as well.

(Also, when I change the Dynamic Web Module Facet level to 6.0, the schema references are not corrected to the new Jakarta ones either. Again, I don't know if related or a separate issue.)

[dougbreaux]

After the latest Eclipse updates (2025-03 and whatever else), I now seem to get a popup asking me if I want to include these features, which I can decline. So, at least that's an improvement. But I still don't know why the Liberty plugin thinks my servers are on a lower version of features. For instance, it will won't let me add a web 6.0 project until I temporarily set it to 4.0.

[dougbreaux]

Still occurring on Eclipse 2025-06. Anyone?

[dougbreaux]

Cry