[
https://issues.apache.org/jira/browse/LUCENE-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970946#action_12970946
]
Steven Rowe commented on LUCENE-2611:
-------------------------------------
{quote}
The input .iml file that comes from the patch has a path like so for the
benchmark contrib module (as an example):
<output url="file://$MODULE_DIR$/../../build/contrib/benchmark/classes/java" />
And after IntelliJ reads this project and saves its files, this is re-written
to:
<output
url="file://$SmileyDev$/Projects/Projects-External/lucene-solr_trunk/lucene/build/contrib/benchmark/classes/java"
/>
Obviously the path as given in the patch could be simplified to not needlessly
use "../" and I'm pretty sure then that IntelliJ will not rewrite it.
{quote}
Not sure why we see different behavior, but on my systems (Windows 7 and
Vista), IntelliJ does *not* rewrite to absolute paths. In fact, IntelliJ will
generate the {{$MODULE_DIR$/../}} style output paths when you create new
modules that output to non-descendant directories.
bq. I wonder if several .iml files can be in the same directory but their
so-called "content-roots" would be set to where they are now?
I'm pretty sure IntelliJ allows only one .iml per directory.
bq. Or, do away with module-specific build output directories and have them
inherit the project level. Yes, this means the output directory is then
inconsistent with ant. That matters little to me, but I can understand others
having a difference of opinion..
I want to keep the output directories the same - I often switch between
IntelliJ (for quick turnaround dev/testing) and Ant (pre-JIRA-patch testing).
> 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: 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.patch, LUCENE-2611.patch,
> LUCENE-2611.patch, LUCENE-2611.patch, LUCENE-2611.patch, LUCENE-2611.patch,
> LUCENE-2611.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 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.
> Iam Jambour has written up on the Lucene wiki a detailed set of instructions
> for applying the 3.X branch patch:
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
