[
https://issues.apache.org/jira/browse/SOLR-14920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498169#comment-17498169
]
Kevin Risden commented on SOLR-14920:
-------------------------------------
So test-framework is being reviewed here:
https://github.com/apache/solr/pull/704 - I think this is pretty close with
some of the minor items being addressed today.
I went through solrj with a fine tooth comb:
https://github.com/apache/solr/pull/706 - [~erickerickson] I could use your
help here on specifically
"solr/solrj/src/test/org/apache/solr/client/solrj/io/stream/" where there are a
TON of changes to a few files. I excluded that path.
core probably needs to be split into test and non test - it is just too many
files to do at once - https://github.com/apache/solr/pull/705.
> Format code automatically and enforce it in Solr
> ------------------------------------------------
>
> Key: SOLR-14920
> URL: https://issues.apache.org/jira/browse/SOLR-14920
> Project: Solr
> Issue Type: Improvement
> Reporter: Erick Erickson
> Priority: Major
> Labels: codestyle, formatting
> Time Spent: 8h 50m
> Remaining Estimate: 0h
>
> See the discussion at: LUCENE-9564.
> This is a placeholder for the present, I'm reluctant to do this to the Solr
> code base until after:
> * we have some Solr-specific consensus
> * we have some clue what this means for the reference impl.
> Reconciling the reference impl will be difficult enough without a zillion
> format changes to add to the confusion.
> So my proposal is
> 1> do this.
> 2> Postpone this until after the reference impl is merged.
> 3> do this in one single commit for reasons like being able to conveniently
> have this separated out from git blame.
> Assigning to myself so it doesn't get lost, but anyone who wants to take it
> over please feel free.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
