Community
Participate
Working Groups
Add support for pack200
James, Christian: Would either of you guys like to volunteer to try out the new signing & packing system? http://wiki.eclipse.org/Modeling_Project_Releng/Signing_And_Packing Note that the packing step works but the update site is not yet taking advantage of it. Time to overhaul the update site generator.
Bug renamed. Wiki updated -- update site builder now works with Master zip and pack.gz files. GEF is happy; JET packing (see bug 217929) is happy, signing TBD once I get committer status. I'm going to take on EMF next, after that it'll be UML2 or OQTV. Who wants some? ;-)
If it's working so well for everybody else, of course I want some of that! Make it so!
Me too please - for UML2. Thanks, - James.
Max said: I’m having problems with some of the source plugins, org.eclipse.ocl.sources namely, not sure about others. When I install this plugin from the update site (M5 version), I have no zip files in it, and MANIFEST.MF is just a bunch of SHA1 digests. The plugin installs fine into eclipse, but seems to never be loaded. And this leads to unresolved dependencies in my build. Is that a known problem/with workaround or maybe I overlooked something? I said: Crap. Sounds like something is screwy with the "master" zip I'm now using to generate the update site. I can revert to the old method that takes an SDK zip, but that might end up breaking the signing for features... Can you try some other source feature/plugins? The signing/packing is now enabled for EMF, GEF, UML2, OCL, and JET. I think I feel an M5huh coming on. :(
Created attachment 89801 [details] console log showing failure to load gef source plugins Further testing shows: * GEF: all features can be installed from update (including .pack.gz files) but the source features are invalid. Are the source plugins valid, I wonder? See attached console output. * EMF: site OK for EMF 2.4.0M5, but not signed/packed (error in properties file); rerunning with property fixed, site.xml contains <category> but no <features>. This is bad. * UML2: site.xml contains 2.2.0M5 <category> but no <features>. This, too, is bad. * JET: site.xml contains 0.9.0M5 <category> but no <features>. Anyone seeing a pattern here? * OCL: site.xml contains 1.2.0M5 <category> 4 times but only 3 blocks of <features>. Duplication is bad (but easily fixed). However, the 4th <category> w/ no matching <features> suggests a repeat of the above problem. So, it appears we have two problems: * source features should not be signed? or, were not jarred properly prior to signing * buildUpdate.sh's new -siteXMLOnly option isn't working correctly with Master.zip contents to generate <features>, or is trying to put it in the wrong file (site-milestones.xml instead of site-interim.xml?) The good news is that "unsigning" a feature should be easy, and shouldn't affect installation via zip as the zips don't include jarred features. In other words, I don't forsee the need for an set of M5huh builds, just a bunch of work to fix the update sites. Phew!
(In reply to comment #6) > The good news is that "unsigning" a feature should be easy, and shouldn't > affect installation via zip as the zips don't include jarred features. In other > words, I don't forsee the need for an set of M5huh builds, just a bunch of work > to fix the update sites. Phew! Just to confirm, I did extract the GEF-ALL-3.4M5.zip and the source was fine.
(In reply to comment #7) > > Just to confirm, I did extract the GEF-ALL-3.4M5.zip and the source was fine. Similarly, source attachments in OCL M5 are alright, too, when installed from the SDK ZIP. Note that the old style of source-attachment bundle still must be a directory bundle, in case the problem is an attempt to leave them JARred when installing from Update Manager. The new system in PDE 3.4 uses individual JAR bundles.
(In reply to comment #7) > > Just to confirm, I did extract the GEF-ALL-3.4M5.zip and the source was fine. > Bad news, Christian checked and I have verified. The source is not working in GEF-SDK-3.4M5.zip.
(In reply to comment #9) > > Just to confirm, I did extract the GEF-ALL-3.4M5.zip and the source was fine. > Bad news, Christian checked and I have verified. The source is not working in > GEF-SDK-3.4M5.zip. OK, the three SDK zips are fixed. Added the missing source plugins' MANIFEST.MFs and confirmed that the build process won't forget them next time. Word to the wise, Ant's <zipfilesets> apparently need to be explicitly told to include third-level-nested files (eg., plugindir/META-INF/MANIFEST.MF) like this: <include name="**/org.eclipse.gef*" /> <include name="**/org.eclipse.gef*/**" /> <include name="**/org.eclipse.gef*/**/**" /> Zips and updated .md5 files are on emf.torolab and have been synched to download.eclipse.org. Give it 30 mins or so for mirror replication. The GEF update site has been rejigged using the (older) non-signed/non-packed GEF-ALL-*.zip's contents instead of the new signed/packed Master zip... at least until I can figure out why the source features are being corrupted during signing (their manifests are being stripped of their Bundle-* directives and replaced with SHA1-Digest information; also, the src.zip contents are being purged). Spoke with Kim and the platform signing doesn't do this so maybe our source features are different... or maybe I shouldn't be manually jarring them before signing them. Unsure. Now to roll this fix out to the other 4 projects...
> Now to roll this fix out to the other 4 projects... Other update sites have been rolled back to their non-signed/non-packed state. Actually, you might still get packed jars when installing, but NOT for source plugins. Of course there's another problem I encountered, which is that UML2 won't install via update because it seems to think that it needs emf.converter 2.3.0 even though 2.4.0 is installed. See bug 219208. Not sure if this will block GMF builds, or is just an end-user issue.
Signed source plugins are now fixed for EMF. Will run test build for GEF to verify, but it looks promising.
(In reply to comment #12) Signed GEF sources appear as expected in Help > Updates > Manage Config and Help > About > Plugins / Features. If anyone wants to install and test using some deeper mechanism than just checking for breakages in in the above dialogs, you can get this latest test build here: http://emf.torolab.ibm.com/gef/downloads/?project=gef&sortBy=date&hlbuild=0#latest http://emf.torolab.ibm.com/tools/gef/updates/site-interim.xml Moving to verified. If you notice anything amiss, please reopen.
Fix available in HEAD: 1.2.0M7 (S200805061053).
Fix available in HEAD: 1.2.0M7 (S200805061125).
Fix available in HEAD: 1.2.0M7 (S200805061205).
