[
https://issues.apache.org/jira/browse/LUCENE-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725589#action_12725589
]
Uwe Schindler commented on LUCENE-1724:
---------------------------------------
bq. Second Step: build contrib with 1.5 JDK
Only those with 1.5, all other contribs together with core. So add something
-Djavac.target to ant, that specifies what to compile and test. If it is 1.4,
all 1.5 contribs are left out.
In my opinion, this is too late to change. After 2.9 will come 3.0 with Java
1.5 support. As noted in the mailing lists before, I would suggest, that the
release process should simply include a test-compilation with 1.4 (I think it
is noted in the Wiki, that this must be done before packaging the artifacts).
> Analysis package calls Java 1.5 API
> -----------------------------------
>
> Key: LUCENE-1724
> URL: https://issues.apache.org/jira/browse/LUCENE-1724
> 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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
