Why two builds?
Beginning with Polarion 2606, Siemens transitioned the Polarion application server from Apache Tomcat 9 to Apache Tomcat 11. This upgrade introduced Jakarta EE 11, which relocates Java web APIs from the legacy Java EE namespace (javax.*) to the Jakarta EE namespace (jakarta.*).
Extensions created for Tomcat 9 / Java EE (Polarion 2512 and earlier versions) lack compatibility with Polarion 2606. The system will examine extensions within the /extensions folder and prevent startup if it detects legacy javax.* web APIs.
As a result, the distribution package for each Nextedy App contains two builds of the same extension.
Choose ONE folder
Select the single folder corresponding to your Polarion version and transfer ONLY that extension folder. Avoid copying both folders into extensions simultaneously.
Polarion 2512 and older (Tomcat 9, Java EE / javax.*) → polarion-2512-and-older/com.nextedy.Risksheet/
Polarion 2606 and newer (Tomcat 11, Jakarta EE 11 / jakarta.*) → polarion-2606-and-newer/com.nextedy.Risksheet/
This applies to every Nextedy product; the example provided is representative only.
Update Procedure
Update Polarion to 2606
Polarion will flag incompatible extensions during startup
Stop the Polarion service
Uninstall the previous version of the Nextedy app (e.g., com.nextedy.Risksheet)
Copy the selected com.nextedy.Risksheet folder to: POLARION_HOME/polarion/extensions/
Follow instructions in INSTALL.txt within the copied folder
Remove POLARION_HOME/data/workspace/.config
Start the Polarion service