You're right. So I think it's better to remove that last paragraph all together. People will naturally FIRST read README.txt and then SYSTEM_REQUIREMENTS.txt. I'll commit this to trunk, 4.x and 4.2 if ok.
diff --git a/solr/SYSTEM_REQUIREMENTS.txt b/solr/SYSTEM_REQUIREMENTS.txt index f06ce37..35da7ff 100644 --- a/solr/SYSTEM_REQUIREMENTS.txt +++ b/solr/SYSTEM_REQUIREMENTS.txt @@ -11,6 +11,3 @@ CPU, disk and memory requirements are based on the many choices made in implementing Solr (document size, number of documents, and number of hits retrieved to name a few). The benchmarks page has some information related to performance on particular platforms. - -*To build Apache Solr from source, refer to the `BUILD.txt` file in -the distribution directory.* -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com Solr Training - www.solrtraining.com 21. mars 2013 kl. 00:05 skrev Steve Rowe <[email protected]>: > solr/README.txt has a little bit of info, maybe just enough, since it says to > look at the output of running "ant" in the solr/ directory; this is probably > better than trying to keep a separate doc in sync with the build. > > So maybe just s/BUILD.txt/README.txt/? > > Steve > > On Mar 20, 2013, at 7:00 PM, Jan Høydahl <[email protected]> wrote: > >> Regarding this, we don't have a solr/BUILD.txt file, even if >> solr/SYSTEM_REQUIREMENTS.txt refers to one: >> >> "*To build Apache Solr from source, refer to the `BUILD.txt` file in the >> distribution directory.* " >> >> So should we create a BUILD.txt for solr or perhaps remove the reference >> from SYSTEM_REQUIREMENTS.txt? >> >> -- >> Jan Høydahl, search solution architect >> Cominvent AS - www.cominvent.com >> Solr Training - www.solrtraining.com >> >> 20. mars 2013 kl. 23:55 skrev Steve Rowe <[email protected]>: >> >>> Hi kamaci, >>> >>> See the README.txt file in the top-level directory of the project, and also >>> solr/README.txt, which tells you how to run Solr. >>> >>> Ant+Ivy is the official build system, so you should get comfortable using >>> it. >>> >>> See also <http://wiki.apache.org/solr/HowToContribute>. >>> >>> I use IntelliJ, and I maintain the "ant idea" target that produces an >>> IntelliJ project. See >>> <http://wiki.apache.org/lucene-java/HowtoConfigureIntelliJ> for more info. >>> >>> I also use Maven, and I maintain the "ant get-maven-poms" target that >>> produces a Maven build in a top-level "maven-build/" directory - see >>> dev-tools/maven/README.maven for more info. This is not an officially >>> supported build, but it should work for most basic things. >>> >>> Good luck, and welcome! >>> >>> Steve >>> >>> On Mar 20, 2013, at 6:43 PM, kamaci <[email protected]> wrote: >>> >>>> I want to extend Solr and forked it from github. I want to develop on it at >>>> Intellij IDEA. I opened the project however there are many modules and I >>>> don't know which one is the main module and how can I run it? Also is there >>>> any problem to use it as Maven project or it is not supported and I should >>>> use Ant + Ivy instead? >>>> >>>> >>>> >>>> -- >>>> View this message in context: >>>> http://lucene.472066.n3.nabble.com/How-to-Run-Solr-Within-Intellij-IDEA-tp4049563.html >>>> Sent from the Lucene - Java Developer mailing list archive at Nabble.com. >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
