[ 
https://issues.apache.org/jira/browse/SOLR-16540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631298#comment-17631298
 ] 

Shawn Heisey commented on SOLR-16540:
-------------------------------------

In the org.apache.solr.util.configuration package in the hadoop-auth module, I 
renamed SSLConfigurationsTest.java to HadoopAuthSSLConfigurationsTest.java 
because eclipse complained about a duplicate class name.  Is that an acceptable 
class name?  Would it be better to change the package instead?

I have this for CHANGES.txt ... is it too verbose?
{code:none}
* SOLR-16540: Fix errors when importing into eclipse.  One test class had the 
same name as another test class
  and there were three instances where a package-info.java file was included on 
a package in the test tree
  and the same package in the main source tree already had a package-info.java 
file.{code}

> Fix errors importing main and branch_9x into eclipse
> ----------------------------------------------------
>
>                 Key: SOLR-16540
>                 URL: https://issues.apache.org/jira/browse/SOLR-16540
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Build
>    Affects Versions: main (10.0), 9.2
>            Reporter: Shawn Heisey
>            Assignee: Shawn Heisey
>            Priority: Minor
>         Attachments: SOLR-16540.patch
>
>
> When creating an eclipse project using the eclipse gradle target, the 
> resulting project has errors.  One is because there is a duplicate class 
> name, the others are having package-info.java in the test code tree in 
> addition to the main code tree for the same package.
> The patch I will attach fixes the errors.  There are thousands of warnings, 
> something for another issue.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to