I'm surprised no one noticed the mismatch of encodings before.
Let's see what the forrest folks have to say...
http://www.mail-archive.com/user@forrest.apache.org/msg01652.html
-Yonik
On 1/30/06, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> Hmmm, the c in Gospodnetic got messed up somewhere in the c
Hmmm, the c in Gospodnetic got messed up somewhere in the chain of things...
I put it in the source xdoc as ć and that worked in the local preview.
That turned into <87> in the generated XML (which still looks fine
if I point by browser at the local file).
When it's served up by apache though, it
Looking nice! Cool.
Yoav
On 1/30/06, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> Basic web site is up.
>
> http://incubator.apache.org/solr/
>
> Built with Forrest 0.7, it grew on me after I got over the stumbling blocks.
> I discovered that "forrest run" also allows you to change the source
> doc
Basic web site is up.
http://incubator.apache.org/solr/
Built with Forrest 0.7, it grew on me after I got over the stumbling blocks.
I discovered that "forrest run" also allows you to change the source
documents and just hit reload in the browser... no need to rebuild to
see the changes.
-Yonik
Yonik Seeley wrote:
Many of the things in the lucene package (FunctionQuery and
SynonymFilter) could be moved to org.apache.solr, and renamed to
org.apache.lucene if/when they officially become part of lucene.
But the other reason for the org.apache.lucene package is for
accessing package-protec
Nutch is a Lucene sub-project, and it uses org.apache.nutch, not
org.apache.lucene.nutch.
I'd follow that for consistency's sake, until we see a problem.
Otis
- Original Message
From: Yonik Seeley <[EMAIL PROTECTED]>
To: solr-dev@lucene.apache.org
Cc: solr-commits@lucene.apache.org
Sent
I think I got it under control now... it was the ext:wiki in tabs.xml
that was causing the problems for forrest 0.7
-Yonik
On 1/30/06, Doug Cutting <[EMAIL PROTECTED]> wrote:
> Yoav Shapira wrote:
> > OK, consistency is a good value. I still think it's more of a pain
> > than it's worth, unless
Ian Holsman wrote:
Doug mentioned that we could use the lucene 'zone' to get a working demo
of Solr which I think we should start as soon as we can get a build going.
We certainly could do this, but I'm not sure that we should. A real
Solr demo will be read/write, and I'm not sure we want to
Yoav Shapira wrote:
OK, consistency is a good value. I still think it's more of a pain
than it's worth, unless Nutch/Lucene are using Forrest features that
can't be done far more simply. We could achieve the same look and
feel via CSS skinning I'd imagine... But since I don't have much
bandwid
> ping infra again after a long enough period has passed).
> http://issues.apache.org/jira/browse/INFRA-687
The Wiki has been created!
http://wiki.apache.org/solr
-Yonik
If anyone wants to try things out, you would have to:
- install the WAR file in webapps as ROOT.
- explode the WAR, and put solarconfig.xml and schema.xml (and files
it references) in WEB-INF/classes where the classloader can find it.
Look in src/testapps/... for examples of these files.
-Yonik
On 1/30/06, Ian Holsman <[EMAIL PROTECTED]> wrote:
> Hi guys.
>
> I was wondering if anyone has come up with a list of things they want to
> accomplish in the next 3-4 weeks. (and are looking for volunteers to do)
>
> So far I've heard:
>
> - a ANT file
> - a small working demo
The main purpose wou
Hola,
OK, consistency is a good value. I still think it's more of a pain
than it's worth, unless Nutch/Lucene are using Forrest features that
can't be done far more simply. We could achieve the same look and
feel via CSS skinning I'd imagine... But since I don't have much
bandwidth to spend on t
I started with Forrest simply because Nutch and the top level Lucene use it.
-Yonik
On 1/30/06, Yoav Shapira <[EMAIL PROTECTED]> wrote:
> Why Forrest? I think it's over-engineered for simple sites. The
> xdocs approach is so much easier to understand and use on a regular
> basis. See e.g.
> ht
Hi,
> - a ANT file
> - a small working demo
The Ant file is in the repository already (top-level build.xml). It
includes a target called "dist-war", which can be called directly and
is also automatically called as part of the standard "dist" target.
The dist-war target creates a WAR file that w
Why Forrest? I think it's over-engineered for simple sites. The
xdocs approach is so much easier to understand and use on a regular
basis. See e.g.
http://svn.apache.org/viewcvs.cgi/logging/site/trunk/.
Yoav
On 1/30/06, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> Sigh. When I deleted most of th
16 matches
Mail list logo
