Hi, On Fri, Aug 10, 2012 at 2:05 PM, Ariel Constenla-Haile <arie...@apache.org> wrote: >> > I will request release blocker status, so that the fix gets included in the >> > next release. >> > This isn't really a release blocker, but the fix is very trivial and it >> > has no >> > risk at all. On the other hand, Programmability should always be a top >> > priority >> > in Apache OpenOffice, because it is a way to develop custom solutions on >> > top of >> > Apache OpenOffice binary release without the need to rebuild from source >> > code >> > nor hack it around. And as the reporter says, this bug is rather annoying. >> > >> > >> >> even trivial fixes are tricky sometimes. Do we have the fix in place and can >> we do some code review? > > I commit it on trunk: > http://svn.apache.org/viewvc?view=revision&revision=1371665 > The bug is far from making AOO "absolutely unusuable".
Some background information, as I was told that I (1) was "quoted" on another bugzilla (2). Looking at all the German names, it looks like most of them come from the WollMux people from München's LiMux project (3). I couldn't find information if they are still using OpenOffice.org, or if they have migrated to LO, or are planning to do so with Apache OpenOffice, Google search shows most results for OOo and WollMux. Any way it does not seem a good idea to make API users wait until the next release to have this bug fixed. You can see this bug annoyance by running the SDK examples openoffice.org/basis3.4/sdk/examples/DevelopersGuide/FirstSteps openoffice.org/basis3.4/sdk/examples/DevelopersGuide/OfficeBean and even using the NB plug-in: in a new AOO Component Project, bootstrapping to fill the tree with types opens the Start Center too. Regards (1) https://issues.apache.org/ooo/show_bug.cgi?id=120501#c2 (2) https://bugs.freedesktop.org/show_bug.cgi?id=42470#c14 (3) http://www.muenchen.de/Rathaus/dir/limux/english/index.html Amongs other, see http://de.wikipedia.org/wiki/LiMux
