[jira] [Commented] (LUCENE-5249) All Lucene/Solr modules should use the same dependency versions

2013-10-04 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13786467#comment-13786467
 ] 

ASF subversion and git services commented on LUCENE-5249:
-

Commit 1529250 from [~steve_rowe] in branch 'dev/branches/branch_4x'
[ https://svn.apache.org/r1529250 ]

LUCENE-5257: merge CHANGES.txt entry with LUCENE-5249's entry (merged trunk 
r1529249)

 All Lucene/Solr modules should use the same dependency versions
 ---

 Key: LUCENE-5249
 URL: https://issues.apache.org/jira/browse/LUCENE-5249
 Project: Lucene - Core
  Issue Type: Improvement
  Components: general/build
Reporter: Steve Rowe
Assignee: Steve Rowe
Priority: Minor
 Fix For: 5.0, 4.6

 Attachments: LUCENE-5162.patch


 [~markrmil...@gmail.com] wrote on the dev list:
 {quote}
 I'd like it for some things if we actually kept the versions somewhere else - 
 for instance, Hadoop dependencies should match across the mr module and the 
 core module.
 Perhaps we could define versions for dependencies across multiple modules 
 that should probably match, in a prop file or ant file and use sys sub for 
 them in the ivy files.
 For something like Hadoop, that would also make it simple to use Hadoop 1 
 rather than 2 with a single sys prop override. Same with some other 
 depenencies.
 {quote}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

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



[jira] [Commented] (LUCENE-5249) All Lucene/Solr modules should use the same dependency versions

2013-10-04 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13786464#comment-13786464
 ] 

ASF subversion and git services commented on LUCENE-5249:
-

Commit 1529249 from [~steve_rowe] in branch 'dev/trunk'
[ https://svn.apache.org/r1529249 ]

LUCENE-5257: merge CHANGES.txt entry with LUCENE-5249's entry

 All Lucene/Solr modules should use the same dependency versions
 ---

 Key: LUCENE-5249
 URL: https://issues.apache.org/jira/browse/LUCENE-5249
 Project: Lucene - Core
  Issue Type: Improvement
  Components: general/build
Reporter: Steve Rowe
Assignee: Steve Rowe
Priority: Minor
 Fix For: 5.0, 4.6

 Attachments: LUCENE-5162.patch


 [~markrmil...@gmail.com] wrote on the dev list:
 {quote}
 I'd like it for some things if we actually kept the versions somewhere else - 
 for instance, Hadoop dependencies should match across the mr module and the 
 core module.
 Perhaps we could define versions for dependencies across multiple modules 
 that should probably match, in a prop file or ant file and use sys sub for 
 them in the ivy files.
 For something like Hadoop, that would also make it simple to use Hadoop 1 
 rather than 2 with a single sys prop override. Same with some other 
 depenencies.
 {quote}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

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



[jira] [Commented] (LUCENE-5249) All Lucene/Solr modules should use the same dependency versions

2013-10-01 Thread Robert Muir (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13783156#comment-13783156
 ] 

Robert Muir commented on LUCENE-5249:
-

+1 I like it, seems like it would prevent lots of mistakes

 All Lucene/Solr modules should use the same dependency versions
 ---

 Key: LUCENE-5249
 URL: https://issues.apache.org/jira/browse/LUCENE-5249
 Project: Lucene - Core
  Issue Type: Improvement
  Components: general/build
Reporter: Steve Rowe
Assignee: Steve Rowe
Priority: Minor
 Attachments: LUCENE-5162.patch


 [~markrmil...@gmail.com] wrote on the dev list:
 {quote}
 I'd like it for some things if we actually kept the versions somewhere else - 
 for instance, Hadoop dependencies should match across the mr module and the 
 core module.
 Perhaps we could define versions for dependencies across multiple modules 
 that should probably match, in a prop file or ant file and use sys sub for 
 them in the ivy files.
 For something like Hadoop, that would also make it simple to use Hadoop 1 
 rather than 2 with a single sys prop override. Same with some other 
 depenencies.
 {quote}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

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



[jira] [Commented] (LUCENE-5249) All Lucene/Solr modules should use the same dependency versions

2013-10-01 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13783337#comment-13783337
 ] 

ASF subversion and git services commented on LUCENE-5249:
-

Commit 1528215 from [~steve_rowe] in branch 'dev/trunk'
[ https://svn.apache.org/r1528215 ]

LUCENE-5249: All Lucene/Solr modules should use the same dependency versions

 All Lucene/Solr modules should use the same dependency versions
 ---

 Key: LUCENE-5249
 URL: https://issues.apache.org/jira/browse/LUCENE-5249
 Project: Lucene - Core
  Issue Type: Improvement
  Components: general/build
Reporter: Steve Rowe
Assignee: Steve Rowe
Priority: Minor
 Attachments: LUCENE-5162.patch


 [~markrmil...@gmail.com] wrote on the dev list:
 {quote}
 I'd like it for some things if we actually kept the versions somewhere else - 
 for instance, Hadoop dependencies should match across the mr module and the 
 core module.
 Perhaps we could define versions for dependencies across multiple modules 
 that should probably match, in a prop file or ant file and use sys sub for 
 them in the ivy files.
 For something like Hadoop, that would also make it simple to use Hadoop 1 
 rather than 2 with a single sys prop override. Same with some other 
 depenencies.
 {quote}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

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



[jira] [Commented] (LUCENE-5249) All Lucene/Solr modules should use the same dependency versions

2013-10-01 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13783377#comment-13783377
 ] 

ASF subversion and git services commented on LUCENE-5249:
-

Commit 1528222 from [~steve_rowe] in branch 'dev/branches/branch_4x'
[ https://svn.apache.org/r1528222 ]

LUCENE-5249: All Lucene/Solr modules should use the same dependency versions 
(merged trunk r1528215)

 All Lucene/Solr modules should use the same dependency versions
 ---

 Key: LUCENE-5249
 URL: https://issues.apache.org/jira/browse/LUCENE-5249
 Project: Lucene - Core
  Issue Type: Improvement
  Components: general/build
Reporter: Steve Rowe
Assignee: Steve Rowe
Priority: Minor
 Attachments: LUCENE-5162.patch


 [~markrmil...@gmail.com] wrote on the dev list:
 {quote}
 I'd like it for some things if we actually kept the versions somewhere else - 
 for instance, Hadoop dependencies should match across the mr module and the 
 core module.
 Perhaps we could define versions for dependencies across multiple modules 
 that should probably match, in a prop file or ant file and use sys sub for 
 them in the ivy files.
 For something like Hadoop, that would also make it simple to use Hadoop 1 
 rather than 2 with a single sys prop override. Same with some other 
 depenencies.
 {quote}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

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