==Project News and Details======Status====* Set Java's location (usr/lib/jvm/java-1I now have some time to resume work on the project.5.0-sun-1.5.0.06/) in /etc/default/tomcat5 --[[User:John64|John64]] 20:15, 3 October 2006 (EDT) This time I will manage my time more wisely* Figured out port for Tomcat5, 8180 private<strike>I have too many assignments. Setting up port forwarding as we speak using public port 81 Oct 3, 2006* Using personal Machine instead of the VM due I need to it being double NAT-eddo work on them, and thus inaccessible from outside but I should have more free time during the host machine Oct 2, 2006* Set up server using Ubuntu 6Christmas break.06LTS with Linux 2.6.17ck1 Oct 2, 2006* RSyncing machine Oct 2, 2006</strike>

====Candidates==Options==* Help with [http://lxr.mozilla.org/ LXR]/[http://landfill.mozilla.org/mxr-test/ MXR]/[http://www.mozilla.org/bonsai.html Bonsai] - Not working on setting one up because there is already onedevelopment.* Make a sort-of branch respectful version of [[http://gonzui.sourceforge.net GonzuiOpenGrok]] - Impressive looking thing. This will but this would be my first target to setup due to its simplicity and apparently a very powerful natureshoddy implementation that doesn't really do what it should* [http://www.opensolaris.org/os/project/opengrok/ Setup one OpenGrok] - This is by far per active branch of the coolest project I have come across so far. It uses Java Server PagesMozilla Project, something I know nothing about, so lots of reading. Since this is part of the opensolaris project, I would have been thinking of trying to run it in an OpenSolaris Virtual Machineno version history whatsoever, as that OS is picking up steamapart from file dates. It is available for Linux, * [Re]write major portions of how [[OpenGrok]] deals with history and changesets and that is the target system. By the waylikes, this one is my favorite so far. Example: [http://cvs.opensolarispersonal preference.org/source/ Opensolaris]* Try to fit [http://www.cenqua.com/fisheye/index.html Fisheye] - Commercial Solution that is free (as in beer) into the current development model, but it seems this might be more like finding a problem for open source projectsa solution. Before I start to look at This is a very very powerful tool, but itis not really like LXR or OpenGrok, I would like it is more useful to exhaust analyze CVS/SVN histories more than search for functions, files, definitions and the numerous open source prospectslikes. Fisheye is also '''extremely''' slow.* Hosted by Tigris - I forgot the name Within my lan, it takes a long time to do any queries, but its hosted by "Tigris" and over the internet it looked pretty goodis impossible. If you I don't know why, especially since OpenGrok uses the name, please edit as appropriate* [http://savannahsame basic technologies.nongnu.org/projects/horus Horus] - Not really what is needed(10 minutes plus for one page load on a lan connection, but in its a nice interface for programming students own code. I will not be actively doing anything to it.* [http://bazaar-vcs.org Bazaar] - I dont really know what this isdefence, it might be what is needed, but it might be something irrelevant.* [http://sourceforge.net/projects/sourcenav/ Sourcenav] - investigating this projectstill indexing the code)

====LinksWhy I like OpenGrok====Apart from the fact that it does not support branches, this is in my opinion the perfect tool. It is fast, open souce and most importantly, it makes really easy to navigate, well thought out pages that just work. Because of the way OpenSolaris does file versions for their code, they don't use branches at all. OpenSolaris currently uses a linear method of file versioning, they don't use branches, they use versions as a sory of branch, basically the idea that Office 12 is the "2007 branch" and Office 11 is the "2003 branch". Mozilla doesn't do this, so it would be nessecary to implement this feature. Luckily, however, OpenGrok is very modularized and atomic in nature. If you go to the OpenGrok page, you can get a more complete explanation, but the basic jist of it is that there are many "Guru's", each with a task. The files are first read by the History Guru who looks at the file and decides what type of versioning the file uses. Once the versions have been analyzed, they are passed on to the file analyzer guru who then decides what type of file it is, and passes it on to a file type analyzer. The allows for portions of the code to be changed without changing the whole system, so if we wanted to be able to do special things with XUL/XPCOM as far as how to handle its symbols, we would write one module which is not dependent at all on any other file analyzer. The same way, if Mozilla switchs to SVN, we would just port the branching support to SVN. On the chances that Mozilla switches to something other than CVS or SVN, a HistoryGuru could be written for that type of versioning history. The OpenGrok project is under the [http://www.sun.com/cddl/ CDDL] which [http://www.sun.com/cddl/CDDL_MPL_redline.pdf derives from the MPL 1.1] In closing, I really like the OpenGrok project because it is '''very''' fast, '''very''' powerful and '''VERY''' modular! ==Links==

* [http://endeveloper.wikipediamozilla.org/wikien/Apache_Tomcat Tomcat on Wikipediadocs/Mozilla_Source_Code_Via_CVS Devmo:CVS Checkout]* [http://developer.mozilla.org/en/docs/Mozilla_Source_Code_Via_CVS Rsyncing_the_CVS_Repository Devmo: Rsyncing the CVS Checkout]* [http://developer.mozilla.org/en/docs/Rsyncing_the_CVS_Repository Rsyncing the CVS_Tags Devmo: CVSTags]- to get the branches to checkout

==Notes on Accessing Test Server==foreach (@branches){If you want to access # Download the test server through anything other than port 80makefile, you are going to have to type in then checkout from the following address into a browser and note the IP address you get in your address barmakefile system(" mkdir ${src_root}/$_; cd ${src_root}/$_; cvs -d ${cvsserver} co -r $_ mozilla/client. 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 advancemk; make -f ${src_root}/${_}/mozilla/client.mk checkout MOZ_CO_PROJECT=all; ");}

====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. <br/pre>A: Please Edit Me