[ https://issues.apache.org/jira/browse/LUCENE-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Rowe updated LUCENE-2611: -------------------------------- Attachment: LUCENE-2611_intellij_fix_codestyle.patch David, I made a couple of changes: # I got rid of the global code style file. I don't see the point in maintaining two copies of the same file (except for the name). People who want a global code style can likely manage conversion of the per-project code style file. # I simplified the {{idea}} target in the top-level {{build.xml}} and got rid of vestigial environment and platform variables that were there to support per-platform global style file installation instructions. Committing shortly. > 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_intellij_fix_codestyle.patch, > LUCENE-2611_intellij_fix_codestyle.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