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.
Done, including source bundle jars.
(In reply to comment #1) > Done, including source bundle jars. Rich, is this an enhancement that was done in the common Modeling builds? Or was it changes that you did in the GMF releng, within the Modeling build framework? It would be great if you could post a brief note on the Modeling Releng Wiki to describe the changes that you made, if there is anything Modeling-centric to it.
I've covered this with Nick in the past. We simply utilize PDE's capability, as per: http://wiki.eclipse.org/PDEBuild/Individual_Source_Bundles Mainly, it involves declaring individualSourceBundles=true in your build.properties file.
[target cleanup] 2.2 M3 was the original target milestone for this bug
[GMF Restructure] Bug 319140 : product GMF and component Releng was the original product and component for this bug
