[
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-part2.patch
After Robert's changes from SOLR-2299 to allow Eclipse to run all Lucene/Solr
tests, the IntelliJ config in {{dev-tools/}} is out of sync. This patch fixes
that by moving {{solr/src/test/test-files/}} to {{solr/src/test-files/}}, so
that IntelliJ can specify {{solr/src/test-files/}} as a content root (IntelliJ
doesn't allow nested content roots, and {{solr/src/test/}} is already a content
root) -- otherwise, {{test-files/}} is copied over to the build directory,
rather than just its contents.
{{solr/contrib/analysis-extras/src/test/test-files/}} is also moved up one
level in the same fashion.
This patch doesn't contain the Subversion move operations - first run {{svn mv
solr/src/test/test-files solr/src/ ; svn mv
solr/contrib/analysis-extras/src/test/test-files
solr/contrib/analysis-extras/src/}}, then apply the patch.
The patch also fixes up the Eclipse configuration in {{dev-tools/eclipse/}}.
The patch also sets the Java language level on all Solr modules to 6.0. (The
default language level is 5.0.)
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.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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
