Community
Participate
Working Groups
Bug 202462 and bug 148782 call for source to be delivered in individual bundles. To do this effeciently we need to have a way of identifying and handling differently source bundles. Ultimately source bundles need never be actually installed as they are never run. PDE discovers them through its model (workspace and target). p2 should make this easy to implement and manage.
In bug 215464 we show a performance slowdown on headless startup because of the increase number of source bundles. Any outlook on when this bug will be fixed? Hopefully the same fix to p2 can also be ported to update to fix bug 215491.
I'll try to do something for M5. However if that was enabled, I'm unclear on how PDE would find the source bundles.
My understanding is that PDE does not use the source bundles from the running host environment. Instead it finds them in the configured target. The target set of bundles in many cases does not match the set of bundles running in the host. This forces PDE to find and parse the bundle manifests from the target themselves to find the source bundles. The end result is the source bundles do not actually have to be installed for PDE to discover them.
(In reply to comment #3) > My understanding is that PDE does not use the source bundles from the running > host environment. Instead it finds them in the configured target. The target > set of bundles in many cases does not match the set of bundles running in the > host. This forces PDE to find and parse the bundle manifests from the target > themselves to find the source bundles. The end result is the source bundles do > not actually have to be installed for PDE to discover them. > Thomas is correct, PDE finds source bundles in the target platform and they do not have to be installed in the host. You can see the current known source bundles on the Source Code Locations tab on the Target Platform preference page.
And in the case of a p2 provisioned SDK, the content of the target platform is derived from the content of the bundles.txt which means that the source bundles will be nowhere to be found :-). I have released a change in the MD Generator that will cause the bundles.txt to not contain the source bundles at install time.
I have released support to write a file listing all the source bundles separately from the bundles.txt. The file will be written in the configuration folder under org.eclipse.source.bundles/source.bundles.txt To leverage the new support you will need to regenerate metadata. The name of the folders and paths can be changed.
