[
https://issues.apache.org/jira/browse/LUCENE-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated LUCENE-2611:
---------------------------------
Attachment: LUCENE-2611_intellij_fix_codestyle.patch
This patch uses a project-specified code style. This simplified the build.xml a
little since we don't need to tell people to copy their intellij codestyle file
to a path OS-specific. I also looked carefully at the code style to ensure it
was as canonical as it should be (e.g. "use same indents = true, continuation
indent size = 4 even for groovy,java,xml), and don't need the parent scheme
name. That was a little time-consuming as I restarted IntelliJ many times to
see how it reacted to little changes. I updated the stand-alone codestyle
accordingly too... someone might want to install a global named codestyle but
it's not required.
> 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_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
