Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 0.10.6
-
Component/s: None
-
Labels:None
Description
Trying to fix CHEF-2346 but illustrating my change is difficult due to the configs being packed in chef-solr/solr/solr-home.tar.gz and chef-solr/solr/solr-jetty.tar.gz.
Issue Links
- is duplicated by
-
CHEF-2973
undefined method `collect' in check_server_side_cookbooks
-
Activity
Matthew Kent
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Fix Version/s | 0.10.6 [ 10403 ] | |
| Resolution | Fixed [ 1 ] |
Bryan McLellan [Opscode]
made changes -
| Triage Status | [Triaged] |
Bryan McLellan [Opscode]
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |
Matthew Kent
made changes -
| Resolution | Fixed [ 1 ] | |
| Status | Closed [ 6 ] | Reopened [ 4 ] |
Matthew Kent
made changes -
| Status | Reopened [ 4 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Daniel DeLeo
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |
Bryan McLellan [Opscode]
made changes -
Bryan McLellan [Opscode]
made changes -
| Workflow | jira [ 14210 ] | New OSS [ 20180 ] |
Bryan McLellan [Opscode]
made changes -
| Workflow | New OSS [ 20180 ] | OSS: Product Management [ 28094 ] |
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
1h 44m | 1 | Matthew Kent | 17/Aug/11 7:19 PM | |||||
|
3d 16h 36m | 1 | Matthew Kent | 14/Oct/11 3:14 PM | |||||
|
9s | 1 | Matthew Kent | 14/Oct/11 3:14 PM | |||||
|
66d 9h 2m | 2 | Daniel DeLeo | 26/Oct/11 8:59 PM |
Proposed solution in https://github.com/mdkent/chef/commits/CHEF-2553
Took the approach of creating a tar_solr rake task that's a prerequisite to rake gem (and thus rake package). I dropped the files from the gemspec and add them dynamically.
One issue I see with this approach is that gem build chef-solr.gemspec won't produce a complete package as it's not using rake. Not sure about the idea of putting ruby in the gemspec but it could bail out if $0 == "gem" or otherwise produce a warning. Still seems an improvement over the current situation though.