You can certainly create a lucene index once and deploy it multiple times with your app. It should be portable if you deploy the relevant lucene jar as well.
So I think that is a yes to "can". Not sure about the "should" though. As far as I'm aware lucene won't index HTML directly although there are HTML parsers you could use to extract the text and pass it to lucene. But there might be better ways to do it - have you asked in the Grails community? -- Ian. On Fri, Nov 18, 2011 at 12:00 AM, Nathan Wells <nwwe...@gmail.com> wrote: > All, > > I'm using the excellent Grails web framework, and the documentation > tool it provides. The documenation tool allows you to write in wiki > and it will output fully formatted and linked documentation. What it > doesn't do is provide a search mechanism for docs (static html). > > I think the best solution to my problem is to generate an index at > build time (after the HTML has been generated), and ship that with the > product. Since these files will literally never change, I want to > avoid having to index every time I deploy my web app. So, in my case, > the "indexing" and the "searching" operations are heavily disjoint. My > question to the group is, Can/Should I do this with Lucene? Is my > approach sane? Can an index be made portable? > > Thanks for your help! > Nathan Wells > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
