Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Date: Tue, 1 Jun 2010 15:16:14 -0700 (PDT)
From: Chris Hostetter <hossman_lucene@fucit.org>
To: solr-user@lucene.apache.org
Subject: Re: wrong lucene package in solr trunk?
In-Reply-To: <4C051839.5030901@iais.fraunhofer.de>
Message-ID: <alpine.DEB.1.10.1006011511290.23503@radix.cryptio.net>
References: <4C051839.5030901@iais.fraunhofer.de>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


: In order to use the current trunk version of solr, I built it running
: "ant package" in trunk/solr and added the resulting maven artifacts to
: my project.

the trunk is definitley in flux now with the way Lucene & solr (and the 
new "modules" directory) are all designed to be built as one monolithic 
release.

ultimatley it should be possible to build the individual pieces seperately 
9and to a large extent you can already do that) but it doesn't suprise me 
at all that the POMs don't make sense at the moment.

Bottom line: your best bet for right now if you want to build from source, 
is to check out hte full Lucene trunk 
(https://svn.apache.org/repos/asf/lucene/dev/trunk/) instead of just Solr, 
and build at the top level -- using all hte jars produced instead of 
trusting that any of hte POMs will be correct.  

(The simple fact is even if the POMs were correct, because it's all one 
trunk now the Solr POMs would refer to Lucene jars that don't exist in any 
repository - because they are all compiled at once)


-Hoss