date:20070605


 [ 
https://issues.apache.org/jira/browse/LUCENE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Doron Cohen resolved LUCENE-446.


Resolution: Fixed

committed (experimental mode).

 search.function - (1) score based on field value, (2) simple score 
 customizability
 --

 Key: LUCENE-446
 URL: https://issues.apache.org/jira/browse/LUCENE-446
 Project: Lucene - Java
  Issue Type: New Feature
  Components: Search
Reporter: Yonik Seeley
Assignee: Doron Cohen
Priority: Minor
 Fix For: 2.2

 Attachments: function.patch.txt, function.patch.txt, 
 function.patch.txt, function.zip, function.zip


 FunctionQuery can return a score based on a field's value or on it's ordinal 
 value.
 FunctionFactory subclasses define the details of the function.  There is 
 currently a LinearFloatFunction (a line specified by slope and intercept).
 Field values are typically obtained from FieldValueSourceFactory.  
 Implementations include FloatFieldSource, IntFieldSource, and OrdFieldSource.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (LUCENE-850) Easily create queries that transform subquery scores arbitrarily


[ 
https://issues.apache.org/jira/browse/LUCENE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501620
 ] 

Doron Cohen commented on LUCENE-850:


Mike,

If I understood it correctly your patch can be described as:
- turn DisMaxQuery into a private case of a new generalized 
CustomizableOrQuery
- demostrates this customizability with a new ProductQuery.
- DisMax(OR)Query logic is as before = max =f scob-scores plus tie breaker.
- Product(OR)Query logic is: score = multiplication of scores of sub-scorers.

The regular Bolean Or could probably be phrased this way as Sum(OR)Qurey.

Now in LUCENE-446 I added CustomScoreQuery, which is simpler: 
- score = f (score(q), score(vq))
where 
- f() is overridable, 
- q is any query
- vq is optional, and it is a value-source-query, likely based on (cached) 
field values.

So it currently doesn't support your comment
   I've often wanted to multiply the scores of two queries.

When first writing CustomScoreQuery I looked at combining any two or N 
subqueries, but wasn't sure how to do this. How to normalize. How to calculate 
the weights. But now I think that we could  perhaps follow your approach 
closer: call it CustomOrQuery, go for any N subqueries, and define f() 
accordingly. 

But is this really required / useful?  
What are the use cases for this general/arbiterary combining of scores (beyond 
current capabilities of o.a.l.search.function)?

Thanks,
Doron

 Easily create queries that transform subquery scores arbitrarily
 

 Key: LUCENE-850
 URL: https://issues.apache.org/jira/browse/LUCENE-850
 Project: Lucene - Java
  Issue Type: New Feature
  Components: Search
Reporter: Mike Klaas
Assignee: Doron Cohen
 Attachments: prodscorer.patch.diff


 Refactor DisMaxQuery into SubQuery(Query|Scorer) that admits easy 
 subclassing.  An example is given for multiplicatively combining scores.
 Note: patch is not clean; for demonstration purposes only.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (LUCENE-850) Easily create queries that transform subquery scores arbitrarily


 [ 
https://issues.apache.org/jira/browse/LUCENE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Doron Cohen updated LUCENE-850:
---

 Assignee: (was: Doron Cohen)
Lucene Fields: [Patch Available]  (was: [New, Patch Available])

 Easily create queries that transform subquery scores arbitrarily
 

 Key: LUCENE-850
 URL: https://issues.apache.org/jira/browse/LUCENE-850
 Project: Lucene - Java
  Issue Type: New Feature
  Components: Search
Reporter: Mike Klaas
 Attachments: prodscorer.patch.diff


 Refactor DisMaxQuery into SubQuery(Query|Scorer) that admits easy 
 subclassing.  An example is given for multiplicatively combining scores.
 Note: patch is not clean; for demonstration purposes only.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (LUCENE-907) Demo and contrib jars should contain NOTICE.TXT and LICENSE.TXT

Demo and contrib jars should contain NOTICE.TXT and LICENSE.TXT
---

 Key: LUCENE-907
 URL: https://issues.apache.org/jira/browse/LUCENE-907
 Project: Lucene - Java
  Issue Type: Bug
  Components: Build
Reporter: Michael Busch
Assignee: Michael Busch
Priority: Trivial
 Fix For: 2.2


We should include NOTICE.TXT and LICENSE.TXT not only in the core jar but also
in the demo and contrib jars.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (LUCENE-907) Demo and contrib jars should contain NOTICE.TXT and LICENSE.TXT


 [ 
https://issues.apache.org/jira/browse/LUCENE-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Busch updated LUCENE-907:
-

Attachment: lucene-907.patch

With this patch the two files are included in the META-INF dir of
the demo jar, the demo war and the contrib jars.

I will commit this soon.

 Demo and contrib jars should contain NOTICE.TXT and LICENSE.TXT
 ---

 Key: LUCENE-907
 URL: https://issues.apache.org/jira/browse/LUCENE-907
 Project: Lucene - Java
  Issue Type: Bug
  Components: Build
Reporter: Michael Busch
Assignee: Michael Busch
Priority: Trivial
 Fix For: 2.2

 Attachments: lucene-907.patch


 We should include NOTICE.TXT and LICENSE.TXT not only in the core jar but also
 in the demo and contrib jars.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Resolved: (LUCENE-907) Demo and contrib jars should contain NOTICE.TXT and LICENSE.TXT


 [ 
https://issues.apache.org/jira/browse/LUCENE-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Busch resolved LUCENE-907.
--

Resolution: Fixed

Committed.

 Demo and contrib jars should contain NOTICE.TXT and LICENSE.TXT
 ---

 Key: LUCENE-907
 URL: https://issues.apache.org/jira/browse/LUCENE-907
 Project: Lucene - Java
  Issue Type: Bug
  Components: Build
Reporter: Michael Busch
Assignee: Michael Busch
Priority: Trivial
 Fix For: 2.2

 Attachments: lucene-907.patch


 We should include NOTICE.TXT and LICENSE.TXT not only in the core jar but also
 in the demo and contrib jars.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (LUCENE-794) SpanScorer and SimpleSpanFragmenter for Contrib Highlighter

2007-06-05 Thread Mark Miller (JIRA)


[ 
https://issues.apache.org/jira/browse/LUCENE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501682
 ] 

Mark Miller commented on LUCENE-794:


I plan on one more release and than I am finished.

I need to optimize the scoring (stop looking at positions for terms that are 
not position sensitive)

Make a couple unit tests to check for a bug I suspect

Turn the javadoc's into something I am actually proud of.

I would wait for this final patch before taking a look at this Mark H.

I apologize for being so incremental on this issue...lesson learned.

- Mark

 SpanScorer and SimpleSpanFragmenter for Contrib Highlighter
 ---

 Key: LUCENE-794
 URL: https://issues.apache.org/jira/browse/LUCENE-794
 Project: Lucene - Java
  Issue Type: Improvement
  Components: Other
Reporter: Mark Miller
Priority: Minor
 Attachments: CachedTokenStream.java, CachedTokenStream.java, 
 CachedTokenStream.java, DefaultEncoder.java, Encoder.java, Formatter.java, 
 Highlighter.java, Highlighter.java, Highlighter.java, Highlighter.java, 
 Highlighter.java, HighlighterTest.java, HighlighterTest.java, 
 HighlighterTest.java, HighlighterTest.java, MemoryIndex.java, 
 QuerySpansExtractor.java, QuerySpansExtractor.java, QuerySpansExtractor.java, 
 QuerySpansExtractor.java, SimpleFormatter.java, spanhighlighter.patch, 
 spanhighlighter2.patch, spanhighlighter3.patch, spanhighlighter5.patch, 
 spanhighlighter6.patch, spanhighlighter7.patch, spanhighlighter_patch_4.zip, 
 SpanHighlighterTest.java, SpanHighlighterTest.java, SpanScorer.java, 
 SpanScorer.java, WeightedSpanTerm.java


 This patch adds a new Scorer class (SpanQueryScorer) to the Highlighter 
 package that scores just like QueryScorer, but scores a 0 for Terms that did 
 not cause the Query hit. This gives 'actual' hit highlighting for the range 
 of SpanQuerys and PhraseQuery. There is also a new Fragmenter that attempts 
 to fragment without breaking up Spans.
 See http://issues.apache.org/jira/browse/LUCENE-403 for some background.
 There is a dependency on MemoryIndex.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (LUCENE-908) Lucli doesn't include standard MANIFEST.MF

Lucli doesn't include standard MANIFEST.MF
--

 Key: LUCENE-908
 URL: https://issues.apache.org/jira/browse/LUCENE-908
 Project: Lucene - Java
  Issue Type: Bug
  Components: Build
Reporter: Michael Busch
Assignee: Michael Busch
Priority: Trivial
 Fix For: 2.2


Is there a particular reason why lucli has it's own MANIFEST.MF file? Lucli's 
build.xml
has an own jar target and does not use the jar target from common-build.xml. 
The result
is that the MANIFEST.MF file does not contain infos like Created-By Apache 
Lucene Java,
neither does META-INF contain LICENSE.TXT and NOTICE.TXT.

Is there a reason why lucli behaves different in this regard? If not I think we 
should fix this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Please help testing the release files

2007-06-05 Thread Michael Busch


Michael Busch wrote:


I checked on Ubuntu Linux 7.0.4 32 Bit.

With all Sun JDKs 1.4, 5.0 and 6.0:

lucene-2.2-dev.tar.gz:
 + md5: OK
 + LICENSE.TXT:  ? (see below)
 + NOTICE.TXT:  ? (see below)
 + ant clean war-demo: OK

lucene-2.2-dev-src.tar.gz:
 + md5: OK
 + ant clean test: OK


* the two files LICENSE.TXT and NOTICE.TXT are located in the META_INF 
dir
of lucene-core-2.2-dev.jar which is OK, but neither in 
lucene-demos-2.2-dev.jar, nor

in the contrib jars. I guess we have to add them to those jars as well?

I just fixed this with LUCENE-907 and uploaded new release files to the 
same location:

http://people.apache.org/~buschmi/staging_area/lucene/

lucene-2.2-dev.tar.gz:
+ LICENSE.TXT:  OK
+ NOTICE.TXT:  OK


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (LUCENE-808) bufferDeleteTerm in IndexWriter might flush prematurely


 [ 
https://issues.apache.org/jira/browse/LUCENE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Doron Cohen updated LUCENE-808:
---

Priority: Minor  (was: Major)

 bufferDeleteTerm in IndexWriter might flush prematurely
 ---

 Key: LUCENE-808
 URL: https://issues.apache.org/jira/browse/LUCENE-808
 Project: Lucene - Java
  Issue Type: Bug
  Components: Index
Affects Versions: 2.1
Reporter: Doron Cohen
Assignee: Doron Cohen
Priority: Minor
 Attachments: successive_bufferDeleteTerm.patch


 Successive calls to remove-by-the-same-term would increment 
 numBufferedDeleteTerms
 although all but the first are no op if no docs were added in between. Hence 
 deletes would
 be flushed too soon.
 It is a minor problem, should be rare, but it seems cleaner to fix this. 
 Attached patch also fixes TestIndexWriterDelete.testNonRAMDelete() which 
 somehow
 relied on this behavior.  All tests pass.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Resolved: (LUCENE-808) bufferDeleteTerm in IndexWriter might flush prematurely


 [ 
https://issues.apache.org/jira/browse/LUCENE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Doron Cohen resolved LUCENE-808.


   Resolution: Invalid
Lucene Fields: [Patch Available]  (was: [New, Patch Available])

No one else but me consider this behavior a problem, so close it.

 bufferDeleteTerm in IndexWriter might flush prematurely
 ---

 Key: LUCENE-808
 URL: https://issues.apache.org/jira/browse/LUCENE-808
 Project: Lucene - Java
  Issue Type: Bug
  Components: Index
Affects Versions: 2.1
Reporter: Doron Cohen
Assignee: Doron Cohen
Priority: Minor
 Attachments: successive_bufferDeleteTerm.patch


 Successive calls to remove-by-the-same-term would increment 
 numBufferedDeleteTerms
 although all but the first are no op if no docs were added in between. Hence 
 deletes would
 be flushed too soon.
 It is a minor problem, should be rare, but it seems cleaner to fix this. 
 Attached patch also fixes TestIndexWriterDelete.testNonRAMDelete() which 
 somehow
 relied on this behavior.  All tests pass.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (LUCENE-908) Lucli doesn't include standard MANIFEST.MF

2007-06-05 Thread Steven Parkes (JIRA)


[ 
https://issues.apache.org/jira/browse/LUCENE-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501702
 ] 

Steven Parkes commented on LUCENE-908:
--

I'm pretty sure it's to get the stuff that's in the MANIFEST.MF in there: the 
Main-Class header, in particular. With this, you can say java -jar jar w/o 
having to specify the main class.

Probably simplest just to also add the necessary files/lines manually? It's not 
DRY with the code common-build.xml, but it's simple for an uncommon case.

 Lucli doesn't include standard MANIFEST.MF
 --

 Key: LUCENE-908
 URL: https://issues.apache.org/jira/browse/LUCENE-908
 Project: Lucene - Java
  Issue Type: Bug
  Components: Build
Reporter: Michael Busch
Assignee: Michael Busch
Priority: Trivial
 Fix For: 2.2


 Is there a particular reason why lucli has it's own MANIFEST.MF file? Lucli's 
 build.xml
 has an own jar target and does not use the jar target from 
 common-build.xml. The result
 is that the MANIFEST.MF file does not contain infos like Created-By Apache 
 Lucene Java,
 neither does META-INF contain LICENSE.TXT and NOTICE.TXT.
 Is there a reason why lucli behaves different in this regard? If not I think 
 we should fix this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (LUCENE-740) Bugs in contrib/snowball/.../SnowballProgram.java - Kraaij-Pohlmann gives Index-OOB Exception

2007-06-05 Thread Steven Parkes (JIRA)


[ 
https://issues.apache.org/jira/browse/LUCENE-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501703
 ] 

Steven Parkes commented on LUCENE-740:
--

Do we want to consider this a candidate for 2.2? In any case, the license files 
in the patch could be applied, since 2.2 seems to be catching lots of those.

 Bugs in contrib/snowball/.../SnowballProgram.java - Kraaij-Pohlmann gives 
 Index-OOB Exception
 --

 Key: LUCENE-740
 URL: https://issues.apache.org/jira/browse/LUCENE-740
 Project: Lucene - Java
  Issue Type: Bug
  Components: Analysis
Affects Versions: 1.9
 Environment: linux amd64
Reporter: Andreas Kohn
Priority: Minor
 Attachments: 740-license.txt, lucene-1.9.1-SnowballProgram.java, 
 snowball.patch.txt


 (copied from mail to java-user)
 while playing with the various stemmers of Lucene(-1.9.1), I got an
 index out of bounds exception:
 lucene-1.9.1java -cp
 build/contrib/snowball/lucene-snowball-1.9.2-dev.jar
 net.sf.snowball.TestApp Kp bla.txt
 Exception in thread main java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at net.sf.snowball.TestApp.main(TestApp.java:56)
 Caused by: java.lang.StringIndexOutOfBoundsException: String index out
 of range: 11
at java.lang.StringBuffer.charAt(StringBuffer.java:303)
at 
 net.sf.snowball.SnowballProgram.find_among_b(SnowballProgram.java:270)
at net.sf.snowball.ext.KpStemmer.r_Step_4(KpStemmer.java:1122)
at net.sf.snowball.ext.KpStemmer.stem(KpStemmer.java:1997)
 This happens when executing
 lucene-1.9.1java -cp
 build/contrib/snowball/lucene-snowball-1.9.2-dev.jar
 net.sf.snowball.TestApp Kp bla.txt
 bla.txt contains just this word: 'spijsvertering'.
 After some debugging, and some tests with the original snowball
 distribution from snowball.tartarus.org, it seems that the attached
 change is needed to avoid the exception.
 (The change comes from tartarus' SnowballProgram.java)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (LUCENE-908) MANIFEST.MF cleanup (main jar and luci customizations)


[ 
https://issues.apache.org/jira/browse/LUCENE-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501713
 ] 

Michael Busch commented on LUCENE-908:
--

Hi Hoss,

I think this makes sense. It would be great if you could provide a patch here?

 MANIFEST.MF cleanup (main jar and luci customizations)
 --

 Key: LUCENE-908
 URL: https://issues.apache.org/jira/browse/LUCENE-908
 Project: Lucene - Java
  Issue Type: Bug
  Components: Build
Reporter: Michael Busch
Assignee: Michael Busch
Priority: Trivial
 Fix For: 2.2


 there are several problems with the MANIFEST.MF file used in the core jar, 
 and some inconsistencies in th luci jar:
 Lucli's build.xml has an own jar target and does not use the jar target 
 from common-build.xml. The result
 is that the MANIFEST.MF file is not consistent and the META-INF dir does not 
 contain LICENSE.TXT and NOTICE.TXT.
 Is there a reason why lucli behaves different in this regard? If not I think 
 we should fix this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (LUCENE-910) Add/change warning comments in the javadocs of Payload APIs

Add/change warning comments in the javadocs of Payload APIs
---

 Key: LUCENE-910
 URL: https://issues.apache.org/jira/browse/LUCENE-910
 Project: Lucene - Java
  Issue Type: Task
  Components: Javadocs
Reporter: Michael Busch
Assignee: Michael Busch
Priority: Trivial
 Fix For: 2.2


Since the payload API is still experimental we should change the comments
in the javadocs similar to the new search/function package.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (LUCENE-740) Bugs in contrib/snowball/.../SnowballProgram.java - Kraaij-Pohlmann gives Index-OOB Exception


[ 
https://issues.apache.org/jira/browse/LUCENE-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501718
 ] 

Michael Busch commented on LUCENE-740:
--

I think it makes sense to apply the license patch for 2.2.

I will commit it today in case there are no objections.

 Bugs in contrib/snowball/.../SnowballProgram.java - Kraaij-Pohlmann gives 
 Index-OOB Exception
 --

 Key: LUCENE-740
 URL: https://issues.apache.org/jira/browse/LUCENE-740
 Project: Lucene - Java
  Issue Type: Bug
  Components: Analysis
Affects Versions: 1.9
 Environment: linux amd64
Reporter: Andreas Kohn
Priority: Minor
 Attachments: 740-license.txt, lucene-1.9.1-SnowballProgram.java, 
 snowball.patch.txt


 (copied from mail to java-user)
 while playing with the various stemmers of Lucene(-1.9.1), I got an
 index out of bounds exception:
 lucene-1.9.1java -cp
 build/contrib/snowball/lucene-snowball-1.9.2-dev.jar
 net.sf.snowball.TestApp Kp bla.txt
 Exception in thread main java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at net.sf.snowball.TestApp.main(TestApp.java:56)
 Caused by: java.lang.StringIndexOutOfBoundsException: String index out
 of range: 11
at java.lang.StringBuffer.charAt(StringBuffer.java:303)
at 
 net.sf.snowball.SnowballProgram.find_among_b(SnowballProgram.java:270)
at net.sf.snowball.ext.KpStemmer.r_Step_4(KpStemmer.java:1122)
at net.sf.snowball.ext.KpStemmer.stem(KpStemmer.java:1997)
 This happens when executing
 lucene-1.9.1java -cp
 build/contrib/snowball/lucene-snowball-1.9.2-dev.jar
 net.sf.snowball.TestApp Kp bla.txt
 bla.txt contains just this word: 'spijsvertering'.
 After some debugging, and some tests with the original snowball
 distribution from snowball.tartarus.org, it seems that the attached
 change is needed to avoid the exception.
 (The change comes from tartarus' SnowballProgram.java)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (LUCENE-909) Demo targets for running the demo

[
https://issues.apache.org/jira/browse/LUCENE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Doron Cohen updated LUCENE-909:
---

Attachment: lucene-909.patch

The patch:

1) adds 4 targets to demo's build file:
- demo-index-html - Run html indexing demo (index the javadocs).
- demo-index-text - Run text indexing demo (index the sources of the
demo).
- demo-search-html - Run interactive search demo.
- demo-search-text - Run interactive search demo.

2) changes the search demo interactive print statements (which ask user input)
to println(), so that the request for input shows also when the demo runs from
ant (ant buffers the output until it detects eol, found no way around this).

3) fixes a minor search demo bug, so that it now exists nicely when entering an
empty query string.

Demo targets for running the demo
-

Key: LUCENE-909
URL: https://issues.apache.org/jira/browse/LUCENE-909
Project: Lucene - Java
Issue Type: Task
Reporter: Doron Cohen
Assignee: Doron Cohen
Priority: Trivial
Fix For: 2.2

Attachments: lucene-909.patch

Now that the demo build targets are working and build the jar/war, it may be
useful for users to also be able to run the demo with something like 'ant
run-demo'. This complements existing docs/demo.html.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (LUCENE-909) Demo targets for running the demo

Demo targets for running the demo
-

 Key: LUCENE-909
 URL: https://issues.apache.org/jira/browse/LUCENE-909
 Project: Lucene - Java
  Issue Type: Task
Reporter: Doron Cohen
Assignee: Doron Cohen
Priority: Trivial
 Fix For: 2.2


Now that the demo build targets are working and build the jar/war, it may be 
useful for users to also be able to run the demo with something like 'ant 
run-demo'. This complements existing docs/demo.html.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (LUCENE-908) Lucli doesn't include standard MANIFEST.MF


[ 
https://issues.apache.org/jira/browse/LUCENE-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501711
 ] 

Hoss Man commented on LUCENE-908:
-

the existing jar logic in common-build.xml could be refacotred into a macro 
with a a nested tag option so that contribs could add additional items, that 
would probably be the cleanest way to support MANIFEST.MF add ons.

on a related subject, when i was setting up the solr MANIFEST.MF i discovered 
lots of things are wrong about the way Lucene's MANIFEST file is built 
(aparently i never raised them in lucene-java, or if i did we never did anythng 
about them), here are the comments from Solr's build.xml that we may also want 
to fix...

http://svn.apache.org/viewvc/lucene/solr/trunk/build.xml
!--
http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html#JAR%20Manifest

http://java.sun.com/j2se/1.5.0/docs/guide/versioning/spec/versioning2.html
http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Package.html

http://java.sun.com/j2se/1.5.0/docs/api/java/util/jar/package-summary.html

http://java.sun.com/developer/Books/javaprogramming/JAR/basics/manifest.html
--
!-- Don't set 'Manifest-Version' it identifies the version of the
 manifest file format, and should allways be 1.0 (the default)

 Don't set 'Created-by' attribute, it's purpose is 
 to identify the version of java used to build the jar,
 which ant will do by default.

 Ant will happily override these with bogus strings if you
 tell it to, so don't.

 NOTE: we don't use section info because all of our manifest data
 applies to the entire jar/war ... no package specific info.
--
!-- spec version must match digit+{.digit+}* --
!-- impl version can be any string --








 Lucli doesn't include standard MANIFEST.MF
 --

 Key: LUCENE-908
 URL: https://issues.apache.org/jira/browse/LUCENE-908
 Project: Lucene - Java
  Issue Type: Bug
  Components: Build
Reporter: Michael Busch
Assignee: Michael Busch
Priority: Trivial
 Fix For: 2.2


 Is there a particular reason why lucli has it's own MANIFEST.MF file? Lucli's 
 build.xml
 has an own jar target and does not use the jar target from 
 common-build.xml. The result
 is that the MANIFEST.MF file does not contain infos like Created-By Apache 
 Lucene Java,
 neither does META-INF contain LICENSE.TXT and NOTICE.TXT.
 Is there a reason why lucli behaves different in this regard? If not I think 
 we should fix this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (LUCENE-908) MANIFEST.MF cleanup (main jar and luci customizations)

[
https://issues.apache.org/jira/browse/LUCENE-908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hoss Man updated LUCENE-908:

Description:
there are several problems with the MANIFEST.MF file used in the core jar, and
some inconsistencies in th luci jar:

Lucli's build.xml has an own jar target and does not use the jar target from
common-build.xml. The result
is that the MANIFEST.MF file is not consistent and the META-INF dir does not
contain LICENSE.TXT and NOTICE.TXT.

Is there a reason why lucli behaves different in this regard? If not I think we
should fix this.

was:
Is there a particular reason why lucli has it's own MANIFEST.MF file? Lucli's
build.xml
has an own jar target and does not use the jar target from common-build.xml.
The result
is that the MANIFEST.MF file does not contain infos like Created-By Apache
Lucene Java,
neither does META-INF contain LICENSE.TXT and NOTICE.TXT.

Is there a reason why lucli behaves different in this regard? If not I think we
should fix this.

Summary: MANIFEST.MF cleanup (main jar and luci customizations) (was:
Lucli doesn't include standard MANIFEST.MF)

MANIFEST.MF cleanup (main jar and luci customizations)
--

Key: LUCENE-908
URL: https://issues.apache.org/jira/browse/LUCENE-908
Project: Lucene - Java
Issue Type: Bug
Components: Build
Reporter: Michael Busch
Assignee: Michael Busch
Priority: Trivial
Fix For: 2.2

there are several problems with the MANIFEST.MF file used in the core jar,
and some inconsistencies in th luci jar:
Lucli's build.xml has an own jar target and does not use the jar target
from common-build.xml. The result
is that the MANIFEST.MF file is not consistent and the META-INF dir does not
contain LICENSE.TXT and NOTICE.TXT.
Is there a reason why lucli behaves different in this regard? If not I think
we should fix this.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (LUCENE-909) Demo targets for running the demo


[ 
https://issues.apache.org/jira/browse/LUCENE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501721
 ] 

Doron Cohen commented on LUCENE-909:


In (3) above it should be exits (not exists...)
I will commit this if there are no objections.


 Demo targets for running the demo
 -

 Key: LUCENE-909
 URL: https://issues.apache.org/jira/browse/LUCENE-909
 Project: Lucene - Java
  Issue Type: Task
Reporter: Doron Cohen
Assignee: Doron Cohen
Priority: Trivial
 Fix For: 2.2

 Attachments: lucene-909.patch


 Now that the demo build targets are working and build the jar/war, it may be 
 useful for users to also be able to run the demo with something like 'ant 
 run-demo'. This complements existing docs/demo.html.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (LUCENE-909) Demo targets for running the demo


[ 
https://issues.apache.org/jira/browse/LUCENE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501726
 ] 

Michael Busch commented on LUCENE-909:
--

I just tried it out. Works great, Doron!

+1 for committing.

Minor question: Should ant clean also remove the directories
demo-html-dir and demo-text-dir?

 Demo targets for running the demo
 -

 Key: LUCENE-909
 URL: https://issues.apache.org/jira/browse/LUCENE-909
 Project: Lucene - Java
  Issue Type: Task
Reporter: Doron Cohen
Assignee: Doron Cohen
Priority: Trivial
 Fix For: 2.2

 Attachments: lucene-909.patch


 Now that the demo build targets are working and build the jar/war, it may be 
 useful for users to also be able to run the demo with something like 'ant 
 run-demo'. This complements existing docs/demo.html.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (LUCENE-909) Demo targets for running the demo


[ 
https://issues.apache.org/jira/browse/LUCENE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501740
 ] 

Doron Cohen commented on LUCENE-909:


Good idea, I'll add that, thanks!

 Demo targets for running the demo
 -

 Key: LUCENE-909
 URL: https://issues.apache.org/jira/browse/LUCENE-909
 Project: Lucene - Java
  Issue Type: Task
Reporter: Doron Cohen
Assignee: Doron Cohen
Priority: Trivial
 Fix For: 2.2

 Attachments: lucene-909.patch


 Now that the demo build targets are working and build the jar/war, it may be 
 useful for users to also be able to run the demo with something like 'ant 
 run-demo'. This complements existing docs/demo.html.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Resolved: (LUCENE-909) Demo targets for running the demo


 [ 
https://issues.apache.org/jira/browse/LUCENE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Doron Cohen resolved LUCENE-909.


   Resolution: Fixed
Lucene Fields: [Patch Available]  (was: [Patch Available, New])

committed, including Michael's suggestion ('clean' deletes demo index dirs).

 Demo targets for running the demo
 -

 Key: LUCENE-909
 URL: https://issues.apache.org/jira/browse/LUCENE-909
 Project: Lucene - Java
  Issue Type: Task
Reporter: Doron Cohen
Assignee: Doron Cohen
Priority: Trivial
 Fix For: 2.2

 Attachments: lucene-909.patch


 Now that the demo build targets are working and build the jar/war, it may be 
 useful for users to also be able to run the demo with something like 'ant 
 run-demo'. This complements existing docs/demo.html.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Build failed in Hudson: Lucene-Nightly #111

2007-06-05 Thread hudson

See http://lucene.zones.apache.org:8080/hudson/job/Lucene-Nightly/111/

--
started
Checking out http://svn.apache.org/repos/asf/lucene/java/trunk
FATAL: null
java.lang.IndexOutOfBoundsException
at java.nio.Buffer.checkBounds(Buffer.java:454)
at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:125)
at java.nio.ByteBuffer.get(ByteBuffer.java:674)
at 
org.tmatesoft.svn.core.internal.delta.SVNDeltaReader.deflate(SVNDeltaReader.java:159)
at 
org.tmatesoft.svn.core.internal.delta.SVNDeltaReader.nextWindow(SVNDeltaReader.java:125)
at 
org.tmatesoft.svn.core.internal.io.dav.handlers.BasicDAVDeltaHandler.characters(BasicDAVDeltaHandler.java:98)
at 
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.characters(AbstractSAXParser.java:570)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanContent(XMLDocumentFragmentScannerImpl.java:1062)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1649)
at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at 
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at 
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:631)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:594)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.dispatch(HTTPRequest.java:197)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:284)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:229)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:217)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:219)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:211)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:601)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:162)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:322)
at hudson.scm.SubversionSCM$1.invoke(SubversionSCM.java:259)
at hudson.scm.SubversionSCM$1.invoke(SubversionSCM.java:247)
at hudson.FilePath.act(FilePath.java:226)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:247)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:225)
at hudson.model.AbstractProject.checkout(AbstractProject.java:281)
at 
hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:150)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:116)
at hudson.model.Run.run(Run.java:549)
at hudson.model.Build.run(Build.java:99)
at hudson.model.Executor.run(Executor.java:61)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (LUCENE-908) MANIFEST.MF cleanup (main jar and luci customizations)

