Hmm, after I hit the "Add" button for the previous comment on this issue, the issue did not include the comment I had just typed in. I thought that I had accidently hit the "Cancel" button instead of the "Add" button, so I gritted my teeth and re-entered (something like) the same comment. Sorry for the noise...
> -----Original Message----- > From: Steven Rowe (JIRA) [mailto:j...@apache.org] > Sent: Monday, August 23, 2010 2:42 AM > To: dev@lucene.apache.org > Subject: [jira] Commented: (LUCENE-2611) IntelliJ IDEA setup > > > [ https://issues.apache.org/jira/browse/LUCENE- > 2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment- > tabpanel&focusedCommentId=12901282#action_12901282 ] > > Steven Rowe commented on LUCENE-2611: > ------------------------------------- > > All compilation succeeds for me with the attached patch under IntelliJ > IDEA 9.0.3 on Windows Vista 64-bit with Java6 1.6.0_13 64-bit. > > Except for the Solr and the DIH modules, all modules' JUnit test runs > succeed for me. > > The DIH module JUnit test run succeeds if I add code to > {{TestContentStreamDataSource}} to clear the {{solr.solr.home}} property > in {{tearDown()}}. Without this code, the {{solr.solr.home}} property > setting introduced in leaks into following JUnit tests and cause the > resource loader to look in the wrong place. (The attached patch does not > contain the property clearing code, since I wasn't sure that was the right > way to go.) > > The Solr module JUnit test run shares the {{solr.solr.home}} leakage > problem, at a minimum in {{TestSolrCoreProperties}}, and likely in other > tests too. However, I didn't track down all of those problems because I > got a bunch of failures related to refused connections and HTTP 500 > errors. These may be because my firewall settings don't allow these > connections, but I haven't tracked the problem(s) down yet, so I'm not > sure. > > I plan on making another patch with a similar setup for the 3.X branch. > > > IntelliJ IDEA setup > > ------------------- > > > > Key: LUCENE-2611 > > URL: https://issues.apache.org/jira/browse/LUCENE-2611 > > Project: Lucene - Java > > Issue Type: New Feature > > Components: Build > > Affects Versions: 4.0 > > Reporter: Steven Rowe > > Priority: Minor > > Fix For: 4.0 > > > > Attachments: LUCENE-2611.patch > > > > > > 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. > > -- > 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
