Apache OpenOffice (AOO) Bugzilla – Issue 1069
Create an LXR index of the OOo source code repository
Last modified: 2021-05-27 19:28:25 UTC
It would be great if we had an lxr index at say http://lxr.openoffice.org. I understand this is in the pipeline and thought it might be useful to have an issue with which both internal and external people can track the progress of this.
Is there any information available on when this will be available? If there is anything at all I can do to help, please ask.
reset priority to 3 since no existing processes or functionalties are broken. It would be very helpful to provide this help to OpenOffice.org community. Other OpenSource projects (like mozilla, see: http://lxr.mozilla.org) have success with this aid.
Hi, This issue has been entered internally as pcn5398 for investigation/evaluation. Thank you Kat
accepting issue
changing QA contact from bugs@ to issues@
Reassigning all of kat's open issues to support so that I can go through them.
There's a new internal issue number for this (PCN2248), as we're planning to add this to the core product in our next major release (code-named Danube).
An LXR or someother type of cross-referencer would of great help to the community. This issue has been logged for nearly a year now. What are the chances of getting it resolved?? LXR is quite easy to setup and maintain. I would like to see any type of cross-referencer for OpenOffice.org :)
Hi , I noticed this issue some time ago, and have played with LXR. I have successfully implemented this on the OOo codebase on a server at work (alas, behind a firewall) and can only say it is an awesome tool. It might even be useful in determining what code is cruft, and can be pruned. If wanted, I can implementent this on a server at home. Martijn
Cool! Please push it to a public server. I really need it. Now I have to run a debugger (gdb/ddd) to stop a running OO.o and see the backtrace to figure out the call tree.
Hi This won't be implemented until the next upgrade of SC for OOo (at the soonest). So, however desperate you may be to want this, you'll have to be more patient. louis
closing this issue as it is resolved in the Danube release
If an item is fixed in a later SC release, please change status to "resolved/later". Thanks, Stefan.
Ximian now mirrors the OOo CVS at http://ooo.ximian.com/ There are public Bonsai and LXR services available.
This issue was scheduled to be in the Danube release, but has been pushed off to an indeterminate time. Complications have come up which mean that Danube is not now the official release for LXR indexing.
The internal issue has been updated such that this will be considered for the truckee2 release.
Update: Marking this issue Resolved, Later as it is being targeted for a Truckee 2 release of Sourcecast. Action Plan: CollabNet support will check on this issue regularly fro updates. Next Update: As soon as we have more information from Product Management. Thanks, Kristen
In case anyone finds their way to this bug then http://ooo.ximian.com/lxr/ is what you're looking for.
Readjusting the target release as per an internal update.
Can we have that in English, please? What exactly does "PCN2248 Consid-Hudson" mean? This issue has been open for over 3 years, and while I'm gratefult to the Ximian guys for providing LXR support, it'd be really nice to have it on the OOo site.
It appears that the LXR links on ooo.ximian.com/lxr are now broken.o
ooo.x.c/lxr/ is not broken, it is down for some reasons! Hope it will be up soon.A dedicated server should help.
Setting the milestone as 'CEE Consid-future'. Regards, Karishma Support Operations
Why not simply set the milestone as "when hell freezes over", as, given that this issue has been open for 6 years(!!) it is plain that Collab.net have no intention of ever providing this feature?
See http://go-oo.org/lxr/
@smsm1: sure. but wouldn't it be just nice, to have core infrastructure provided by our infrastructure provider?
This feature has been considered for a future release . Moving this issue to the Resolved-Later queue.
Wasn't it planned for a later SC release back as far as 2002?? Can you provide _any_ evidence that this feature might actually get implemented by Collab.net? If not, then isn't marking as "Resolved Later" really a fudge?
We have implemented a search feature for Subversion which be would the next generation Version Control System to be used by Openoffice very very soon . With the help of the new search capability that has been added with the next upcoming release . You can now search Subversion repositories for commits based on the following information: * Log messages * Names of authors * Revision numbers * Date ranges * Combinations of the above criteria However this search capability does not include search of content of repositories or files. Marking this issue as Resolved Later.
Given that, in your own words: "this search capability does not include search of content of repositories or files" and this issue relates to the ability to search and cross-reference the code, I hard think that marking it as "resolved" is appropriate. Re-opening.
Doesn't http://svn.services.openoffice.org/opengrok/ resolve this issue?
Yes, OpenGrok is a more than perfect replacement for LXR. IMHO we can close this issue. The search capabilities mentioned by Jobin in #desc30 are more a functionality similar to Bonsai. Would be nice to get that at svn.services.oo.o
Hurrah :-)
+1 for marking as resolved
Since the subversion search is available in CEE 5.0, Marking this as fixed. Some sample searches with ref to desc30. * you can search for commits based on the log messages in all projects. A search for *Issue12345* will fetch the results of all commits whose log messages hold this text. * you can search for commits within a given date range, or commits made on a single date using the YYYYMMDD format. If you searched using *20070123* (for the date format YYYYMMDD,) the search will fetch all commits on Jan 23 2007. If you searched using *commit_date:[20070123 TO 20070603] * the search will fetch all commits between the date range Jan 23 2007 and June 3 2007. * you can search for commits made by an author with a search pattern like *author:john_doe* in all projects. This will return a list of commits by the user John Doe.