[
https://issues.apache.org/jira/browse/LUCENE-908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hoss Man updated LUCENE-908:

Attachment: LUCENE-908.patch

quick pass at adopting some of the stuff i learned doing the Solr MANIFEST.MF
... i haven't tested it extensively (Michael i'm hoping you can take the ball
and run with it, i've got about a million other things going on at the moment)

note: it was a while ago when i looked into all of this MANIFEST stuff and i'm
not sure i fully understood it then, let alone now.

patch moves jaring into a new macro (jarify) ... contribs can override the
jar-core target to call jarify and override some options as well as add new
attributes to appear in the manifest file.

manifest now includes a lot more information then it did before.

things this doesn't address...
* manifest file in demo war file
* manifest file in any of gdata's jars/war (it doesn't use the
contrib-build.xml either)
* spec version must match digit+{.digit+}* ... this is true for our
official releases, but broken in our nightlies.
* need to svn remove the existing luci MANIFEST file
* should luci's Class-Path refer to the full name of the lucene core jar?

MANIFEST.MF cleanup (main jar and luci customizations)
--

Attachments: LUCENE-908.patch

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (LUCENE-848) Add supported for Wikipedia English as a corpus in the benchmarker stuff

2007-06-05 Thread Grant Ingersoll (JIRA)


