Re: IntelliJ build

2014-11-26 Thread Ramkumar R. Aiyengar
An another thing I found out after a bit of digging is that the language compliance level setting in the Project SDK had to be set at 8, else it fails compilation as we are already making use of the default methods feature. On 25 Nov 2014 03:38, david.w.smi...@gmail.com david.w.smi...@gmail.com

Re: IntelliJ build

2014-11-26 Thread Steve Rowe
David, I’d rather not go down the transitive route, because it would introduce misalignments with the Ant build, and because unwanted transitive deps could improperly influence the IntelliJ build. But if you feel strongly about it, go ahead: -0. Thanks for working on it. Steve On Nov 24

Re: IntelliJ build

2014-11-26 Thread david.w.smi...@gmail.com
misalignments with the Ant build, and because unwanted transitive deps could improperly influence the IntelliJ build. But if you feel strongly about it, go ahead: -0. Thanks for working on it. Steve On Nov 24, 2014, at 10:37 PM, david.w.smi...@gmail.com wrote: On trunk I cleaned and re

Re: IntelliJ build

2014-11-26 Thread Steve Rowe
, and because unwanted transitive deps could improperly influence the IntelliJ build. But if you feel strongly about it, go ahead: -0. Thanks for working on it. Steve On Nov 24, 2014, at 10:37 PM, david.w.smi...@gmail.com wrote: On trunk I cleaned and re-created my IntelliJ based build

IntelliJ build

2014-11-24 Thread david.w.smi...@gmail.com
On trunk I cleaned and re-created my IntelliJ based build (ant clean-idea, idea). IntelliJ didn’t get the memo about Java 8 so I changed that (locally). Then I found that the Solr velocity contrib couldn’t resolve a ResourceLoader class in analysis-common. So I simply checked the “export”

[jira] [Commented] (LUCENE-4385) IntelliJ build output locations should not be the same as Ant's

2013-03-22 Thread Commit Tag Bot (JIRA)
://svn.apache.org/viewvc?view=revisionrevision=1384601 LUCENE-4385: Move IntelliJ build output directories and test working directories to top-level directory idea-build/ (merged trunk r1384588) IntelliJ build output locations should not be the same as Ant's

[jira] [Commented] (LUCENE-4385) IntelliJ build output locations should not be the same as Ant's

2013-03-22 Thread Commit Tag Bot (JIRA)
://svn.apache.org/viewvc?view=revisionrevision=1384527 LUCENE-4385: eclipse output goes to eclipse-build instead of 'bin' for consistency with other IDEs IntelliJ build output locations should not be the same as Ant's

[jira] [Created] (LUCENE-4385) IntelliJ build output should not be the same as Ant's

2012-09-13 Thread Steven Rowe (JIRA)
Steven Rowe created LUCENE-4385: --- Summary: IntelliJ build output should not be the same as Ant's Key: LUCENE-4385 URL: https://issues.apache.org/jira/browse/LUCENE-4385 Project: Lucene - Core

[jira] [Updated] (LUCENE-4385) IntelliJ build output locations should not be the same as Ant's

2012-09-13 Thread Steven Rowe (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-4385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Rowe updated LUCENE-4385: Summary: IntelliJ build output locations should not be the same as Ant's (was: IntelliJ build

[jira] [Commented] (LUCENE-4385) IntelliJ build output locations should not be the same as Ant's

2012-09-13 Thread Robert Muir (JIRA)
on. IntelliJ build output locations should not be the same as Ant's --- Key: LUCENE-4385 URL: https://issues.apache.org/jira/browse/LUCENE-4385 Project: Lucene - Core Issue Type

[jira] [Commented] (LUCENE-4385) IntelliJ build output locations should not be the same as Ant's

2012-09-13 Thread Steven Rowe (JIRA)
possible to fix eclipse to use eclipse-build or something rather than bin/ so we know better what is going on. +1, but I don't use Eclipse, so somebody else will have to take care of this one IntelliJ build output locations should not be the same as Ant's

[jira] [Commented] (LUCENE-4385) IntelliJ build output locations should not be the same as Ant's

2012-09-13 Thread Robert Muir (JIRA)
. IntelliJ build output locations should not be the same as Ant's --- Key: LUCENE-4385 URL: https://issues.apache.org/jira/browse/LUCENE-4385 Project: Lucene - Core Issue Type

[jira] [Commented] (LUCENE-4385) IntelliJ build output locations should not be the same as Ant's

2012-09-13 Thread Robert Muir (JIRA)
: {noformat} bin.* build {noformat} IntelliJ build output locations should not be the same as Ant's --- Key: LUCENE-4385 URL: https://issues.apache.org/jira/browse/LUCENE-4385

[jira] [Commented] (LUCENE-4385) IntelliJ build output locations should not be the same as Ant's

2012-09-13 Thread Robert Muir (JIRA)
, put it in svn:ignore, and nuked bin/ from svn:ignore. IntelliJ build output locations should not be the same as Ant's --- Key: LUCENE-4385 URL: https://issues.apache.org/jira/browse

[jira] [Updated] (LUCENE-4385) IntelliJ build output locations should not be the same as Ant's

2012-09-13 Thread Steven Rowe (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-4385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Rowe updated LUCENE-4385: Attachment: LUCENE-4385.patch Patch switching IntelliJ build output directories (and test working

[jira] [Resolved] (LUCENE-4385) IntelliJ build output locations should not be the same as Ant's

2012-09-13 Thread Steven Rowe (JIRA)
Available (was: New) Committed: * trunk: [r1384588|http://svn.apache.org/viewvc?view=revrev=1384588] * branch_4x: [r1384601|http://svn.apache.org/viewvc?view=revrev=1384601] IntelliJ build output locations should not be the same as Ant's