Liferay 2025 Q3.0 - Upgrade Jakarta

I created a new workspace with liferay version : 2025 Q3.6 and gradle version is 14.0.2 , after workspace is ready I created a rest-builder module and just doing buildREST in the gradle tasks .

I got javax issue

I did :
./gradlew upgradeJakarta

it updated jakarata but still I’m facing same issue .

I’m using Intellij Idea IDE .

Maybe check out the gradle.properties. It could contain a line like this: com.liferay.portal.tools.rest.builder.version=1.0.377 We had problems before because the version was too low after an upgrade. Try to comment it out, then it should use the most current version of the rest builder fitting to your workspace.

not works , already not exists in gradle.properties

1 Answer

1

The rest-builder defaults to javax for backwards compatibility.

Set javaEEPackage: jakarta in your rest-config.yaml to regen on Jakarta.
See additional details in our documentation.

I recommend running buildREST first, and then upgradeJakartato allow full conversion.

It works as a code , thanks for your support but when I running the liferay ( start server ) Version : 2025 Q3.7 I got many errors in startup 2025-11-05 10:12:50.634 WARN [Framework Event Dispatcher: Equinox Container: 62b81e31-ec05-4b13-ae9d-43084d06e73f][Framework:53] FrameworkEvent WARNING org.osgi.framework.ServiceException: org.apache.felix.scr.impl.manager.SingleComponentManager.getService() returned a null service object at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.factoryGetService(ServiceFactoryUse.java:228)

Is this missing service specifically on your custom rest-builder module? Would need more context on the error message to help diagnose. First step would be to confirm that you can startup liferay successfully without any custom modules deployed.

it's only startup liferay server without any custom modules deployed , I got error on startup it . Version : 2025 Q3.7 JDK 21 Gradle : 14.0.2

I tested a vanilla bundle using blade, 2025.q3.7 & JDK 21 and didn't see start up errors. As a sanity check, can you clear all temporary caches by running something like rm -rf ../../osgi/state/* ../../work/* ../../logs/* ../work/* ../temp/* ../../data/document_library/* ../../data/elasticsearch7/* ../../data/hypersonic/* in /bundles/tomcat/bin

It works, It was caching issue Thanks