spring-extender assumes bundle can see Release class when reading Liferay-Require-SchemaVersion

• Type: Bug
• Status: Reopened
• Resolution: Unresolved
• Affects Version/s: Master
• Fix Version/s: None
• Component/s: Dev Tools > Portal Build Env > bnd
• Labels:
  • 7.3-devtools
  • devtools
  • gs-bench

Please refer to PTR-784

The ServiceConfigurationExtender in the spring extender when it reads the Liferay-Require-SchemaVersion header, it assumes the bundle will have visibility to the class com.liferay.portal.kernel.model.Release, see
https://github.com/liferay/liferay-portal/blob/7.1.1-ga2/modules/apps/portal/portal-spring-extender-impl/src/main/java/com/liferay/portal/spring/extender/internal/configuration/ServiceConfigurationExtender.java#L150-L186

However, this may not already be imported by the bundle. So the this import requirement should be emitted by our bnd plugins when processing the bundle that has the Liferay-Require-SchemaVersion