[
https://issues.apache.org/jira/browse/SOLR-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17127036#comment-17127036
]
Jason Gerlowski commented on SOLR-14532:
----------------------------------------
I'm able to reproduce with Andras' reproduction steps. So the issue definitely
exists, at least with one set of commands.
I'm not quite sure how to interpret [~dweiss]s comment above. Dawid, are you
saying that devs really shouldn't be using {{./gradlew idea}} anymore to
generate IntelliJ configs and should instead just do a normal import-as-gradle
from the IDE? Or am I misinterpreting you there?
Even if the {{idea}} task is nearing the end of its life, it might be worth a
gitignore change still to remove this wart, unless someone's wants to remove it
as a part of this ticket.
> Add iml file to gitignore
> -------------------------
>
> Key: SOLR-14532
> URL: https://issues.apache.org/jira/browse/SOLR-14532
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Andras Salamon
> Priority: Trivial
> Attachments: SOLR-14532.patch
>
>
> If I execute {{gradlew idea}} in my {{lucene-solr-upstream}} directory, it
> will create three files in the root directory:
> {noformat}
> lucene-solr-upstream.iml
> lucene-solr-upstream.ipr
> lucene-solr-upstream.iws
> {noformat}
> Git will ignore the {{ipr}} and the {{iws}} file, but it lists the iml file
> as a new file. We should also ignore that one.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
