Community
Participate
Working Groups
When installing BIRT 2.1 using the Update Manager, the user receives a number of warnings (one for each "Feature", I think) indicating the Feature is not signed. This is quiet a disconcerting warning (see attached) and may put some user off installing BIRT. To see this problem, simply follow the installation instructions from the Callisto download site. In summary: 1. Install Eclipse 3.2 IDE 2. In Update Manager, select the BIRT features (and dependencies) 3. Press the "Update" button For future releases, we need to make sure that the BIRT Features are signed in order to avoid this message. (Note that this should also probably be part of the Release Checklist to ensure that it is completed for the final builds).
Created attachment 45786 [details] Verification Warning Dialog
need to coordinate with other Eclipse projects on how to sign features and plugins. Tentatively schedule for 2.1.1.
I upgraded platform from Eclipse Update Site, the warning message appeared also. It seems some of the eclipse update site jars are not signed also. Need to coordinate with other Eclipse projects on jar signing.
Use signed jars for update site in Milestone/Release build.
When updating using signed pack200 files, NPE will be thrown out. Eclipse.org is using a newer version of the jarprocessor to sign jars. See bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=135044. There seems to be a problem when using older versions to unpack a jar signed using the newer one: https://bugs.eclipse.org/bugs/show_bug.cgi?id=163421.
Tested with Eclipse 3.3M6 + signed birt jars on local server. "jarprocessor.exclude.children = true" added to plugin org.eclipse.birt.integration.wtp.ui, which contains eclipse signed jars.
