To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=110427
User fs changed the following:
What |Old value |New value
================================================================================
Status|REOPENED |RESOLVED
--------------------------------------------------------------------------------
Resolution| |INVALID
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Mon Mar 29 08:14:26 +0000
2010 -------
> I'd not call this "rebranding" but "changing the extension identifier"
No, the *extension identifier* is the thing mentioned in the description.xml.
What was changed here is the name of the resulting .oxt file, which has nothing
to do with the extension identifier. In fact, even in CWS mysqlnative, the .oxt
files as generated during build were (for at least one platform) renamed before
being uploaded to the extension site ...
An now, I cannot answer you why this change was made, that's up to Dirk to
answer, who (I think) did it.
> Besides that, what you added to OOO320 DOES miss the buildfixes I did in
> cws mysqlnative. Should I really need patches to apply myself again because
> you cannot get them over properly?
Hmm - is it possible that you added those fixes after the 1.0 release? We just
copied over the 1.0 release version. But since SVN screw up the thing during a
rebase attempt, it might well be possible we missed something there.
Re-closing as INVALID. Nearly all of the stuff you claimed in the original
description is bogus, including the "extension identifier" thing, as explained
above.
If you need a build issue to be fix, submit a usual build breaker issue, please.
---------------------------------------------------------------------
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: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
