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.
Doug, beside org.eclipse.cdt.core.win32 and the source plugins, no other plug-ins will get unpacked for installation. Can we say we satisfied this requirement?
I'd say so. Most of the plug-ins are jar'ed. I believe there are ways to jar up these plug-ins as well but that requires some work. The objective is to reduce the load on the servers as we do a good job of it. Marking fixed.
