[Jakarta Lucene Wiki] Updated: PoweredBy

Date: 2004-11-26T17:04:32 Editor: RoyDebox <[EMAIL PROTECTED]> Wiki: Jakarta Lucene Wiki Page: PoweredBy URL: http://wiki.apache.org/jakarta-lucene/PoweredBy no comment Change Log: -- @@ -53,6 +53,7 @@

Fwd: help with official binary mirrored releases

Here is some more info on making releases. Erik Begin forwarded message: From: David Crossley <[EMAIL PROTECTED]> Date: November 26, 2004 5:31:53 PM EST To: Jakarta Project Management Committee List <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: help with official binary mirrored re

RE: encoding of german analyzer source files

Actually, in Netbeans 4.0 although you can tell the editor the encoding for each file individually, that doesn't solve your problem. At least for standard projects, you can only provide the required compiler switch (-encoding UTF-8) at the project level. I ran into this same issue building Lucene

Re: encoding of german analyzer source files

On Friday 26 November 2004 23:40, Murray Altheim wrote: > In grepping through the source I noted nine instances of a lowercase > use of " registered as a bug. Kinda makes me wonder what's generating that, > because when I run javadoc on my own stuff this doesn't happen. This (package.html) isn't

Re: encoding of german analyzer source files

I wrote: [...]> You can sniff the first few bytes (which is what is recommended in the XML 1.0 spec, you can see how they do it there), but making such an assumption may lead to program failure if the assumption is incorrect. Extensible Markup Language (XML) 1.0 (Third Edition) Appendix F Aut

Re: encoding of german analyzer source files

Andi Vajda wrote: I can tell the NetBeans-IDE the encoding of every single source file. But the problem is that I might not know which the correct encoding is. In case of Lucene it is quite clear because it is mentioned in the build.xml file. But what is the situation if someone sends you a stem

Re: encoding of german analyzer source files

I can tell the NetBeans-IDE the encoding of every single source file. But the problem is that I might not know which the correct encoding is. In case of Lucene it is quite clear because it is mentioned in the build.xml file. But what is the situation if someone sends you a stemmer class for exa

[Jakarta Lucene Wiki] Updated: PoweredBy

Date: 2004-11-26T11:23:17 Editor: TomBloomfield <[EMAIL PROTECTED]> Wiki: Jakarta Lucene Wiki Page: PoweredBy URL: http://wiki.apache.org/jakarta-lucene/PoweredBy no comment Change Log: -- @@ -44,6 +44,

Re: cvs commit: jakarta-lucene/xdocs index.xml

On Nov 26, 2004, at 1:40 PM, Christoph Goller wrote: So why not merge these changes back to 1.4.3 and keep the site purely at that branch? Well, it seems that the Lucene website is something that changes more often than releases. So I don't see much sense in using the outdated 1.4.3 branch versi

Re: cvs commit: jakarta-lucene/xdocs index.xml

On Nov 26, 2004, at 12:09 PM, Christoph Goller wrote: Erik Hatcher schrieb: On Nov 26, 2004, at 11:40 AM, [EMAIL PROTECTED] wrote: - href="http://cvs.apache.org/dist/jakarta/lucene/v1.4.2/";>here. + href="http://cvs.apache.org/dist/jakarta/lucene/v1.4.3/";>here. Di

Re: cvs commit: jakarta-lucene/xdocs index.xml

Erik Hatcher schrieb: On Nov 26, 2004, at 1:14 PM, Christoph Goller wrote: Erik Hatcher schrieb: On Nov 26, 2004, at 12:09 PM, Christoph Goller wrote: The distribution will contain docs and API from branch 1.4.3. For the web-page I plan to use docs from the CVS head, but API Javadoc from 1.4.3 bran

Re: cvs commit: jakarta-lucene/xdocs index.xml

On Nov 26, 2004, at 1:14 PM, Christoph Goller wrote: Erik Hatcher schrieb: On Nov 26, 2004, at 12:09 PM, Christoph Goller wrote: The distribution will contain docs and API from branch 1.4.3. For the web-page I plan to use docs from the CVS head, but API Javadoc from 1.4.3 branch. Does this sound re

Re: cvs commit: jakarta-lucene/xdocs index.xml

I found the following link: jakarta.apache.org/site/convert-to-mirror.htm - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: cvs commit: jakarta-lucene/xdocs index.xml

