[
https://issues.apache.org/jira/browse/LUCENE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560948#action_12560948
]
Michele Bini commented on LUCENE-472:
-------------------------------------
Michael,
committing it's obviously yor decision and you certainly have a better point of
view of lucene release process than I have but please note that changes in the
java files are mostly syntactic and the non-syntactic one (in
lucene/index/DocumentsWriter.java) looks quite safe anyway.
That said, I was naive in my patch submission (more or less, I put it in JIRA 2
years ago and forgot about it :) ) but I'm interested in having a lucente 2.4.x
which actually works on gcj.
As I currently understand, the 2.4.x branch will be left in bug fix mode but
not completely discontinued, so I can adapt the patch for inclusion in the
2.4.x branch post 2.4.0.
Would this be a reasonable plan?
> Some fixes to let gcj build lucene using ant gcj target
> -------------------------------------------------------
>
> Key: LUCENE-472
> URL: https://issues.apache.org/jira/browse/LUCENE-472
> Project: Lucene - Java
> Issue Type: Bug
> Affects Versions: CVS Nightly - Specify date in submission
> Reporter: Michele Bini
> Priority: Minor
> Attachments: gcj-build.diff
>
>
> I'm attaching a patch that fixes two problems with the gcj build.
> First, some imports in lucene.search.FieldCacheImpl.java that gcj requires
> but jdk doesn't were missing.
> Second, the Makefile uses the wrong name for the lucene-core .jar file.
--
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]
