Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #252800 +++ Projects must use jar'ed plug-ins (with unpack=false) unless authorized by the planning council for technical reasons. Nested jars should be avoided if possible since it creates problems for projects that has dependencies to such plug-ins. The OSGi runtime is fine with it but the compiler is not able to handle classpaths that contain nested jars. In case only one nested jar exists, it is often better to expand the contents of that jar into the root folder (i.e. unnest the jar). If a plug-in contains large files that are frequently used (opened and closed), a jar'ed plug-in might degrade performance significantly since the file must be decompressed each time it is opened.
Xiaoying, can we verify that we do this when we start doing Galileo builds?
To use jars for dtp source plugins, I will change current org.eclipse.datatools.sdk.feature.source into individule source bundles. The affected package will be dtp-sdk package.
Please note that this is for Galileo only, so we should not do this for our 1.6.2 build scripts. We'll need to keep them separate.
The change will only go into HEAD after 1.6.2 branch is created.
Fixed.
