You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Rowe (JIRA)" <ji...@apache.org> on 2014/09/10 07:57:28 UTC
[jira] [Comment Edited] (LUCENE-5930) Change intellij setup to have
1 module per lucene module instead of 3
[ https://issues.apache.org/jira/browse/LUCENE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14128111#comment-14128111 ]
Steve Rowe edited comment on LUCENE-5930 at 9/10/14 5:56 AM:
-------------------------------------------------------------
LUCENE-4367 is where I added the extra test modules for lucene-core, lucene-codecs, solr-core and solr-solrj, because any module that uses the lucene or solr test-framework module makes (or made, anyway) IntelliJ think there was a circular dependency. See the images I put up on the Maven version of that issue (LUCENE-4365) that show the situation [before|https://issues.apache.org/jira/secure/attachment/12543942/lucene.solr.dependency.cycles.png.jpg] and [after|https://issues.apache.org/jira/secure/attachment/12543981/lucene.solr.cyclic.dependencies.removed.png].
Maybe IntelliJ is smarter now (IntelliJ v9 or v10 when LUCENE-4367 was put in place; v13 now and v14 EAP is available) about the difference between test and compile scope dependencies? It's worth trying.
IIRC, some modules have (test-)resource-only fake modules in order to copy over resources or something like that.
bq. I also think we should try grouping modules? That would make it a lot less cumbersome to navigate.
http://www.jetbrains.com/idea/webhelp/grouping-modules.html
+1
was (Author: steve_rowe):
LUCENE-4367 is where I added the extra test modules for lucene-core, lucene-codecs, solr-core and solr-solrj, because any module that uses the lucene or solr test-framework module makes (or made, anyway) IntelliJ think there was a circular dependency. See the images I put up on the Maven version of that issue (LUCENE-4365) that show the situation [before|https://issues.apache.org/jira/secure/attachment/12543942/lucene.solr.dependency.cycles.png.jpg]and [after|https://issues.apache.org/jira/secure/attachment/12543981/lucene.solr.cyclic.dependencies.removed.png].
Maybe IntelliJ is smarter now (IntelliJ v9 or v10 when LUCENE-4367 was put in place; v13 now and v14 EAP is available) about the difference between test and compile scope dependencies? It's worth trying.
IIRC, some modules have (test-)resource-only fake modules in order to copy over resources or something like that.
bq. I also think we should try grouping modules? That would make it a lot less cumbersome to navigate.
http://www.jetbrains.com/idea/webhelp/grouping-modules.html
+1
> Change intellij setup to have 1 module per lucene module instead of 3
> ---------------------------------------------------------------------
>
> Key: LUCENE-5930
> URL: https://issues.apache.org/jira/browse/LUCENE-5930
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Ryan Ernst
>
> The number of intellij modules is getting out of hand. Intellij supports marking subdirectories within a module as source/resources/tests/test-resources. I think we should consolidate these modules so we have just one per lucene module. Is there some reason I'm missing that this was not done in the first place?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org