lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] Commented: (LUCENE-1724) Analysis package calls Java 1.5 API
Date Tue, 30 Jun 2009 11:44:47 GMT


Uwe Schindler commented on LUCENE-1724:

The problem is, some contribs must be build with 1.5. So you need to use at least 1.5 for
the whole build. The core and anaylsis javac are parametrized with -source and -target to
1.4 which generates 1.4 java classes out of only 1.4 compatible source code.

The problem here is, that the java compiler has no possibility to check if a *method/class*
is available in 1.4, as it only knows his own rt.jar (normally it could e.g. use the @since
javadoc tag, but this is not includedin the rt.jar and an annotation is not available). This
is a well known problem to all java developers.

> Analysis package calls Java 1.5 API
> -----------------------------------
>                 Key: LUCENE-1724
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Analysis
>            Reporter: Simon Willnauer
>            Assignee: Michael McCandless
>             Fix For: 2.9
>         Attachments: CharacterCache.patch
> I found compile errors when I tried to compile trunk with 1.4 JVM.
> org.apache.lucene.analysis.NormalizeCharMap
> org.apache.lucene.analysis.MappingCharFilter
> uses Character.valueOf() which has been added in 1.5.
> I added a CharacterCache (+ testcase) with a valueOf method as a replacement for that
quite useful method.
> org.apache.lucene.analysis.BaseTokenTestCase
> uses StringBuilder instead of the synchronized version StringBuffer (available in 1.4)
> I will attach a patch shortly.

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:
For additional commands, e-mail:

View raw message