Hi Alejandro,

I think this wasn't detected as a breaking change because it is part of the web module, not the API. Anyway, you are right and we should offer an easier path to upgrade this. Please check the following example to know how to upgrade your code:
https://github.com/liferay/liferay-portal/blob/ded0e9390637985231e962e4ad4cfa4639eabb26/modules/apps/asset/asset-publisher-web/src/main/java/com/liferay/asset/publisher/web/internal/portlet/action/AssetPublisherConfigurationAction.java#L143


Also, have you tried the Liferay Upgrade Planner, it probably resolves this kind of issues.


Let us know if you get to upgrade your code.

Hey Alberto!
We have already executed the Liferay Upgrade planner, and sadly, it does not resolve this kind of issues. Afaik, the Liferay Upgrade planner only executed a task to eliminate the versioning number and to try and bring the new dependencies, with some issues itself.
At the end of the day we ended up using the  Liferay Upgrade Planner until it functionality came to an end and started upgrading manually, when we found out this issue.

Thanks for the information provided, I'll comment again when we end up upgrading our module.