Deploying multiple theme contributors with the same servlet context path does not respect Liferay-Theme-Contributor-Weight

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.1.X, 7.2.X, Master
• Fix Version/s: 7.0.0 DXP FP94, 7.0.10.15 DXP SP15, 7.0.X, 7.1.10 DXP FP19, 7.1.10.5 SP5, 7.1.X, 7.2.10 DXP FP8, 7.2.10.3 DXP SP3, 7.2.X, 7.3.4 CE GA5, 7.3.10 DXP GA1, Master
• Component/s: Themes Infrastructure > Theme Contributor Extender
• Labels:
  • ee-ts
  • liferay-dxp-70-sp15
  • liferay-dxp-71-sp5
  • liferay-dxp-72-sp3
  • liferay-fixpack-de-94-7010
  • liferay-fixpack-dxp-19-7110
  • liferay-fixpack-dxp-8-7210
• Branch Version/s:
  7.2.x, 7.1.x, 7.0.x
• Backported to Branch:
  Committed
• Fix Priority: 3
• Git Pull Request: https://github.com/shuyangzhou/liferay-portal/pull/9293

Steps to reproduce

1. Deploy the attached org.foo.control.menu.one.jar
2. Deploy the attached org.foo.product.menu.jar
3. Run the following cURL command and observe that we get an HTTP 200 response:

   curl --location --head http://localhost:8080/o/control-menu/css/1.css

4. Deploy the attached org.foo.control.menu.two.jar
5. Delete org.foo.product.menu.jar from osgi/modules
6. Deploy the attached org.foo.product.menu.jar again
7. Run the following cURL command:

   curl --location --head http://localhost:8080/o/control-menu/css/2.css

Expectation is that, because org.foo.product.menu.two has a higher Liferay-Theme-Contributor-Weight, its resources should be available and we should see an HTTP 200 response.

Actual behavior is that, because org.foo.product.menu.one was deployed first, the resources for org.foo.product.menu.two are not available and we see an HTTP 404 response.