Bill Au wrote: > I think that making the path names configurable should be required > rather than optional. I should not require all OpenGrok users to have > things installed under /etc/opengrok and /var/opengrok.
Well at least the /etc/opengrok will be kinda hardcoded, since source.war is populated with web.xml containing the path I don't mind people patching their conf/web.xml for their rpm/deb and then building their own source.war (seems to be the rpm case) , but /etc/opengrok seems to be a good default for configuration.xml ... (at least saves my time for debian & opensolaris patching ;) ) I'll check out a way to make the package relocatable (e.g. having a base, where default base would be / , so if you rellocate to /opt your defaults would be /opt/etc/opengrok, ... ), but I am not sure how portable that would be ... (the appropriate package build-system patches are still the best option I see) ... anyways it would solve the opengrok-per user problem, however the big precondition is to have only one opengrok on the system ... currently it supports projects, so if more people would want to use it, they would just ask their local admin to add their project ... (saves memory for another jvm + another indexer lurking on the system). The reasonable rest will be configurable by cli options ... sends comments, patches, flowers, pizza & drinks my way :-D (review will follow soon, if someone wants to test on OpenSolaris / Debian he is welcome to help me) L P.S. just for reference, current opengrok packages (they all kinda work, but none of them is perfect): http://rpmfind.net/linux/RPM/fedora/9/i386/opengrok-0.6-9.hg275.fc9.noarch.html http://pkgsrc.se/devel/opengrok ( http://cvsweb.netbsd.se/cgi-bin/bsdweb.cgi/pkgsrc/devel/opengrok/Makefile?rev=1.5;content-type=text%2Fplain ) http://mentors.debian.net/debian/pool/contrib/o/opengrok/ ( http://bugs.debian.org/425609 ) > > Bill > > > On Fri, Aug 29, 2008 at 9:21 AM, Lubos Kosco <Lubos.Kosco at sun.com > <mailto:Lubos.Kosco at sun.com>> wrote: > > Trond Norbye wrote: > > Hi all, > > > > The following is my suggestion for a release plan for OpenGrok, > and I > > welcome all comments / discussion so that we can get an > agreement and > > move it to the Wiki page. > > > > If you have additional features that you intend to get merged in > these > > releases, please let us know. > > > > 0.7 > > * The code coverage for blocks must be at least 60% > > * No P1 or P2 bugs > > * All bugs and RFEs must be evaluated > > * The following features must be completed > > * Logging must be completed > > > > * Out of box setup - enhance Opengrok script to provide out of box > functionality ( so deployment into tomcat(glassfish in 0.8) and > easy to > use indexer script ), the only thing needed would be location of > sources > by default - read config from /etc/opengrok/configuration.xml > - write logs + user data into /var/opengrok/data and > /var/opengrok/logs > respectively (on the logs - that would mean having bundled default > logging.properties , e.g. not having to read oga.properties just for > default logger setup ... ) > > optionally make it configurable in case we'd want to go for > /etc/opt or > /var/opt as base - above should work for OpenSolaris + Debian > (paths will not be a problem even for windows, I personally have > C:\etc\opengrok and C:\var\opengrok :-D on my vista laptop ;) ) > > - I'd still would like to have a proper working cli (capturing latest > config defaults ; especially for automated environments this is a > must) > as an primary alternative to JMX approach > > > * ??? > > > > I suggest that we enter feature freeze September 17 2008 (==> > we will > > only apply bug fixes and new tests until 0.7 is released) > > > > 0.8 > > * The code coverage for blocks must be at least 70% > > * No P1 or P2 bugs > > * All bugs and RFEs must be evaluated > > * The following features must be completed > > * Configure everything through the JMX client > > * History cache stored in a database > > * ??? > > > > 0.9 > > * The code coverage for blocks must be at least 80% > > * No P1 or P2 bugs > > * All bugs and RFEs must be evaluated > > * The following features must be completed > > * SCM checkout / update through JMX > > * ??? > > > > > > Looks good otherwise (bearing your and not mine emma tests in mind > ;) ) > > thank you Trond > Lubos > > P.S. the out of box setup is one of the reasons why we don't have a > package in opensolaris nor in debian, so it does matter a bit & > yes I do > volunteer to finish it ;) > > > Cheers, > > > > Trond > > > > _______________________________________________ > > opengrok-discuss mailing list > > opengrok-discuss at opensolaris.org > <mailto:opengrok-discuss at opensolaris.org> > > http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss > > > > _______________________________________________ > opengrok-discuss mailing list > opengrok-discuss at opensolaris.org > <mailto:opengrok-discuss at opensolaris.org> > http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss > >
