lucene-solr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Solr Wiki] Update of "HowToConfigureEclipse" by RobertMuir
Date Tue, 20 Mar 2012 09:49:57 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "HowToConfigureEclipse" page has been changed by RobertMuir:

break out eclipse configuration into its own wikipage. HowToContribute is too overwhelming
(yep, thats a bad thing)

New page:
== Eclipse (Galileo, J2EE version, but any relatively recent Eclipse should
do): ==
Checkout the trunk with subclipse (location:,
then run 'ant eclipse' and refresh your project.

=== Enabling Assertions for unit tests in Eclipse ===
By default, Eclipse does not run test with assertions enabled. This causes some tests to run
incorrectly in Eclipse and excludes some checks in the source code.

Change this by checking the box "Add '-ea' to VM arguments when creating a new JUnit launch

This checkbox is available under Windows>Preferences>Java>JUnit

== Eclipse (using Git) ==
Work has begun to maintain a Git repository with project settings. It allows a simple "File
-> Import... -> Projects from Git" workflow using EGit (version >= 0.9). Currently
it's a single Eclipse project compiling Lucene and Solr without errors. It's likely better
to have separate projects for proper dependency management. Please contribute!

The repository is available on GitHub (git:// It can
be easily kept in sync with Apache SVN using the Lucene & Solr Git mirror.

== Tips ==

 * Under some conditions, I've seen this process have thousands of compile  errors, something
like "class XXX defined in multiple places". This went  away when I highlighted the project
and clicked "refresh".
 * Think about installing the subclipse plugin, it'll allow you to update your source from
within Eclipse. See:
 * You can create patches for the committers to apply from within the IDE easily.
 * By and large, you won't "run" a Lucene program, you'll really run unit tests. (Others,
please chime in here!!!). The general development cycle for Lucene is to add functionality,
add unit tests, make sure all unit tests run and check in (actually, submit a patch to check
in, preferably attached to a JIRA issue). There's no "program" that you start up in your IDE
to test changes, just use unit tests.

Running SOLR in Eclipse: See:

View raw message