[
https://issues.apache.org/jira/browse/SOLR-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856212#action_12856212
]
Yonik Seeley commented on SOLR-1873:
------------------------------------
bq. As I wrap up the remaining work here, one issue looms: We are going to need
to move Hudson to Java 6 before this can be committed.
In most respects, I think that would be a positive anyway. Java6 is now the
primary production deployment platform for new projects (and it's new projects
that will be using new lucene and/or solr). With respect to keeping Lucene
Java5 compatible, we can always run the tests with Java5 before commits (that's
what I did in the past when Lucene was on Java1.4)
> Commit Solr Cloud to trunk
> --------------------------
>
> Key: SOLR-1873
> URL: https://issues.apache.org/jira/browse/SOLR-1873
> Project: Solr
> Issue Type: New Feature
> Affects Versions: 1.4
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 1.5
>
> Attachments: log4j-over-slf4j-1.5.5.jar, SOLR-1873.patch,
> SOLR-1873.patch, SOLR-1873.patch, SOLR-1873.patch, zookeeper-3.2.2.jar
>
>
> This is a real hassle - I didn't merge up to trunk before all the svn
> scrambling, so integrating cloud is now a bit difficult. I'm running through
> and just preparing a commit by hand though (applying changes/handling
> conflicts a file at a time).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
