[
https://issues.apache.org/jira/browse/LUCENE-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-2611:
--------------------------------
Description:
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
was:
Setting up Lucene/Solr in IntelliJ IDEA can be time-consuming.
The attached patch adds a new top level directory {{dev-tools/}} with sub-dir
{{idea/}} containing basic setup files for trunk, as well as a top-level ant
target named "idea" that copies 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 test run per module is
included.
Once {{ant idea}} has been run, the only configuration that must be performed
manually is configuring the project-level JDK.
If this patch is committed, Subversion svn:ignore properties should be
added/modified to ignore the destination module files (*.iml) in each module's
directory.
Iam Jambour has written up on the Lucene wiki a detailed set of instructions
for applying the 3.X branch patch:
http://wiki.apache.org/lucene-java/HowtoConfigureIntelliJ
Summary: IntelliJ IDEA and Eclipse setup (was: IntelliJ IDEA setup)
> 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.patch,
> LUCENE-2611-branch-3x.patch, LUCENE-2611-branch-3x.patch,
> LUCENE-2611-branch-3x.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
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
