Description Mazen Faraj 2005-08-22 10:17:52 EDT

NL support is intro has a bug that appears when plugins that have intro comtent 
are jarred.
when a plugin that contains intro content is jarred, the intro code extracts 
all resources from the directory that contains that intro content file. (The 
assumption is that all resources must be relative to the intro content file and 
so extracting the parent folder is sufficient to expose all resource to the SWT 
browser on the file system).
However, when there is an NL fragment for the jarred intro plugin, the 
extraction code in intro is not sufficient to extract all resources. What is 
happening is that resources from under the fragment are being extracted but the 
original host plugin reousrces are not. This is bad because "delta" resources 
(eg: images and CSS files) can not be dropped in NL fragments. All resources 
need to be copied to the NL fragment to work around this problem.  

Currently, the runtime apis do not have convenience/util apis that return a 
list of URLs that represent a given folder (or IPath) when multiple matches are 
found. The Runtime team supplied a workaround in bug 107374 (btw, that runtime 
team). 

Intro component will use this workaround for 3.1.1. In 3.2, the runtime team 
might posibly include these apis and make them public.