Hi Stevo,
Thanks for reviewing the Maven POMs in LUCENE-2657 - I appreciate it.
In those poms, not all modules have explicit version and groupId which
is a bad practice.
Really? According to the POM best practices section in Sonatype's Maven book
: solrj http client 4
Tried to checkout lucene/solr and setup projects and classpath in eclipse
-
there seems to be circular dependency between modules - this is not
possible/allowed in maven built project, would require refactoring.
Regards,
Stevo.
On Wed, Dec 8, 2010 at 1:42 PM, Stevo Slavić
Tried to checkout lucene/solr and setup projects and classpath in eclipse -
there seems to be circular dependency between modules - this is not
possible/allowed in maven built project, would require refactoring.
Regards,
Stevo.
On Wed, Dec 8, 2010 at 1:42 PM, Stevo Slavić ssla...@gmail.com
-
From: Stevo Slavić [mailto:ssla...@gmail.com]
Sent: Wednesday, December 22, 2010 9:17 AM
To: solr-user@lucene.apache.org
Subject: Re: solrj http client 4
Tried to checkout lucene/solr and setup projects and classpath in eclipse
-
there seems to be circular dependency between modules
SOLR-2020 addresses upgrading to HttpComponents (form HttpClient). I
have had no time to work more on it, yet, though. I also don't have that
much experience with the new version, so any help is much appreciated.
Cheers,
Chantal
On Tue, 2010-12-07 at 18:35 +0100, Yonik Seeley wrote:
On Tue, Dec
OK, thanks. Can't promise anything, but would love to contribute. First
impression on the source code - ant is used as build tool, wish it was
maven. If it was maven then
https://issues.apache.org/jira/browse/SOLR-1218would be trivial or
wouldn't exist in the first place.
Regards,
Stevo.
On Wed,
