[ https://issues.apache.org/jira/browse/LUCENE-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998435#comment-12998435 ]
David Smiley commented on LUCENE-2611: -------------------------------------- Steven, I think the IntelliJ IDEA configuration should use a project code-style. One of the things that annoys me about IntelliJ's code style configuration screen is that it's confusing--it kind of suggests that you can configure your project to point to an IDE-wide named code style. But you can't. There's a global style in effect, and you can switch among them by name, and there's your project's code style which is optional. I don't want to have to bring up this dialog, switch to the lucene code-style, then click the "copy to project" button. This will stream-line the setup too, since you don't need to create an global named code style, which isn't very useful. > IntelliJ IDEA and Eclipse setup > ------------------------------- > > Key: LUCENE-2611 > URL: https://issues.apache.org/jira/browse/LUCENE-2611 > Project: Lucene - Java > Issue Type: New Feature > Components: Build > Affects Versions: 3.1, 4.0 > Reporter: Steven Rowe > Priority: Minor > Fix For: 3.1, 4.0 > > Attachments: LUCENE-2611-branch-3x-part2.patch, > LUCENE-2611-branch-3x.patch, LUCENE-2611-branch-3x.patch, > LUCENE-2611-branch-3x.patch, LUCENE-2611-branch-3x.patch, > LUCENE-2611-branch-3x.patch, LUCENE-2611-part2.patch, LUCENE-2611.patch, > LUCENE-2611.patch, LUCENE-2611.patch, LUCENE-2611.patch, LUCENE-2611.patch, > LUCENE-2611.patch, LUCENE-2611.patch, LUCENE-2611.patch, > LUCENE-2611_eclipse.patch, LUCENE-2611_mkdir.patch, LUCENE-2611_test.patch, > LUCENE-2611_test.patch, LUCENE-2611_test.patch, LUCENE-2611_test.patch, > LUCENE-2611_test_2.patch, utf8.patch > > > Setting up Lucene/Solr in IntelliJ IDEA or Eclipse can be time-consuming. > The attached patches add a new top level directory {{dev-tools/}} with > sub-dirs {{idea/}} and {{eclipse/}} containing basic setup files for trunk, > as well as top-level ant targets named "idea" and "eclipse" that copy these > files into the proper locations. This arrangement avoids the messiness > attendant to in-place project configuration files directly checked into > source control. > The IDEA configuration includes modules for Lucene and Solr, each Lucene and > Solr contrib, and each analysis module. A JUnit run configuration per module > is included. > The Eclipse configuration includes a source entry for each > source/test/resource location and classpath setup: a library entry for each > jar. > For IDEA, once {{ant idea}} has been run, the only configuration that must be > performed manually is configuring the project-level JDK. For Eclipse, once > {{ant eclipse}} has been run, the user has to refresh the project > (right-click on the project and choose Refresh). > If these patches is committed, Subversion svn:ignore properties should be > added/modified to ignore the destination IDEA and Eclipse configuration > locations. > Iam Jambour has written up on the Lucene wiki a detailed set of instructions > for applying the 3.X branch patch for IDEA: > http://wiki.apache.org/lucene-java/HowtoConfigureIntelliJ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org