Hi Karl, That makes sense. I was misusing by checking out the whole tree. I will checkout trunk(s) now.
Thanks for the explanation. Ahmet On Thursday, April 3, 2014 5:48 PM, Karl Wright <[email protected]> wrote: Hi Ahmet, You should never be checking out the whole manifoldcf tree. You are expected to check out "trunk", or a branch, or a tag individually. As far as this slowing down svn itself -- the directories in question are in fact just pointers to versions of files kept already by lucene/solr; they are not duplicates. And, even if you delete them, svn keeps them around because it is a source-control system and nothing ever really goes away. So there would be little point in removing them at this point. It's also a standard release-engineering rule that you *never* delete tags. Karl On Thu, Apr 3, 2014 at 8:14 AM, Ahmet Arslan <[email protected]> wrote: Hi, > >Since they never released, cant we delete these four folders from svn? >They are 596 MB total and slows down svn operations? > >Ahmet > > > >On Wednesday, April 2, 2014 5:58 PM, Ahmet Arslan <[email protected]> wrote: >Hi Karl, > >Thanks for the explanation. > >Ahmet > > > > >On Wednesday, April 2, 2014 4:24 AM, Karl Wright <[email protected]> wrote: >Hi Ahmet, > >The original plan for the MCF solr plugins was that they were going to be >released as part of Lucene/Solr. But they decided not to. The tags were >from the time before they became our responsibility. > >Karl > > > >On Tue, Apr 1, 2014 at 9:02 PM, Ahmet Arslan <[email protected]> wrote: > >> Hi, >> >> I was looing at integration tags. I see source code of solr/lucene checked >> in the following tags. Is this normal? >> We have version 2.0 for solr3x and solr4x plugins. >> >> du -hs * returned following tags. >> >> manifoldcf/integration/solr-4.x/tags >> 147Mrelease-4.0-SNAPSHOT >> 147Mrelease-4.0-SNAPSHOT_V1 >> >> manifoldcf/integration/solr-3.x/tags >> >> 151Mrelease-3.5-SNAPSHOT >> 151Mrelease-3.5-SNAPSHOT_V1 >> >> Ahmet >> On Tuesday, April 1, 2014 3:41 AM, Ahmet Arslan <[email protected]> wrote: >> >> Hi Karl, >> >> I created CONNECTORS-914 to mavenize solr3x plugin. renaming directories >> created a big patch. Please take a look at it. >> >> Thanks, >> Ahmet >> >> On Monday, March 31, 2014 5:09 PM, Karl Wright <[email protected]> wrote: >> >> Please go ahead and create a ticket. Attach your proposed patch, and I'll >> have a look at it the first available time. >> >> >> FWIW, I suggest you model a maven build on the elastic search's maven >> project. That project also supports generating release candidates, which >> is essential. >> >> >> Thanks! >> Karl >> >> >> >> >> >> On Fri, Mar 28, 2014 at 9:04 PM, Ahmet Arslan <[email protected]> wrote: >> >> Hi Karl, >> > >> >I was able to build these solr-plugins by >> > >> >copy ManifoldCFQParserPlugin and ManifoldCFSearchComponent to a maven >> project. >> >copy test Mani*Test files to maven proect >> >copy solr-mcf to basedir. >> > >> >mvn package success. It doesn't need to be built as a module of >> solr/lucene >> > >> >Do you want me to create a ticket? >> >Ahmet >> > >> > >> > >> >On Saturday, March 29, 2014 2:34 AM, Karl Wright <[email protected]> >> wrote: >> >The solr plugin needs to be built as a module of solr/lucene, so the >> >build downloads the solr distribution, unpacks it, and then copies the >> >plugin code into the distribution before building it. >> > >> >Karl >> > >> >Sent from my Windows Phone >> >From: Ahmet Arslan >> >Sent: 3/28/2014 8:01 PM >> >To: dev >> >Subject: why solr plugin downloads solr distro? >> >Hi, >> > >> >For solr4x plugin why solr-4.6.1-src.tgz is dowloded into >> >integration/solr-4.x/trunk/download/solr.tgz and expanded into >> >solr-4.x/trunk/download/solr? >> > >> >There are two solr plugins here, binary dependencies(maven, ant) >> >should enough to compile these, no? >> > >> >By the way ant image yields integration/solr-4.x/trunk/build.xml:100: >> >A zip file cannot include itself on mac os. >> > >> >Thanks, >> >Ahmet >> > >> > >
