OSGi Fragments let affected Modules start/stop endlessly (7.3.2+)OSGi Fragments let affected Modules start/stop endlessly (7.3.2+)https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&threadId=1196566292026-04-04T08:48:13Z2026-04-04T08:48:13ZRE: OSGi Fragments let affected Modules start/stop endlessly (7.3.2+)Dominik Markshttps://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=1204798002020-11-30T11:25:56Z2020-11-30T11:25:56Z<p>Is there any progress on this issue? We are facing the same problem...</p>Dominik Marks2020-11-30T11:25:56ZOSGi Fragments let affected Modules start/stop endlessly (7.3.2+)Torsten Rademacherhttps://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=1196566282020-07-27T10:00:12Z2020-07-27T10:00:12ZHello,<br />In the two newest Liferay CE Versions 7.3.2 and 7.3.3 we have a problem with some OSGi fragments:<br />When we deploy e.g. a blogs-web-fragment, asset-publisher-web-fragment or social-bookmarks-taglib-fragment, the log just shows endlessly, that the affected module hast started and then stopped. Of course the module is not available afterwards.<br />For some other module fragments we found out, that there is a new gradle property per module fragment named "compile.jsp.include", but this hat no impact no the fragments named above.<br />Are there any other properties to set for module fragments?<br />We really miss a documentation for this.<br />GreetsTorsten Rademacher2020-07-27T10:00:12Z