Change modules_ext project template to filter compiled jsps from original module

• Type: Task
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: None
• Fix Version/s: None
• Component/s: Dev Tools > Project Templates
• Labels:
  • 7.3-devtools
  • devtools
  • ee-ts

When using the modules_ext gradle plugin, if you point to a module with JSPs, those will be pre-compiled, and if you try to override any of them, those will be ignored because the JSP servlet will load the compiled jsps from original module instead of new jsp.

This discussion originated here: https://issues.liferay.com/browse/PTR-1741

Jose in that ticket proposes that we add the following configuration to the modules_ext template to support this configuration out of the box:

Bundle-Name: Liferay Portal Search Web
Bundle-SymbolicName: com.liferay.portal.search.web
Bundle-Version: 2.0.35
Import-Package: \
!com.liferay.util.xml,\
!org.apache.jasper.runtime,\
!org.glassfish.jsp.api,\
\
*
Web-ContextPath: /portal-search-web

Include-Resource: "@com.liferay.portal.search.web-2.0.35.jar!/!org/apache/jsp/*"