lucene-java-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Lucene-java Wiki] Trivial Update of "HowtoConfigureIntelliJ" by SteveRowe
Date Sat, 09 Jun 2012 23:13:31 GMT
Dear Wiki user,

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

The "HowtoConfigureIntelliJ" page has been changed by SteveRowe:
http://wiki.apache.org/lucene-java/HowtoConfigureIntelliJ?action=diff&rev1=20&rev2=21

  = Configure IntelliJ =
  == IntelliJ (tested with v9, v10, and v11) ==
- In Lucene/Solr `branches/lucene_solr_X_Y/` and `tags/lucene_solr_X_Y_Z` (where `X.Y` >=
3.1), `branches/branch_3x/` and `trunk/`, running '''`ant idea`''' from the command line will
populate your working copy with the configuration files IntelliJ needs to be able to compile,
test, and debug Lucene and Solr. To then open the code in IntelliJ IDEA, simply hit File->Open
Project and Choose the directory containing the checked out source (i.e. the top level directory
that contains both the lucene and solr directories.)
+ Run '''`ant idea`''' from the command line to populate your working copy with the configuration
files IntelliJ needs to be able to compile, test, and debug Lucene and Solr. To then open
the code in IntelliJ IDEA, simply hit File->Open Project and Choose the directory containing
the checked out source (i.e. the top level directory that contains both the lucene and solr
directories.)
  
  The project configuration will have:
  
-  1. An IntelliJ module for each Solr/Lucene module (Lucene and Solr core, Lucene and Solr
contribs, and `modules/*/` on trunk), with jar and inter-module dependencies defined.
+  1. An IntelliJ module for each Solr/Lucene module, with jar and inter-module dependencies
defined.
   1. A JUnit test run/debug configuration defined for each module's tests, including the
runtime directory and required JVM parameters.  All tests run and pass.  IntelliJ allows more
than one of these to run simultaneously, so you can gain some test parallelism by starting
up more than one at a time.
   1. Ant integration: from the "Run" menu, you can invoke any Ant task defined in any module's
build.xml file.
  

Mime
View raw message