Very nice.
It would be able nice to set the browse path using a system property for
convenience and security.
Also I thought that I'd mention that you need a nightly build for this since
2.2 won't work.
-
To unsubscribe, e-mai
Are there any licensing issues with GWT? (I've never used it)
OK on that score I think :
http://code.google.com/webtoolkit/terms.html
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL P
On Nov 14, 2007, at 1:26 PM, Chris Hostetter wrote:
: Seems like a fine place to put it for now. But it really deserves
a better
: home than that. What about a new "client/luke" directory?
(following on
: Solr's structure).
i'd vote to stick with contrib ... it's just easier on the bu
: Seems like a fine place to put it for now. But it really deserves a better
: home than that. What about a new "client/luke" directory? (following on
: Solr's structure).
i'd vote to stick with contrib ... it's just easier on the build system.
: > 3) What needs to change in the build process
wid Weiss <[EMAIL PROTECTED]>
To: java-dev@lucene.apache.org
Sent: Wednesday, 14 November, 2007 4:55:22 PM
Subject: Re: Web-based Luke
> I'm putting together a Google Web Toolkit-based version of Luke:
>http://www.inperspective.com/lucene/Luke.war
This is neat, Mark!
At first I
I'm putting together a Google Web Toolkit-based version of Luke:
http://www.inperspective.com/lucene/Luke.war
This is neat, Mark!
At first I thought: darn, how the heck is he accessing the filesystem from
JavaScript (GWT or otherwise)?! Then it became clear to me that it's actually
the _
On Nov 12, 2007, at 1:21 PM, mark harwood wrote:
I'm putting together a Google Web Toolkit-based version of Luke:
http://www.inperspective.com/lucene/Luke.war
( Just add your version of lucene core jar to WEB-INF/lib
subdirectory and you should have the basis of a web-enabled Luke.)
Mark:
