Difference between revisions of "Code Indexer"
m (→Candidates) |
(→Links) |
||
Line 39: | Line 39: | ||
* [http://www.nongnu.org/cvs/ CVS] on non-gnu.org | * [http://www.nongnu.org/cvs/ CVS] on non-gnu.org | ||
* [http://subversion.tigris.org/ Subversion] | * [http://subversion.tigris.org/ Subversion] | ||
+ | * [http://atucker.typepad.com/blog/2005/11/a_new_source_br.html Blog Entry] on OpenGrok | ||
==Notes on Accessing Test Server== | ==Notes on Accessing Test Server== |
Revision as of 14:13, 4 October 2006
Contents
Project Name
Source Code Indexing Service Analysis
Project Description
Mozilla’s source code is enormous—millions of lines of C, C++, JavaScript, Perl, Python, Java, C#, etc. Developers currently use the lxr system to quickly search and browse it on-line: http://lxr.mozilla.org. Mozilla is planning a move from CVS to Subversion for revision control, and at the same time wants to evaluate other source indexing services. Two BSD students are working to setup, document, and test other potential services (e.g., fisheye, opengrok, mxr) on one of the Seneca-Mozilla servers (see below). In each case this requires configuration changes and some scripting to get the services to properly integrate with Mozilla’s other on-line tools. When the test services are installed and synched with the live source tree, Mozilla will point its developers to them and get feedback—the students will help collect and synthesize this feedback.
Project Leader(s)
Project Contributor(s)
Project News and Details
Status
- Set Java's location in /etc/default/tomcat5 --John64 20:15, 3 October 2006 (EDT)
- Figured out port for Tomcat5, 8180 private. Setting up port forwarding as we speak using public port 81 Oct 3, 2006
- Using personal Machine instead of the VM due to it being double NAT-ed, and thus inaccessible from outside the host machine Oct 2, 2006
- Set up server using Ubuntu 6.06LTS with Linux 2.6.17ck1 Oct 2, 2006
- RSyncing machine Oct 2, 2006
Candidates
- LXR/MXR/Bonsai - Not working on setting one up because there is already one
- Gonzui - Impressive looking thing. This will be my first target to setup due to its simplicity and apparently very powerful nature
- OpenGrok - This is by far the coolest project I have come across so far. It uses Java Server Pages, something I know nothing about, so lots of reading. Since this is part of the opensolaris project, I have been thinking of trying to run it in an OpenSolaris Virtual Machine, as that OS is picking up steam. It is available for Linux, and that is the target system. By the way, this one is my favorite so far. Example: Opensolaris
- Fisheye - Commercial Solution that is free (as in beer) for open source projects. Before I start to look at it, I would like to exhaust the numerous open source prospects.
- Hosted by Tigris - I forgot the name, but its hosted by "Tigris" and it looked pretty good. If you know the name, please edit as appropriate
- Horus - Not really what is needed, but its a nice interface for programming students own code. I will not be actively doing anything to it.
- Bazaar - I dont really know what this is, it might be what is needed, but it might be something irrelevant.
- Sourcenav - investigating this project
Links
- Official Blurb just in case I forget what I am doing :P
- John's School Page
- CVS2SVN Tool to convert CVS to SVN. Will be used to test SVN interop.
- Tomcat on Wikipedia
- CVS Checkout
- Rsyncing the CVS
- Tomcat5 on Ubuntu
- Tomcat Tips
- CVS on non-gnu.org
- Subversion
- Blog Entry on OpenGrok
Notes on Accessing Test Server
If you want to access the test server through anything other than port 80, you are going to have to type in the following address into a browser and note the IP address you get in your address bar. This is because I have dynamic DNS. Everything, including the source itself, will be in the http root for easy access to the files. This is not optimal, and will not stay this way once things advance.
Superfind - Will resolve as www.no-ip.com computer, which is why you have to use a browser to get the IP
Questions
Please edit in an answer if you know
What to index
Q: I was wondering if it is prefered to index the source for the current development or stable branch. More specifically, I am unsure how each solution handles file versions.
A: Please Edit Me