Nils is quite right (and you certainly do not create bin/run
yourself). Type 'mvn' to build a zip file, and then unzip that file,
everything is laid out as documented.

B.

On Sat, Jan 29, 2011 at 11:46 PM, Nils Breunese <[email protected]> wrote:
> Just follow the instructions on https://github.com/rnewson/couchdb-lucene (or 
> README.md). The instructions say:
>
> "You will now have a zip file in the target/ directory. This contains all the 
> couchdb-lucene code, dependencies, startup scripts and configuration files to 
> run couchdb-lucene."
>
> So yes, it's complete expected that running 'mvn' results in a target 
> directory. In there you'll find the zip file which has everything needed to 
> run couchdb-lucene.
>
> Nils.
> ________________________________________
> Van: Amine BENHAMZA [[email protected]]
> Verzonden: zondag 30 januari 2011 0:28
> Aan: [email protected]
> Onderwerp: Re: Basic question about couchdb-lucene
>
> Thanks Bill for your answer.
>
> I did what's being indicated: Install maven, get in directory then run
> "mvn". I got the "target" directory after the install. No additional new
> directories post install.
>
> Any clue !!!
>
> Thanks
>
>
> On 30 January 2011 00:00, Bill Barry <[email protected]> wrote:
>
>> On Sat, Jan 29, 2011 at 2:44 PM, Amine BENHAMZA
>> <[email protected]> wrote:
>> > Hello every Body,
>> >
>> > I installed couchdb-lucene 0.6.0. To run it, I have to execute ./bin/run.
>> I
>> > don't have a bin directory in the main directory. What's is the clue ?
>> >
>> > Here's a view on the directory generated by the install :
>> > @ubuntu:~/rubydev/java/couchdb-lucene$ ls
>> > BREAKING_CHANGES  couchdb-external-hook.py  LICENSE  NEWS  pom.xml
>> > README.md  src  target  THANKS.md  TODO
>>
>>
>> I have just done this myself recently so maybe I can help.   The
>> download does not include /bin/run, you must create this using the
>> instructions in the README.md file.
>>
>> Bill
>>
> ------------------------------------------------------------------------
>  VPRO   www.vpro.nl
> ------------------------------------------------------------------------
>

Reply via email to