Tangentially related, but the link on the "how to contribute" page to the IntelliJ code style file is broken, it reached over into the SOLR Wiki... I stole the one from SOLR and added it as an attachment and the "how to contribute" page now links to it....
Erick On Sun, Feb 28, 2010 at 5:14 AM, Shai Erera <ser...@gmail.com> wrote: > I've read BUILD.txt and it doesn't look like it'll fit there. That files > discusses how to build Lucene using Ant and JDK. The word IDE is not > mentioned, nor Eclipse. > > BTW, there is a typo in the file "before returning to this README" - not > sure if the word README is intended to be like that, or a leftover from when > this was once in README? > > Shai > > > On Sun, Feb 28, 2010 at 12:11 PM, Uwe Schindler <u...@thetaphi.de> wrote: > >> Maybe this change is better in BUILD.txt? I am not sure. >> >> >> >> ----- >> >> Uwe Schindler >> >> H.-H.-Meier-Allee 63, D-28213 Bremen >> >> http://www.thetaphi.de >> >> eMail: u...@thetaphi.de >> >> >> >> *From:* Shai Erera [mailto:ser...@gmail.com] >> *Sent:* Sunday, February 28, 2010 10:55 AM >> >> *To:* java-dev@lucene.apache.org >> *Subject:* Re: Adding .classpath.tmpl >> >> >> >> Index: README.txt >> =================================================================== >> --- README.txt (revision 917047) >> +++ README.txt (working copy) >> @@ -28,8 +28,6 @@ >> part of the core library. Of special note are the JAR files in the >> analyzers directory which >> contain various analyzers that people may find useful in place of the >> StandardAnalyzer. >> >> - >> - >> docs/index.html >> The contents of the Lucene website. >> >> @@ -42,3 +40,10 @@ >> >> src/demo >> Some example code. >> + >> +SET UP THE ENVIRONMENT >> + >> +Checkout the HowToContribute wiki page >> +(http://wiki.apache.org/lucene-java/HowToContribute) which includes >> useful >> +information on how to contribute code to Lucene, as well as how to set up >> your >> +environment quickly (code formatting rules and setting the classpath >> quickly). >> \ No newline at end of file >> >> Is this ok? >> >> Shai >> >> On Sun, Feb 28, 2010 at 11:07 AM, Uwe Schindler <u...@thetaphi.de> wrote: >> >> I think we can add this to the README.txt! Do you have a patch? >> >> >> >> ----- >> >> Uwe Schindler >> >> H.-H.-Meier-Allee 63, D-28213 Bremen >> >> http://www.thetaphi.de >> >> eMail: u...@thetaphi.de >> >> >> >> *From:* Shai Erera [mailto:ser...@gmail.com] >> *Sent:* Sunday, February 28, 2010 6:30 AM >> *To:* java-dev@lucene.apache.org >> *Subject:* Re: Adding .classpath.tmpl >> >> >> >> I uploaded the file to >> http://wiki.apache.org/lucene-java/HowToContribute(bottom of the page). But >> I don't see any good spot to stuff it in the >> README. There is no pointer to the HowToContribute page at all, nor to the >> code formatting styles ... what do you think - create such section at the >> bottom of README, or leave it out? >> >> On Fri, Feb 26, 2010 at 2:58 PM, Shai Erera <ser...@gmail.com> wrote: >> >> Thanks for your response. I will update the Wiki with the file. After I do >> that, I'll add some text to the README file. I'll need one of you to help me >> commit it though. >> >> >> >> Thanks again, >> >> Shai >> >> >> >> On Thu, Feb 25, 2010 at 6:21 PM, Mark Miller <markrmil...@gmail.com> >> wrote: >> >> +1 - I'd prefer this stay out of svn as well - I'd rather it go on the >> wiki too - perhaps in the same place that you can find the formatting file >> for eclipse and intellij. >> >> -- >> - Mark >> >> http://www.lucidimagination.com >> >> >> >> >> >> On 02/25/2010 11:10 AM, Grant Ingersoll wrote: >> >> To me, this is stuff that can go on the wiki or somewhere else, otherwise >> over time, there will be others to add in, etc. We could simply add a >> pointer to the wiki page in the README. >> >> On Feb 24, 2010, at 11:55 PM, Shai Erera wrote: >> >> >> >> Hi >> >> I always find it annoying when I checkout the code to a new project in >> eclipse, that I need to put everything that I care about in the classpath >> and adding the dependent libraries. On another project I'm involved with, we >> did that process once, adding all the source code to the classpath and the >> libraries and created a .classpath.tmpl. Now when people checkout the code, >> they can copy the content of that file to their .classpath file and setting >> up the project is reducing from a couple of minutes to few seconds. >> >> I don't want to check-in .classpath because not everyone wants all the >> code in their classpath. >> >> I attached such file to the mail. Note that the only dependency which will >> break on other machines is the ant.jar dependency, which on my Windows is >> located under c:\ant. That jar is required to compile contrib/ant from >> eclipse. Not sure how to resolve that, except besides removing that line >> from the file and document separately that that's what you need to do if you >> want to add contrib/ant ... >> >> The file is sorted by name, putting the core stuff at the top - so it's >> easy for people to selectively add the interesting packages. >> >> I don't know if an issue is required, if so I can create it in and move >> the discussion there. >> >> Shai >> <lucene.classpath.tmpl> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: java-dev-h...@lucene.apache.org >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: java-dev-h...@lucene.apache.org >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: java-dev-h...@lucene.apache.org >> >> >> >> >> >> >> > >