[ 
https://issues.apache.org/jira/browse/LUCENE-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501760
 ] 

Grant Ingersoll commented on LUCENE-848:


OK, I applied the patch and am testing this.  I updated the build file to point 
to 
http://people.apache.org/~gsingers/wikipedia/enwiki-20070527-pages-articles.xml.bz2

 Add supported for Wikipedia English as a corpus in the benchmarker stuff
 

 Key: LUCENE-848
 URL: https://issues.apache.org/jira/browse/LUCENE-848
 Project: Lucene - Java
  Issue Type: New Feature
  Components: contrib/benchmark
Reporter: Steven Parkes
Assignee: Grant Ingersoll
Priority: Minor
 Attachments: LUCENE-848.txt, LUCENE-848.txt, LUCENE-848.txt, 
 LUCENE-848.txt, LUCENE-848.txt, LUCENE-848.txt, LUCENE-848.txt, 
 WikipediaHarvester.java, xerces.jar, xerces.jar, xml-apis.jar


 Add support for using Wikipedia for benchmarking.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [jira] Commented: (LUCENE-848) Add supported for Wikipedia English as a corpus in the benchmarker stuff

2007-06-05 Thread Steven Parkes

I am too; copying it down took most of the day for me ... 

-Original Message-
From: Grant Ingersoll (JIRA) [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 05, 2007 6:23 PM
To: java-dev@lucene.apache.org
Subject: [jira] Commented: (LUCENE-848) Add supported for Wikipedia
English as a corpus in the benchmarker stuff


[
https://issues.apache.org/jira/browse/LUCENE-848?page=com.atlassian.jira
.plugin.system.issuetabpanels:comment-tabpanel#action_12501760 ] 

Grant Ingersoll commented on LUCENE-848:


OK, I applied the patch and am testing this.  I updated the build file
to point to
http://people.apache.org/~gsingers/wikipedia/enwiki-20070527-pages-artic
les.xml.bz2

 Add supported for Wikipedia English as a corpus in the benchmarker
stuff



 Key: LUCENE-848
 URL: https://issues.apache.org/jira/browse/LUCENE-848
 Project: Lucene - Java
  Issue Type: New Feature
  Components: contrib/benchmark
Reporter: Steven Parkes
Assignee: Grant Ingersoll
Priority: Minor
 Attachments: LUCENE-848.txt, LUCENE-848.txt, LUCENE-848.txt,
LUCENE-848.txt, LUCENE-848.txt, LUCENE-848.txt, LUCENE-848.txt,
WikipediaHarvester.java, xerces.jar, xerces.jar, xml-apis.jar


 Add support for using Wikipedia for benchmarking.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
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]

[jira] Commented: (LUCENE-740) Bugs in contrib/snowball/.../SnowballProgram.java - Kraaij-Pohlmann gives Index-OOB Exception


[ 
https://issues.apache.org/jira/browse/LUCENE-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501763
 ] 

Michael Busch commented on LUCENE-740:
--

I committed the license patch. We should probably add SNOWBALL-LICENSE.TXT
to the META-INF dir of the snowball jar after LUCENE-908 is committed and the
manifests are customizable.

Thanks for the patch, Steven!

 Bugs in contrib/snowball/.../SnowballProgram.java - Kraaij-Pohlmann gives 
 Index-OOB Exception
 --

 Key: LUCENE-740
 URL: https://issues.apache.org/jira/browse/LUCENE-740
 Project: Lucene - Java
  Issue Type: Bug
  Components: Analysis
Affects Versions: 1.9
 Environment: linux amd64
Reporter: Andreas Kohn
Priority: Minor
 Attachments: 740-license.txt, lucene-1.9.1-SnowballProgram.java, 
 snowball.patch.txt


 (copied from mail to java-user)
 while playing with the various stemmers of Lucene(-1.9.1), I got an
 index out of bounds exception:
 lucene-1.9.1java -cp
 build/contrib/snowball/lucene-snowball-1.9.2-dev.jar
 net.sf.snowball.TestApp Kp bla.txt
 Exception in thread main java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at net.sf.snowball.TestApp.main(TestApp.java:56)
 Caused by: java.lang.StringIndexOutOfBoundsException: String index out
 of range: 11
at java.lang.StringBuffer.charAt(StringBuffer.java:303)
at 
 net.sf.snowball.SnowballProgram.find_among_b(SnowballProgram.java:270)
at net.sf.snowball.ext.KpStemmer.r_Step_4(KpStemmer.java:1122)
at net.sf.snowball.ext.KpStemmer.stem(KpStemmer.java:1997)
 This happens when executing
 lucene-1.9.1java -cp
 build/contrib/snowball/lucene-snowball-1.9.2-dev.jar
 net.sf.snowball.TestApp Kp bla.txt
 bla.txt contains just this word: 'spijsvertering'.
 After some debugging, and some tests with the original snowball
 distribution from snowball.tartarus.org, it seems that the attached
 change is needed to avoid the exception.
 (The change comes from tartarus' SnowballProgram.java)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (LUCENE-905) left nav of docs/index.html in dist artifacts links to hudson for javadocs

2007-06-05 Thread Grant Ingersoll (JIRA)


[ 
https://issues.apache.org/jira/browse/LUCENE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501765
 ] 

Grant Ingersoll commented on LUCENE-905:


There is an .htaccess in docs/api already to zones, so, I guess we can just 
point the top level docs back to it.

I will take care of it .

 left nav of docs/index.html in dist artifacts links to hudson for javadocs
 --

 Key: LUCENE-905
 URL: https://issues.apache.org/jira/browse/LUCENE-905
 Project: Lucene - Java
  Issue Type: Bug
  Components: Build
Reporter: Hoss Man
Priority: Minor
 Fix For: 2.2


 When building the zip or tgz release artifacts, the docs/index.html file 
 contained in that release (the starter point for people to read 
 documentation) links API Docs to 
 http://lucene.zones.apache.org:8080/hudson/job/Lucene-Nightly/javadoc/ 
 instead of to ./api/index.html (the local copy of the javadocs)
 this relates to the initial migration to hudson for the nightly builds and a 
 plan to copy the javadocs back to lucene.apache.org that wasn't considered 
 urgent since it was just for transient nightly docs, but a side affect is 
 that the release documentation also links to hudson.
 even if we don't modify the nightly build process before the 2.2 release, we 
 should update the link in the left nav in the 2.2 release branch before 
 building the final release.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (LUCENE-905) left nav of docs/index.html in dist artifacts links to hudson for javadocs

2007-06-05 Thread Grant Ingersoll (JIRA)


[ 
https://issues.apache.org/jira/browse/LUCENE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501767
 ] 

Grant Ingersoll commented on LUCENE-905:


Committed revision 544706

 left nav of docs/index.html in dist artifacts links to hudson for javadocs
 --

 Key: LUCENE-905
 URL: https://issues.apache.org/jira/browse/LUCENE-905
 Project: Lucene - Java
  Issue Type: Bug
  Components: Build
Reporter: Hoss Man
Assignee: Grant Ingersoll
Priority: Minor
 Fix For: 2.2


 When building the zip or tgz release artifacts, the docs/index.html file 
 contained in that release (the starter point for people to read 
 documentation) links API Docs to 
 http://lucene.zones.apache.org:8080/hudson/job/Lucene-Nightly/javadoc/ 
 instead of to ./api/index.html (the local copy of the javadocs)
 this relates to the initial migration to hudson for the nightly builds and a 
 plan to copy the javadocs back to lucene.apache.org that wasn't considered 
 urgent since it was just for transient nightly docs, but a side affect is 
 that the release documentation also links to hudson.
 even if we don't modify the nightly build process before the 2.2 release, we 
 should update the link in the left nav in the 2.2 release branch before 
 building the final release.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (LUCENE-905) left nav of docs/index.html in dist artifacts links to hudson for javadocs


[ 
https://issues.apache.org/jira/browse/LUCENE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501769
 ] 

Michael Busch commented on LUCENE-905:
--

Great, thanks Grant! Can we resolve this?

 left nav of docs/index.html in dist artifacts links to hudson for javadocs
 --

 Key: LUCENE-905
 URL: https://issues.apache.org/jira/browse/LUCENE-905
 Project: Lucene - Java
  Issue Type: Bug
  Components: Build
Reporter: Hoss Man
Assignee: Grant Ingersoll
Priority: Minor
 Fix For: 2.2


 When building the zip or tgz release artifacts, the docs/index.html file 
 contained in that release (the starter point for people to read 
 documentation) links API Docs to 
 http://lucene.zones.apache.org:8080/hudson/job/Lucene-Nightly/javadoc/ 
 instead of to ./api/index.html (the local copy of the javadocs)
 this relates to the initial migration to hudson for the nightly builds and a 
 plan to copy the javadocs back to lucene.apache.org that wasn't considered 
 urgent since it was just for transient nightly docs, but a side affect is 
 that the release documentation also links to hudson.
 even if we don't modify the nightly build process before the 2.2 release, we 
 should update the link in the left nav in the 2.2 release branch before 
 building the final release.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (LUCENE-910) Add/change warning comments in the javadocs of Payload APIs


 [ 
https://issues.apache.org/jira/browse/LUCENE-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Busch updated LUCENE-910:
-

Attachment: lucene-910.patch

 Add/change warning comments in the javadocs of Payload APIs
 ---

 Key: LUCENE-910
 URL: https://issues.apache.org/jira/browse/LUCENE-910
 Project: Lucene - Java
  Issue Type: Task
  Components: Javadocs
Reporter: Michael Busch
Assignee: Michael Busch
Priority: Trivial
 Fix For: 2.2

 Attachments: lucene-910.patch


 Since the payload API is still experimental we should change the comments
 in the javadocs similar to the new search/function package.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Resolved: (LUCENE-910) Add/change warning comments in the javadocs of Payload APIs


 [ 
https://issues.apache.org/jira/browse/LUCENE-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Busch resolved LUCENE-910.
--

Resolution: Fixed

Committed.

 Add/change warning comments in the javadocs of Payload APIs
 ---

 Key: LUCENE-910
 URL: https://issues.apache.org/jira/browse/LUCENE-910
 Project: Lucene - Java
  Issue Type: Task
  Components: Javadocs
Reporter: Michael Busch
Assignee: Michael Busch
Priority: Trivial
 Fix For: 2.2

 Attachments: lucene-910.patch


 Since the payload API is still experimental we should change the comments
 in the javadocs similar to the new search/function package.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (LUCENE-911) how to compress lucene records

2007-06-05 Thread Sebastin Naveen (JIRA)

how to compress lucene records
--

 Key: LUCENE-911
 URL: https://issues.apache.org/jira/browse/LUCENE-911
 Project: Lucene - Java
  Issue Type: Bug
  Components: Index
Affects Versions: 2.0.0
 Environment: windows/linux
Reporter: Sebastin Naveen
Priority: Critical


hi all,
i compress 4.53 mb records the index store exceeds to 8 mb is there any 
possibility to decrease the size of the lucene

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Resolved: (LUCENE-911) how to compress lucene records


 [ 
https://issues.apache.org/jira/browse/LUCENE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hoss Man resolved LUCENE-911.
-

Resolution: Invalid

if you have questions about using lucene, please post them to the lucene users 
mailing list.

http://lucene.apache.org/java/docs/mailinglists.html

do not open a Jira issue just to ask a question -- Jira is for tracking 
verified bugs and or new feature develpment

 how to compress lucene records
 --

 Key: LUCENE-911
 URL: https://issues.apache.org/jira/browse/LUCENE-911
 Project: Lucene - Java
  Issue Type: Bug
  Components: Index
Affects Versions: 2.0.0
 Environment: windows/linux
Reporter: Sebastin Naveen
Priority: Critical

 hi all,
 i compress 4.53 mb records the index store exceeds to 8 mb is there 
 any possibility to decrease the size of the lucene

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (LUCENE-908) MANIFEST.MF cleanup (main jar and luci customizations)