Hi, I think his question was why the morphlines contrib *source code* is in Solr at all. He argues that we could simply fetch the pre-built contrib module from Maven and not have a fork of the whole module in Solr. Indeed I also don't like it that there are 2 almost similar variants of the morphlines contrib...
Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: Shawn Heisey [mailto:apa...@elyograg.org] > Sent: Tuesday, May 12, 2015 11:59 PM > To: dev@lucene.apache.org > Subject: Re: Why morphlines code is in Solr? > > On 5/12/2015 2:14 PM, Noble Paul wrote: > > When I said jar dependency , I did not mean , that we check in the jar > > > > we use httpclient, but if you checkout lucene trunk you don't get the > > httpclient jar ,but the build process will add it to the distribution > > Doesn't that describe what happens with morphlines? The build process > adds it to the distribution. > > If I'm completely missing the point of what you're saying, I'll shut up and > let > you elaborate and discuss it with other people who know what's going on. > > Thanks, > Shawn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional > commands, e-mail: dev-h...@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
