lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (JIRA)" <>
Subject [jira] [Updated] (LUCENE-4385) IntelliJ build output locations should not be the same as Ant's
Date Thu, 13 Sep 2012 22:37:08 GMT


Steven Rowe updated LUCENE-4385:

    Attachment: LUCENE-4385.patch

Patch switching IntelliJ build output directories (and test working directories) to top-level

The patch also fixes two other problems:
* {{solrj/test-files/\*\*}} weren't being copied over to the test working directory, caused
by a missing dependency from {{solrj-tests}} on {{solrj-test-files}} module.
* In benchmark module tests, the ant target used to copy {{*.alg}} files from {{benchmark/conf/}}
to the test working directory no longer works, since the Ant and IntelliJ output directories
are now different.  Created a dedicated IntelliJ module {{benchmark-conf}} to handle this
situation, similarly to the {{solrj-test-files}} and {{solr-core-test-files}} modules.  Since
IntelliJ doesn't like nested modules (except apparently the top-level module?), I moved the
benchmark module to the {{lucene/benchmark/src/}} directory, and placed the {{benchmark-conf}}
module under {{lucene/benchmark/conf/}}.

Committing shortly.
> IntelliJ build output locations should not be the same as Ant's
> ---------------------------------------------------------------
>                 Key: LUCENE-4385
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: general/build
>    Affects Versions: 5.0, 4.0
>            Reporter: Steven Rowe
>            Assignee: Steven Rowe
>            Priority: Minor
>         Attachments: LUCENE-4385.patch
> The Eclipse and Maven builds don't share their output directories with Ant.  The IntelliJ
build should follow suit and put its build output in directories dedicated to that purpose
and no other.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message