To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=116342
User sb changed the following:
What |Old value |New value
================================================================================
Status|UNCONFIRMED |RESOLVED
--------------------------------------------------------------------------------
Resolution| |WORKSFORME
--------------------------------------------------------------------------------
------- Additional comments from s...@openoffice.org Fri Jan 7 14:58:20 +0000
2011 -------
"it appears that calling 'jarsigner <jar> <alias>' to sign a JAR completely
overwrites the JAR's existing META-INF/MANIFEST.MF, thus effectively dropping
the relevant UNO component attributes from the main section": My mistake was
that I tried this on a manifest whose main section did not start with the
required Manifest-Version attribute.
@cfries: I cannot reproduce your problem, at least not on DEV300_m96. Creating
a valid UNO component JAR, signing it with jarsigner, and including the result
in a valid OOo extension, the resulting extension can be installed without
error. (I do not know what your CentralRegistrationClass and its
RegistrationClasses attribute are, maybe that is where the problem lies.)
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@udk.openoffice.org
For additional commands, e-mail: issues-h...@udk.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
