lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Ramsdale <>
Subject Re: Solr 1.3 Maven Artifact Problem
Date Mon, 03 Nov 2008 23:55:12 GMT
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 assumption.  the current packaging 
> (and even the current way the code is organized with common and core 
> living in src/java while core depends on clients/java/solrj and 
> clients/java/solrj depends on common) is certainly confusing and should be 
> dealt with one way or another before 1.4 ... i opened SOLR-831 as a 
> reminder for this.
> My vote would be to move anything in solrj that core depends on (is that 
> all of solrj?) into common.  something else that might be wise would be to 
> move common into it's own source directory (i'm less convinced that this 
> is neccessary, but it would certianly help eliminately the likely hood of 
> bad common->core dependencies being introduced accidently).
> -Hoss

Meanwhile, could an updated solr-core-1.3.0-sources.jar be posted that 
contains source for o.a.s.client?


View raw message