Where would the modules live? I'm not sure if I sent it on this thread or somewhere else, but what about my proposal to have all three sitting under their own directories, w/ their own trunk/branch/tags, and if it's easier for dev then put all three under one root (for permission management maybe)?
Shai On Tue, Mar 16, 2010 at 11:53 PM, Yonik Seeley <yo...@apache.org> wrote: > On Tue, Mar 16, 2010 at 5:42 PM, Jake Mannix <jake.man...@gmail.com> > wrote: > > On Tue, Mar 16, 2010 at 2:31 PM, Michael McCandless > > <luc...@mikemccandless.com> wrote: > >> > >> If we move lucene under Solr's existing svn path, ie: > >> > >> /solr/trunk/lucene > > > > Chiming in just a bit here - isn't there any concern that independent of > > whether or not people "can" > > build lucene without checking out solr, the mere fact that Lucene will be > > effectively a "subdirectory" > > of solr... is there no concern that there will then be a perception that > Lucene is a subproject of > > Solr, instead of vice-versa? > > Who would have this perception? > Casual users will be using downloads. > > Likewise, should solr be concerned that it's currently under a lucene > URL? How many casual users actually understand the difference between > the lucene TLP and the lucene java subproject? > > This is really about what makes most sense for development. > > -Yonik > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org > >
