Chris Hostetter wrote:
: > I'm not sure if there's any reason for solr-core to declare a maven
: > dependency on solr-solrj.
: When creating the POMs, I had (incorrectly) assumed that the core jar does
: not contain SolrJ classes, hence the dependency.
I consider it a totally justifiable assump
: > I'm not sure if there's any reason for solr-core to declare a maven
: > dependency on solr-solrj.
: When creating the POMs, I had (incorrectly) assumed that the core jar does
: not contain SolrJ classes, hence the dependency.
I consider it a totally justifiable assumption. the current packa
On Wed, Oct 29, 2008 at 9:11 PM, Chris Hostetter
<[EMAIL PROTECTED]>wrote:
>
> i believe the inclusion of solrj code in the core jar is intentional, the
> core jar is intended (as i understand it) to encapsulate everything needed
> to run "Solr" (and because of the built in distributed search feat
: 1) solr-core artifact contains org.apache.solr.client.solrj packages, and at
: the same time, the solr-core artifact depends on the solr-solrj artifact.
what you are seeing isn't specific to the maven jars, that's the way it is
in hte standard release.
i believe the inclusion of solrj code in
Hi,
About the second point, it was my mistake (source dependencies problem
in eclipse).
--
Renaud Delbru
Renaud Delbru wrote:
Hi,
I am using the Solr 1.3 mave nartifacts from [1]. It seems that these
artifacts are not correct. I have noticed that:
1) solr-core artifact contains org.apache.s
Hi,
I am using the Solr 1.3 mave nartifacts from [1]. It seems that these
artifacts are not correct. I have noticed that:
1) solr-core artifact contains org.apache.solr.client.solrj packages,
and at the same time, the solr-core artifact depends on the solr-solrj
artifact.
2) the source jar doe
