Community
Participate
Working Groups
Using I20070220-1330, 1) create a plugin 2) convert it to a fragment of another plugin 3) put it back as a plugin 4) Create another plugin and try to add the first plugin in the dependencies list. The first plugin is not available. This is pretty bad. Also it would be nice to get an easy way (easier than editing manually the manifest file) to convert a plugin to a fragment.
we will take a look at the bug portion. As for adding UI support in the editor to convert a fragment to a plug-in or vice versa, this would be a pretty low priority enhancemnt as it gives very little bang for the buck. Fragments are rare in general and converting back and forth is even more rare, and it would not make sense for us to invest in time/editor real estate to support it. After all, it can be done on the source page by removing one line.
Set as critical since once broken it is a nightmare to get back to a workable state.
This scenario works fine for me. Olivier, are there any missing steps?
Ok, I reproduced it again: 1) Create three plugins test_plugin, test_plugin2 and test_plugin3. 2) No dependencies between them. 3) Convert test_plugin2 as a fragment of test_plugin by adding: Fragment-Host: test_plugin in the MANIFEST.MF file. 4) Restart 5) Remove the line that defines the fragment 6) Try to add test_plugin2 in the dependencies list of test_plugin3. It is not available.
Scenario in comment 4 is reproducible. Thanks.
Fixed.
