lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (LUCENE-2611) IntelliJ IDEA and Eclipse setup
Date Sun, 13 Feb 2011 20:20:57 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Smiley updated LUCENE-2611:
---------------------------------

    Attachment: utf8.patch

For some reason it was missed that javac should be invoked with "-encoding utf-8" options.
I couldn't compile most of the non-english languages when I updated my 3x branch recently.
 Attached is a patch adding this. I also included a build.xml tweak that overwrites the .iml
files... feel free to leave that out or use it if you like it.

> 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-part2.patch, 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, utf8.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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message