It would be nice if these items in the sandbox would have a pre-compiled copy sitting somewhere easy to download. Highlighting seems to be a fairly common question on these lists from beginners, and having to go to cvs, check them out, and then compile them (when many don't have ant scripts) is a lot of extra places where things can go wrong.
The easiest way would be if all of these were put into an options package directly in the main lucene sources, and the normal build process would not build these. But if you wanted the options, there would be a new target you could call on the main lucene source that would build all of these options. This way there is more of a chance that things will get maintained if used or dumped if not, rather than sitting and cluttering the Sandbox. Dan -----Original Message----- From: Hani Suleiman [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 30, 2003 2:44 PM To: [EMAIL PROTECTED] Subject: Re: New highlighter package available Not that my vote counts or is relevant at all, but +1 to not including it, for the same reasons below. Let Lucene focus on what it does best, and ensure it can support addons and plugins like the highlighter, rather than folding them in. Otis Gospodnetic said: > Couldn't we also stick this in the Sandbox, make sure it builds into a > nice little Jar, and just document it in the Lucene's xdocs? > I'm just thinking that highlighting is not something that is a > necessary feature, so why 'polute' the core that should stay lean as it > is today. > The same has been done with Snowball code. > > I don't feel VERY strongly about this, but I do feel that not including > it in the core would be a better thing to do. Those who need it will > know how to get the highlighting jar and put it in their CLASSPATH. > > Otis > > > --- Erik Hatcher <[EMAIL PROTECTED]> wrote: >> This looks great. >> >> Is everything cool licensing-wise with accepting this? Is it being >> offered to us to be included? >> >> Just a quick glance at the code and the only thing I'd change is the >> default hilighting pre/post strings to be <b>/</b>, or perhaps even >> something even more general like <em>/</em> or <span >> class="hilighted">/</span> - but that is obviously just icing. >> >> Erik >> >> >> On Wednesday, September 24, 2003, at 05:56 PM, Doug Cutting wrote: >> >> > Should this be added into the Lucene core? I suspect lots of folks >> >> > would like to use something like this. >> > >> > Doug >> > >> > [EMAIL PROTECTED] wrote: >> >> Details of a new highlighter package are available here: >> >> http://home.clara.net/markharwood/lucene/highlight.htm >> >> Features include: >> >> * Support for highlighting all query types >> >> * Support for getting "best fragments" summary from large docs * >> Works with latest version of Lucene >> >> Hope you find this useful. >> >> Mark Harwood >> > >> > >> > >> --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] For >> additional commands, e-mail: [EMAIL PROTECTED] >> > > > __________________________________ > Do you Yahoo!? > The New Yahoo! Shopping - with improved product search > http://shopping.yahoo.com > > --------------------------------------------------------------------- To > unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