Erik Hatcher schrieb: On Nov 26, 2004, at 12:09 PM, Christoph Goller wrote: The distribution will contain docs and API from branch 1.4.3. For the web-page I plan to use docs from the CVS head, but API Javadoc from 1.4.3 branch. Does this sound reasonable? I think you should use everything from th

Re: cvs commit: jakarta-lucene/xdocs index.xml

On Nov 26, 2004, at 12:09 PM, Christoph Goller wrote: The distribution will contain docs and API from branch 1.4.3. For the web-page I plan to use docs from the CVS head, but API Javadoc from 1.4.3 branch. Does this sound reasonable? I think you should use everything from the 1.4.3 branch. I did no

Re: cvs commit: jakarta-lucene/xdocs index.xml

Erik Hatcher schrieb: On Nov 26, 2004, at 11:40 AM, [EMAIL PROTECTED] wrote: - href="http://cvs.apache.org/dist/jakarta/lucene/v1.4.2/";>here. + href="http://cvs.apache.org/dist/jakarta/lucene/v1.4.3/";>here. Did you sign the binary files and place there where the

cvs commit: jakarta-lucene/docs index.html

goller 2004/11/26 08:52:15 Modified:docs Tag: lucene_1_4_2_dev index.html Log: Revision ChangesPath No revision No revision 1.47.2.2 +3 -3 jakarta-lucene/docs/index.html Index: index.html =

Re: cvs commit: jakarta-lucene/xdocs index.xml

On Nov 26, 2004, at 11:40 AM, [EMAIL PROTECTED] wrote: - href="http://cvs.apache.org/dist/jakarta/lucene/v1.4.2/";>here. + href="http://cvs.apache.org/dist/jakarta/lucene/v1.4.3/";>here. Did you sign the binary files and place there where the mirrors will pick the

cvs commit: jakarta-lucene/xdocs index.xml

goller 2004/11/26 08:40:10 Modified:xdocsTag: lucene_1_4_2_dev index.xml Log: Revision ChangesPath No revision No revision 1.20.2.2 +4 -4 jakarta-lucene/xdocs/index.xml Index: index.xml ===

Re: encoding of german analyzer source files

Murray Altheim wrote: Stefan Wachter wrote: Hi Daniel, I am using NetBeans 3.6 which certainly is unicode aware. Yet, NetBeans seems not to detect that the source files of Lucene are UTF-8 encoded automatically. I guess that it uses the platform specific default encoding which is ISO-8859-1 for

Re: encoding of german analyzer source files

Stefan Wachter wrote: Hi Daniel, I am using NetBeans 3.6 which certainly is unicode aware. Yet, NetBeans seems not to detect that the source files of Lucene are UTF-8 encoded automatically. I guess that it uses the platform specific default encoding which is ISO-8859-1 for my Linux operating sys

Re: encoding of german analyzer source files

Hi Daniel, I am using NetBeans 3.6 which certainly is unicode aware. Yet, NetBeans seems not to detect that the source files of Lucene are UTF-8 encoded automatically. I guess that it uses the platform specific default encoding which is ISO-8859-1 for my Linux operating system. I think what Jav

Re: encoding of german analyzer source files

On Friday 26 November 2004 11:42, Stefan Wachter wrote: > With UTF-8 encoding theses source > files look rather strange when viewed on an "ISO-8859-1" development > environment because they contain german umlauts and the "sharp s". Your editor / IDE needs to be unicode aware and you have to set i

encoding of german analyzer source files

Hi all, in the 1.4.2 distribution the source files of the german analyzer classes are encoded in UTF-8. (CHANGES.txt reports that Otis Gospodnetic changed the file encoding of theses files to UTF-8. I guess that their original encoding was ISO-8859-1.) With UTF-8 encoding theses source files lo

DO NOT REPLY [Bug 32403] - [PATCH] When locks are disabled, IndexWriter.close() throws NullPointerException

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 32403] New: - [PATCH] When locks are disabled, IndexWriter.close() throws NullPointerException

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: Release 1.4.3

Christoph Goller wrote: I think i should finally make Release 1.4.3. Great! I presume the default.properties does no longer exist. I just fill in "1.4.3" as version in the build.xml before building it. Is this ok? I build releases with something like: ant -Dversion=1.4.3 clean dist So that it doe