Hi guys,

My test fragment module gets to the resolved state when I copy it into the deploy folder after portal startup, but only to the installed state when I then restart the portal.

bnd.bnd is:

Bundle-Name: Message Boards Web UI JSP Customizations
Bundle-SymbolicName: org.hopeconsultants.message.boards.web.jsp.mod
Bundle-Version: 1.0.2.1
Fragment-Host: com.liferay.message.boards.web;bundle-version="3.0.33"

The only other file in the project is an empty file at src/main/resources/META-INF/resources/a.jsp (and an empty build.gradle).

In gogoshell when it only gets to the installed state, I can see

 758|Active     |   10|Liferay Message Boards Web (3.0.33)|3.0.33

1123|Installed  |   10|Message Boards Web UI JSP Customizations (1.0.2.1)|1.0.2.1

g! diag 1123
org.hopeconsultants.message.boards.web.jsp.mod [1123]
  Unresolved requirement: Fragment-Host: com.liferay.message.boards.web; bundle-version="3.0.33"

Now if I deploy the fragment module into osgi/static instead of osgi/modules, then it is resolved when I restart the portal. This kind of fits in with the OSGI way of things that a fragment waits around for its host to be installed before the framework attaches it, marks it resolved and starts its host. But none of the OOB modules supplied with Liferay DXP are deployed this way and they work fine.

Does anyone have any idea what is going on?

Ian