added a comment -
17/May/10 4:22 PM Sorry! Okay, this ends up being all confusing like.
So the goal is that the default installed development-environment configuration should point to the optionally installed app-level jetty instance. So if you just run "rake solr:marc:index_test_data" (without a RAILS_ENV, meaning default environment, "development"), it should then index the test data in your development solr instance, which should by default be the optional app-level jetty install.
This gets confusing to make the code work right and reliably, for a couple reasons.
The current default SolrMarc config uses solr.path and solrmarc.solr.war.path to be _file path_ locations of your solr. So the "default" ones need to be right for the app-level installed jetty. The problem is these obviously can't be absolute paths. They need to be relative paths. But SolrMarc insists they are relative to SolrMarc.jar, which is itself in the _plugin_.
And on top of that, these files _start out_ in the plugin, but the tempalte installer _copies_ these path-containing config files to the app. Which would potentially change the relative paths, but in fact does NOT chagne the relative paths, becuase they are STILL relative to SolrMarc.jar (as SolrMarc insists), which is still in the plugin. And when the template installer copies these config files, it _changes_ some of the paths.
Phew, so it gets really confusing making sure these paths are all right (and confusing to test too), and I clearly messed it up, somewhere in that long process things got wrong.
I will fix them. But this probably points that _something_ should be changed to make this less confusing. Either remove the filepaths and just use http ports (as erik hatcher recommends), or change solrmarc to be more flexible about where the relative paths can be relative to, or something. But that's for later, right now I'll just fix things.
I
Bug
Closed
Major
So the goal is that the default installed development-environment configuration should point to the optionally installed app-level jetty instance. So if you just run "rake solr:marc:index_test_data" (without a RAILS_ENV, meaning default environment, "development"), it should then index the test data in your development solr instance, which should by default be the optional app-level jetty install.
This gets confusing to make the code work right and reliably, for a couple reasons.
The current default SolrMarc config uses solr.path and solrmarc.solr.war.path to be _file path_ locations of your solr. So the "default" ones need to be right for the app-level installed jetty. The problem is these obviously can't be absolute paths. They need to be relative paths. But SolrMarc insists they are relative to SolrMarc.jar, which is itself in the _plugin_.
And on top of that, these files _start out_ in the plugin, but the tempalte installer _copies_ these path-containing config files to the app. Which would potentially change the relative paths, but in fact does NOT chagne the relative paths, becuase they are STILL relative to SolrMarc.jar (as SolrMarc insists), which is still in the plugin. And when the template installer copies these config files, it _changes_ some of the paths.
Phew, so it gets really confusing making sure these paths are all right (and confusing to test too), and I clearly messed it up, somewhere in that long process things got wrong.
I will fix them. But this probably points that _something_ should be changed to make this less confusing. Either remove the filepaths and just use http ports (as erik hatcher recommends), or change solrmarc to be more flexible about where the relative paths can be relative to, or something. But that's for later, right now I'll just fix things.
I