There is another class of patches like this RichDocumentRequestHandler (SOLR-284) which brings in dependencies on other libraries, which can safely live as a contrib project.
Do we need to raise a jira issue to track this (contrib creation)? --Noble On Sun, May 4, 2008 at 7:22 AM, Otis Gospodnetic <[EMAIL PROTECTED]> wrote: > Hi Contributor ;) > > I think this is a good suggestion. I think Lucene's contrib/ is working OK, > so I think it's safe to follow that approach. If we observe that something > in contrib/ is *so* frequently used or very core in some way, we can svn mv > it and carry on. > > Otis > > -- > Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch > > > > ----- Original Message ---- > > From: Noble Paul നോബിള് नोब्ळ् <[EMAIL PROTECTED]> > > To: solr-dev@lucene.apache.org > > Sent: Saturday, May 3, 2008 5:30:30 PM > > Subject: contrib for solr > > > > Hi Committers, > > > > As Solr matures and the codebase grows, putting everything in the core > > will lead to a bloat. This may impact our ability to have releases > > early and often. > > > > A case in point is DataImportHandler (SOLR-469). As per our discussion > > with Grant Ingersoll, it makes a lot of sense to make this a contrib > > project rather than adding it to the core codebase. Though it adds a > > lot of value to the system, it actually makes no modifications to the > > core and works purely as a component that can be plugged in by > > configuration. > > > > Going forward, this may not be an exception (as in case of Lucene) and > > we will have more components like this. > > > > So we propose that we have a contrib area for Solr and add > > DataImportHandler to that (and any other component which may fit the > > bill). > > > > please comment > > -- > > --Noble Paul > > -- Shalin Shekhar Mangar > > > > >
