Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4BA1C5C5.20000@holsman.net>
Date: Thu, 18 Mar 2010 17:18:45 +1100
From: Ian Holsman <lists@holsman.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: java-dev@lucene.apache.org
Subject: Re: lucene and solr trunk
References: <c68e39171003152028w36d47f46g37b52d1495ea6db4@mail.gmail.com>
    <9ac0c6aa1003161431h7b114644q2141b6221b2db6a8@mail.gmail.com>
    <4b124c311003161442t2d3d0ffeo551e9fd4cc63bcdd@mail.gmail.com>
    <c68e39171003161453m35213908xe4927f7dae427a96@mail.gmail.com>
    <4b124c311003161501v4fdd7488ga719c1ab78d69ba9@mail.gmail.com>
    <786fde51003161518i6e3030acs25f775e154edde4f@mail.gmail.com>
    <9ac0c6aa1003161547t59d9f029ga4e8b81e77c123b2@mail.gmail.com>
 <da709dd7705afd3ac780e1517c67dd42.squirrel@webmail.xs4all.nl>
 <Pine.LNX.4.64.1003171728370.5433@radix.cryptio.net>
In-Reply-To: <Pine.LNX.4.64.1003171728370.5433@radix.cryptio.net>
Content-Type: multipart/alternative;
 boundary="------------090906050700020601050904"

--------------090906050700020601050904
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

what other libraries do is have a 'core' or a 'common' bit.. which is 
what the lucene library really is.

looking at http://svn.apache.org/repos/asf/lucene/ today I see that 
nearly, but it's called 'java'.
maybe just renaming 'java' to 'core' or 'common' (hadoop uses common) 
might make sense
and let ivy or maven be responsible for pulling the other parts.

as a weekend developer, I would just pull the bit I care about, and let 
ivy or maven get the other bits for me.

btw.. having a master 'pom.xml' in 
http://svn.apache.org/repos/asf/lucene/ could just include the the 
module pom's and build them
without having to have nightly jars etc.

as for the goal of doing single commits, I've noticed that most of the 
discussion has been in the format of

/lucene/XYZ/trunk/...
and /lucene/ABC/trunk

if this is one code base, would it make sense to have it:
/lucene/trunk/ABC
/lucene/trunk/XYZ

?
On 3/18/10 11:33 AM, Chris Hostetter wrote:
> : build and nicely gets all dependencies to Lucene and Tika whenever I build
> : or release, no problem there and certainly no need to have it merged into
> : Lucene's svn!
>
> The key distinction is that Solr is allready in "Lucene's svn" -- The
> question is how reorg things in a way that makes it easier to build Solr
> and Lucene-Java all at once, while wtill making it easy to build just
> Lucene-Java.
>
> : Professionally i work on a (world-class) geocoder that also nicely depends
> : on Lucene by using maven, no problems there at all and no need to merge
> : that code in Lucene's svn!
>
> Unless maven has some features i'm not aware of, your "nicely depends"
> works buy pulling Lucene jars from a repository -- changing Solr to do
> that (instead of having committed jars) would be farrly simple (with or
> w/o maven), but that's not the goal.  The goal is to make it easy to build
> both at once, have patches that update both, and (make it easy to) have
> atomic svn commits that touch both.
>
>
> -Hoss
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
>
>    


--------------090906050700020601050904
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
what other libraries do is have a 'core' or a 'common' bit.. which is
what the lucene library really is.<br>
<br>
looking at
<meta charset="utf-8">
<a href="http://svn.apache.org/repos/asf/lucene/">http://svn.apache.org/repos/asf/lucene/</a>
today I see that nearly, but it's called 'java'.<br>
maybe just renaming 'java' to 'core' or 'common' (hadoop uses common)
might make sense<br>
and let ivy or maven be responsible for pulling the other parts.<br>
<br>
as a weekend developer, I would just pull the bit I care about, and let
ivy or maven get the other bits for me.<br>
<br>
btw.. having a master 'pom.xml' in
<meta charset="utf-8">
<a href="http://svn.apache.org/repos/asf/lucene/">http://svn.apache.org/repos/asf/lucene/</a>
could just include the the module pom's and build them<br>
without having to have nightly jars etc.<br>
<br>
as for the goal of doing single commits, I've noticed that most of the
discussion has been in the format of<br>
<br>
/lucene/XYZ/trunk/...<br>
and /lucene/ABC/trunk<br>
<br>
if this is one code base, would it make sense to have it:<br>
/lucene/trunk/ABC<br>
/lucene/trunk/XYZ<br>
<br>
?<br>
On 3/18/10 11:33 AM, Chris Hostetter wrote:
<blockquote
 cite="mid:Pine.LNX.4.64.1003171728370.5433@radix.cryptio.net"
 type="cite">
  <pre wrap="">: build and nicely gets all dependencies to Lucene and Tika whenever I build
: or release, no problem there and certainly no need to have it merged into
: Lucene's svn!

The key distinction is that Solr is allready in "Lucene's svn" -- The 
question is how reorg things in a way that makes it easier to build Solr 
and Lucene-Java all at once, while wtill making it easy to build just 
Lucene-Java.

: Professionally i work on a (world-class) geocoder that also nicely depends
: on Lucene by using maven, no problems there at all and no need to merge
: that code in Lucene's svn!

Unless maven has some features i'm not aware of, your "nicely depends" 
works buy pulling Lucene jars from a repository -- changing Solr to do 
that (instead of having committed jars) would be farrly simple (with or 
w/o maven), but that's not the goal.  The goal is to make it easy to build 
both at once, have patches that update both, and (make it easy to) have 
atomic svn commits that touch both.


-Hoss


---------------------------------------------------------------------
To unsubscribe, e-mail: <a class="moz-txt-link-abbreviated" href="mailto:java-dev-unsubscribe@lucene.apache.org">java-dev-unsubscribe@lucene.apache.org</a>
For additional commands, e-mail: <a class="moz-txt-link-abbreviated" href="mailto:java-dev-help@lucene.apache.org">java-dev-help@lucene.apache.org</a>


  </pre>
</blockquote>
<br>
</body>
</html>

--------------090906050700020601050904--