Re: Eclipse project files...
xml file or from your >> >> ivy.xml (Hadoop does that). >> >> >> >> >> >> If I put mine in c:\apache, and you put yours in c:\trunk, our >> classpath >> >>> files will reflect that. And I *really* don't want to update the >> project >> >>> and >> >>> get my classpath file overwritten with yours. >> >>> >> >>> Not to mention that I *actually* work on a mac, where Ant has been >> >>> installed in /usr and... >> >>> >> >> >> >> The examples above work on Linux, Windows and should work on Mac OS X >> as >> >> well, there are no absolute paths in the .classpath or .project files. >> >> >> >> >> >> Not to mention other libraries. And what about plugins? >> >>> >> >>> That said, one *can* include a sample classpath and, perhaps, project >> >>> file, that can be copied to "the correct place" and changed to >> reflect >> >>> the >> >>> local setup as has been done on the Wiki, see: >> >>> http://wiki.apache.org/lucene-java/HowToContribute >> >>> >> >> >> >> Eclipse .classpath and .project files can be checked into the source >> >> code repository or they can be generated as part of the building >> system. >> >> >> >> I'd love to have the same good experience with Lucene and Solr... I am >> >> still having problems trying to configure Eclipse to run Solr tests >> (and >> >> yes, I've changed the current directory... but I still have problems). >> >> >> >> Paolo >> >> >> >> >> >> Best >> >>> Erick >> >>> >> >>> On Thu, Apr 15, 2010 at 5:04 PM, hkmortensen wrote: >> >>> >> >>> I spend about two days last week to import lucene and solr in >> eclipse. >> >>> I >> >>>> would not call it easy at all. I took the test sources away >> completely >> >>>> (from >> >>>> the source path). >> >>>> >> >>>> I would like to help putting some useable project files for eclipse >> >>>> together >> >>>> (including the test files ;-) ). >> >>>> >> >>>> Why are classpath files generally not included in open source >> projects? >> >>>> Would they do any harm? I realise when you get experienced with the >> >>>> software >> >>>> you want to make it slim to make text search faster. But for new >> people >> >>>> in >> >>>> a project it would be a lot nicer, I think. >> >>>> >> >>>> Is there any way of distribute work on the solr project? I would not >> >>>> like >> >>>> to >> >>>> do a lot of effort to adapt to eclipse if somebody else does it the >> >>>> same >> >>>> time >> >>>> >> >>>> >> >>>> -- >> >>>> View this message in context: >> >>>> http://n3.nabble.com/Eclipse-project-files-tp708987p722342.html >> >>>> Sent from the Solr - Dev mailing list archive at Nabble.com. >> >>>> >> >>>> >> >>> >> > >> > >> >> -- >> View this message in context: >> http://n3.nabble.com/Eclipse-project-files-tp708987p723819.html >> Sent from the Solr - Dev mailing list archive at Nabble.com. >> > >
Re: Eclipse project files...
d to "the correct place" and changed to reflect > >>> the > >>> local setup as has been done on the Wiki, see: > >>> http://wiki.apache.org/lucene-java/HowToContribute > >>> > >> > >> Eclipse .classpath and .project files can be checked into the source > >> code repository or they can be generated as part of the building system. > >> > >> I'd love to have the same good experience with Lucene and Solr... I am > >> still having problems trying to configure Eclipse to run Solr tests (and > >> yes, I've changed the current directory... but I still have problems). > >> > >> Paolo > >> > >> > >> Best > >>> Erick > >>> > >>> On Thu, Apr 15, 2010 at 5:04 PM, hkmortensen wrote: > >>> > >>> I spend about two days last week to import lucene and solr in eclipse. > >>> I > >>>> would not call it easy at all. I took the test sources away completely > >>>> (from > >>>> the source path). > >>>> > >>>> I would like to help putting some useable project files for eclipse > >>>> together > >>>> (including the test files ;-) ). > >>>> > >>>> Why are classpath files generally not included in open source > projects? > >>>> Would they do any harm? I realise when you get experienced with the > >>>> software > >>>> you want to make it slim to make text search faster. But for new > people > >>>> in > >>>> a project it would be a lot nicer, I think. > >>>> > >>>> Is there any way of distribute work on the solr project? I would not > >>>> like > >>>> to > >>>> do a lot of effort to adapt to eclipse if somebody else does it the > >>>> same > >>>> time > >>>> > >>>> > >>>> -- > >>>> View this message in context: > >>>> http://n3.nabble.com/Eclipse-project-files-tp708987p722342.html > >>>> Sent from the Solr - Dev mailing list archive at Nabble.com. > >>>> > >>>> > >>> > > > > > > -- > View this message in context: > http://n3.nabble.com/Eclipse-project-files-tp708987p723819.html > Sent from the Solr - Dev mailing list archive at Nabble.com. >
Re: Eclipse project files...
I have always used relative paths in my (official) classpath file for eclipse, I was not aware of, that any other could make sense. It is an easy way to ensure that everybody use the same version of the libs. I see the problem with different IDEs. I dont think I volonteer, there seem to be quite many oppinions on this, and if experienced users are happy whith it it is now, then it is probably good ;-) Erick Erickson wrote: > > Well, there certainly *can* be absolute paths, it depends > on whether all your jars are relative to the checked-out > project or whether you had to go exploring your machine. > > But that's a nit. I agree it's certainly possible to carefully > construct the necessary files so that all paths are relative, > and include all the relevant jars located at those relative > path locations. > > Are you volunteering? If so, feel free to create a JIRA > and attach any patches, I'm sure one of the committers will > be happy to make it happen, assuming they approve... > > Erick > > But you're right > > On Thu, Apr 15, 2010 at 5:40 PM, Paolo Castagna < > [email protected]> wrote: > >> Erick Erickson wrote: >> >>> <<>> projects?>>> >>> >>> because they're always wrong ... >>> >> >> It is possible to get it right and when it happens users will have a >> much better experience when they checkout the sources of a project. >> >> Just a few examples of things I use: >> >> - https://jena.svn.sourceforge.net/svnroot/jena/TDB/trunk/.classpath >> - https://jena.svn.sourceforge.net/svnroot/jena/ARQ/trunk/.classpath >> - http://svn.apache.org/repos/asf/hadoop/common/trunk/build.xml >> >> With Maven and/or Ant+Ivy it's possible to generate Eclipse .classpath >> and .project files automatically from your pom.xml file or from your >> ivy.xml (Hadoop does that). >> >> >> If I put mine in c:\apache, and you put yours in c:\trunk, our classpath >>> files will reflect that. And I *really* don't want to update the project >>> and >>> get my classpath file overwritten with yours. >>> >>> Not to mention that I *actually* work on a mac, where Ant has been >>> installed in /usr and... >>> >> >> The examples above work on Linux, Windows and should work on Mac OS X as >> well, there are no absolute paths in the .classpath or .project files. >> >> >> Not to mention other libraries. And what about plugins? >>> >>> That said, one *can* include a sample classpath and, perhaps, project >>> file, that can be copied to "the correct place" and changed to reflect >>> the >>> local setup as has been done on the Wiki, see: >>> http://wiki.apache.org/lucene-java/HowToContribute >>> >> >> Eclipse .classpath and .project files can be checked into the source >> code repository or they can be generated as part of the building system. >> >> I'd love to have the same good experience with Lucene and Solr... I am >> still having problems trying to configure Eclipse to run Solr tests (and >> yes, I've changed the current directory... but I still have problems). >> >> Paolo >> >> >> Best >>> Erick >>> >>> On Thu, Apr 15, 2010 at 5:04 PM, hkmortensen wrote: >>> >>> I spend about two days last week to import lucene and solr in eclipse. >>> I >>>> would not call it easy at all. I took the test sources away completely >>>> (from >>>> the source path). >>>> >>>> I would like to help putting some useable project files for eclipse >>>> together >>>> (including the test files ;-) ). >>>> >>>> Why are classpath files generally not included in open source projects? >>>> Would they do any harm? I realise when you get experienced with the >>>> software >>>> you want to make it slim to make text search faster. But for new people >>>> in >>>> a project it would be a lot nicer, I think. >>>> >>>> Is there any way of distribute work on the solr project? I would not >>>> like >>>> to >>>> do a lot of effort to adapt to eclipse if somebody else does it the >>>> same >>>> time >>>> >>>> >>>> -- >>>> View this message in context: >>>> http://n3.nabble.com/Eclipse-project-files-tp708987p722342.html >>>> Sent from the Solr - Dev mailing list archive at Nabble.com. >>>> >>>> >>> > > -- View this message in context: http://n3.nabble.com/Eclipse-project-files-tp708987p723819.html Sent from the Solr - Dev mailing list archive at Nabble.com.
Re: Eclipse project files...
Robert Muir wrote: On Mon, Apr 12, 2010 at 5:15 AM, Paolo Castagna < [email protected]> wrote: For Lucene, I needed two more jars from Ant project: - ant-1.7.1.jar - ant-junit-1.7.1.jar Paolo, I put these in the lib directory now, to hopefully make IDE configuration easier. Thanks Robert. It's only one single class in the Lucene test suite actually needing those jars: LuceneJUnitResultFormatter. I do not normally tinker with Ant and JUnitResultSetFormatter in my tests, so I do have any suggestion. But, if someone look at LuceneJUnitResultFormatter the two jars above could go. As it is right now, they are necessary in order to run the Lucene test suite from within Eclipse. Paolo
Re: Eclipse project files...
Erick Erickson wrote: Well, there certainly *can* be absolute paths, it depends on whether all your jars are relative to the checked-out project or whether you had to go exploring your machine. I didn't said that is not possible to have absolute paths. :-) True, there certainly *can* be absolute paths, but they are not necessary and can easily be avoided. But that's a nit. I agree it's certainly possible to carefully construct the necessary files so that all paths are relative, and include all the relevant jars located at those relative path locations. +1 Are you volunteering? If so, feel free to create a JIRA and attach any patches, I'm sure one of the committers will be happy to make it happen, assuming they approve... I am curious to know what's the IDE (if any at all) is used by the majority of Lucene/Solr committers. I'll put more effort on this, if the majority of committers are using Eclipse, otherwise it will be of no value for the project. Paolo Erick But you're right
Re: Eclipse project files... and Debian
Hi Thomas, first of all, thank you for sharing your opinions (I followed your recent problems with JSON, for example :-)). I fully understand your troubles. I use Ubuntu (and therefore part of Debian). Thank you for all the good stuff you (your Thomas and the community) are doing. But, for Java artifacts, I prefer to follow other approaches which allow me to have more (or a different type of) control on dependencies. There are different "best practices", for example: - http://repo1.maven.org/maven2/ - https://repository.apache.org/content/repositories/ I think that all the effort and approaches to provide users and developers an automated and painless experience are valuable, but I prefer to use solutions which would work no matter what the operating system it is (Windows, UNIX/Linux, Mac OS X). I use Maven or Ant+Ivy or Ant+Maven. Paolo Thomas Koch wrote: Hi, there's also another kind of user with different expectations to the classpath. I'm new to the world of java and I'm kind of shocked, how binary jar files are thrown around and nobody cares, what they contain and where they came from. When I package a software for Debian, the users of Debian expect me to check the license and the security of the software. So I can not simply take whatever jar file I find in the lib/ folder. So when I develop java software, I prefer to ignore the jars in the lib/ folder and try to satisfy the dependencies with the jar files from the Debian distribution. Those are located in /usr/share/java and often have slightly different names then the original jars. But let us take our time, since Java is free only since 2006, there is still a long way, until free software developers and the java world understand each others. Best regards, Thomas Koch, http://www.koch.ro
Re: Eclipse project files... and Debian
Hi, there's also another kind of user with different expectations to the classpath. I'm new to the world of java and I'm kind of shocked, how binary jar files are thrown around and nobody cares, what they contain and where they came from. When I package a software for Debian, the users of Debian expect me to check the license and the security of the software. So I can not simply take whatever jar file I find in the lib/ folder. So when I develop java software, I prefer to ignore the jars in the lib/ folder and try to satisfy the dependencies with the jar files from the Debian distribution. Those are located in /usr/share/java and often have slightly different names then the original jars. But let us take our time, since Java is free only since 2006, there is still a long way, until free software developers and the java world understand each others. Best regards, Thomas Koch, http://www.koch.ro
Re: Eclipse project files...
Hmmm, now that I look at the rest of the thread (sorry, I just skim things at work) I see you already did provide the zips. I wonder if it would suffice to put them on the Wiki and point to them. [email protected] On Thu, Apr 15, 2010 at 7:48 PM, Erick Erickson wrote: > Well, there certainly *can* be absolute paths, it depends > on whether all your jars are relative to the checked-out > project or whether you had to go exploring your machine. > > But that's a nit. I agree it's certainly possible to carefully > construct the necessary files so that all paths are relative, > and include all the relevant jars located at those relative > path locations. > > Are you volunteering? If so, feel free to create a JIRA > and attach any patches, I'm sure one of the committers will > be happy to make it happen, assuming they approve... > > Erick > > But you're right > > > On Thu, Apr 15, 2010 at 5:40 PM, Paolo Castagna < > [email protected]> wrote: > >> Erick Erickson wrote: >> >>> <<>> projects?>>> >>> >>> because they're always wrong ... >>> >> >> It is possible to get it right and when it happens users will have a >> much better experience when they checkout the sources of a project. >> >> Just a few examples of things I use: >> >> - https://jena.svn.sourceforge.net/svnroot/jena/TDB/trunk/.classpath >> - https://jena.svn.sourceforge.net/svnroot/jena/ARQ/trunk/.classpath >> - http://svn.apache.org/repos/asf/hadoop/common/trunk/build.xml >> >> With Maven and/or Ant+Ivy it's possible to generate Eclipse .classpath >> and .project files automatically from your pom.xml file or from your >> ivy.xml (Hadoop does that). >> >> >> If I put mine in c:\apache, and you put yours in c:\trunk, our classpath >>> files will reflect that. And I *really* don't want to update the project >>> and >>> get my classpath file overwritten with yours. >>> >>> Not to mention that I *actually* work on a mac, where Ant has been >>> installed in /usr and... >>> >> >> The examples above work on Linux, Windows and should work on Mac OS X as >> well, there are no absolute paths in the .classpath or .project files. >> >> >> Not to mention other libraries. And what about plugins? >>> >>> That said, one *can* include a sample classpath and, perhaps, project >>> file, that can be copied to "the correct place" and changed to reflect >>> the >>> local setup as has been done on the Wiki, see: >>> http://wiki.apache.org/lucene-java/HowToContribute >>> >> >> Eclipse .classpath and .project files can be checked into the source >> code repository or they can be generated as part of the building system. >> >> I'd love to have the same good experience with Lucene and Solr... I am >> still having problems trying to configure Eclipse to run Solr tests (and >> yes, I've changed the current directory... but I still have problems). >> >> Paolo >> >> >> Best >>> Erick >>> >>> On Thu, Apr 15, 2010 at 5:04 PM, hkmortensen wrote: >>> >>> I spend about two days last week to import lucene and solr in eclipse. I >>>> would not call it easy at all. I took the test sources away completely >>>> (from >>>> the source path). >>>> >>>> I would like to help putting some useable project files for eclipse >>>> together >>>> (including the test files ;-) ). >>>> >>>> Why are classpath files generally not included in open source projects? >>>> Would they do any harm? I realise when you get experienced with the >>>> software >>>> you want to make it slim to make text search faster. But for new people >>>> in >>>> a project it would be a lot nicer, I think. >>>> >>>> Is there any way of distribute work on the solr project? I would not >>>> like >>>> to >>>> do a lot of effort to adapt to eclipse if somebody else does it the same >>>> time >>>> >>>> >>>> -- >>>> View this message in context: >>>> http://n3.nabble.com/Eclipse-project-files-tp708987p722342.html >>>> Sent from the Solr - Dev mailing list archive at Nabble.com. >>>> >>>> >>> >
Re: Eclipse project files...
Well, there certainly *can* be absolute paths, it depends on whether all your jars are relative to the checked-out project or whether you had to go exploring your machine. But that's a nit. I agree it's certainly possible to carefully construct the necessary files so that all paths are relative, and include all the relevant jars located at those relative path locations. Are you volunteering? If so, feel free to create a JIRA and attach any patches, I'm sure one of the committers will be happy to make it happen, assuming they approve... Erick But you're right On Thu, Apr 15, 2010 at 5:40 PM, Paolo Castagna < [email protected]> wrote: > Erick Erickson wrote: > >> <<> projects?>>> >> >> because they're always wrong ... >> > > It is possible to get it right and when it happens users will have a > much better experience when they checkout the sources of a project. > > Just a few examples of things I use: > > - https://jena.svn.sourceforge.net/svnroot/jena/TDB/trunk/.classpath > - https://jena.svn.sourceforge.net/svnroot/jena/ARQ/trunk/.classpath > - http://svn.apache.org/repos/asf/hadoop/common/trunk/build.xml > > With Maven and/or Ant+Ivy it's possible to generate Eclipse .classpath > and .project files automatically from your pom.xml file or from your > ivy.xml (Hadoop does that). > > > If I put mine in c:\apache, and you put yours in c:\trunk, our classpath >> files will reflect that. And I *really* don't want to update the project >> and >> get my classpath file overwritten with yours. >> >> Not to mention that I *actually* work on a mac, where Ant has been >> installed in /usr and... >> > > The examples above work on Linux, Windows and should work on Mac OS X as > well, there are no absolute paths in the .classpath or .project files. > > > Not to mention other libraries. And what about plugins? >> >> That said, one *can* include a sample classpath and, perhaps, project >> file, that can be copied to "the correct place" and changed to reflect >> the >> local setup as has been done on the Wiki, see: >> http://wiki.apache.org/lucene-java/HowToContribute >> > > Eclipse .classpath and .project files can be checked into the source > code repository or they can be generated as part of the building system. > > I'd love to have the same good experience with Lucene and Solr... I am > still having problems trying to configure Eclipse to run Solr tests (and > yes, I've changed the current directory... but I still have problems). > > Paolo > > > Best >> Erick >> >> On Thu, Apr 15, 2010 at 5:04 PM, hkmortensen wrote: >> >> I spend about two days last week to import lucene and solr in eclipse. I >>> would not call it easy at all. I took the test sources away completely >>> (from >>> the source path). >>> >>> I would like to help putting some useable project files for eclipse >>> together >>> (including the test files ;-) ). >>> >>> Why are classpath files generally not included in open source projects? >>> Would they do any harm? I realise when you get experienced with the >>> software >>> you want to make it slim to make text search faster. But for new people >>> in >>> a project it would be a lot nicer, I think. >>> >>> Is there any way of distribute work on the solr project? I would not like >>> to >>> do a lot of effort to adapt to eclipse if somebody else does it the same >>> time >>> >>> >>> -- >>> View this message in context: >>> http://n3.nabble.com/Eclipse-project-files-tp708987p722342.html >>> Sent from the Solr - Dev mailing list archive at Nabble.com. >>> >>> >>
Re: Eclipse project files...
hkmortensen wrote: I spend about two days last week to import lucene and solr in eclipse. I would not call it easy at all. I took the test sources away completely (from the source path). I share and understand your pain. I would like to help putting some useable project files for eclipse together (including the test files ;-) ). Why are classpath files generally not included in open source projects? I do not have a good answer... I cannot think any good reason why a .classpath and .project file for Eclipse cannot be checked into the repository together with the sources. However, if the project team is using a diverse variety of IDEs, it makes less sense. But, these days, it's possible to generate IDE configuration files via Maven and/or Ant+Ivy. It would be interesting to know what the Lucene and Solr committers normally use: Eclipse? IDEA? Emacs? Vi? ...? Would they do any harm? I realise when you get experienced with the software you want to make it slim to make text search faster. But for new people in a project it would be a lot nicer, I think. +1 Is there any way of distribute work on the solr project? I would not like to do a lot of effort to adapt to eclipse if somebody else does it the same time Paolo
Re: Eclipse project files...
Robert Muir wrote: On Mon, Apr 12, 2010 at 5:15 AM, Paolo Castagna < [email protected]> wrote: For Lucene, I needed two more jars from Ant project: - ant-1.7.1.jar - ant-junit-1.7.1.jar Paolo, I put these in the lib directory now, to hopefully make IDE configuration easier. Thanks, I appreciate. By the way, thanks for your ideas here. I think its worth our time to try to make Lucene/Solr as easy as possible for someone to bring up in their IDE, or we scare people away... Indeed. :-) Paolo
Re: Eclipse project files...
Erick Erickson wrote: <<>> because they're always wrong ... It is possible to get it right and when it happens users will have a much better experience when they checkout the sources of a project. Just a few examples of things I use: - https://jena.svn.sourceforge.net/svnroot/jena/TDB/trunk/.classpath - https://jena.svn.sourceforge.net/svnroot/jena/ARQ/trunk/.classpath - http://svn.apache.org/repos/asf/hadoop/common/trunk/build.xml With Maven and/or Ant+Ivy it's possible to generate Eclipse .classpath and .project files automatically from your pom.xml file or from your ivy.xml (Hadoop does that). If I put mine in c:\apache, and you put yours in c:\trunk, our classpath files will reflect that. And I *really* don't want to update the project and get my classpath file overwritten with yours. Not to mention that I *actually* work on a mac, where Ant has been installed in /usr and... The examples above work on Linux, Windows and should work on Mac OS X as well, there are no absolute paths in the .classpath or .project files. Not to mention other libraries. And what about plugins? That said, one *can* include a sample classpath and, perhaps, project file, that can be copied to "the correct place" and changed to reflect the local setup as has been done on the Wiki, see: http://wiki.apache.org/lucene-java/HowToContribute Eclipse .classpath and .project files can be checked into the source code repository or they can be generated as part of the building system. I'd love to have the same good experience with Lucene and Solr... I am still having problems trying to configure Eclipse to run Solr tests (and yes, I've changed the current directory... but I still have problems). Paolo Best Erick On Thu, Apr 15, 2010 at 5:04 PM, hkmortensen wrote: I spend about two days last week to import lucene and solr in eclipse. I would not call it easy at all. I took the test sources away completely (from the source path). I would like to help putting some useable project files for eclipse together (including the test files ;-) ). Why are classpath files generally not included in open source projects? Would they do any harm? I realise when you get experienced with the software you want to make it slim to make text search faster. But for new people in a project it would be a lot nicer, I think. Is there any way of distribute work on the solr project? I would not like to do a lot of effort to adapt to eclipse if somebody else does it the same time -- View this message in context: http://n3.nabble.com/Eclipse-project-files-tp708987p722342.html Sent from the Solr - Dev mailing list archive at Nabble.com.
Re: Eclipse project files...
<<>> because they're always wrong ... If I put mine in c:\apache, and you put yours in c:\trunk, our classpath files will reflect that. And I *really* don't want to update the project and get my classpath file overwritten with yours. Not to mention that I *actually* work on a mac, where Ant has been installed in /usr and... Not to mention other libraries. And what about plugins? That said, one *can* include a sample classpath and, perhaps, project file, that can be copied to "the correct place" and changed to reflect the local setup as has been done on the Wiki, see: http://wiki.apache.org/lucene-java/HowToContribute Best Erick On Thu, Apr 15, 2010 at 5:04 PM, hkmortensen wrote: > > I spend about two days last week to import lucene and solr in eclipse. I > would not call it easy at all. I took the test sources away completely > (from > the source path). > > I would like to help putting some useable project files for eclipse > together > (including the test files ;-) ). > > Why are classpath files generally not included in open source projects? > Would they do any harm? I realise when you get experienced with the > software > you want to make it slim to make text search faster. But for new people in > a project it would be a lot nicer, I think. > > Is there any way of distribute work on the solr project? I would not like > to > do a lot of effort to adapt to eclipse if somebody else does it the same > time > > > -- > View this message in context: > http://n3.nabble.com/Eclipse-project-files-tp708987p722342.html > Sent from the Solr - Dev mailing list archive at Nabble.com. >
Re: Eclipse project files...
I spend about two days last week to import lucene and solr in eclipse. I would not call it easy at all. I took the test sources away completely (from the source path). I would like to help putting some useable project files for eclipse together (including the test files ;-) ). Why are classpath files generally not included in open source projects? Would they do any harm? I realise when you get experienced with the software you want to make it slim to make text search faster. But for new people in a project it would be a lot nicer, I think. Is there any way of distribute work on the solr project? I would not like to do a lot of effort to adapt to eclipse if somebody else does it the same time -- View this message in context: http://n3.nabble.com/Eclipse-project-files-tp708987p722342.html Sent from the Solr - Dev mailing list archive at Nabble.com.
Re: Eclipse project files...
AFAICT, those are just coding styles. It would be nice to have the project files setup somehow too. On Apr 14, 2010, at 2:40 PM, Chris Hostetter wrote: > > : I think it would be good to put these up on the Wiki. > > We have Eclipse and IDEA configs on the wiki, we just need users of > those IDEs to be proactive about making sure they work well... > > http://wiki.apache.org/solr/HowToContribute#Helpful_Resources > > > -Hoss >
Re: Eclipse project files...
: I think it would be good to put these up on the Wiki. We have Eclipse and IDEA configs on the wiki, we just need users of those IDEs to be proactive about making sure they work well... http://wiki.apache.org/solr/HowToContribute#Helpful_Resources -Hoss
Re: Eclipse project files...
I think it would be good to put these up on the Wiki. On Apr 12, 2010, at 5:15 AM, Paolo Castagna wrote: > Hi Rich, > I felt exactly the same pain last week, when I wanted to have Solr (and > Lucene) configured as Eclipse projects for developing a small patch [1] > (my first to Solr). > > I could have done without Eclipse, but since I might want to post more > patches, I want to have Solr properly configured in Eclipse. > > Other Apache projects, even if they do not commit .classpath and > .project files in SVN, provide a way to create them. > See, for example, Hadoop [2]. > > You can find my .classpath and .project Eclipse files for Lucene and > Solr attached to this email. Be warned, I have included only the minimal > number of contribs and do not consider me an authoritative source of > information for Lucene or Solr. > > For Lucene, I needed two more jars from Ant project: > > - ant-1.7.1.jar > - ant-junit-1.7.1.jar > > I copied them in the ./lucene/lib directory. > > Finally, there are some comments about Eclipse on the Solr wiki [3], > but I did not find them useful. Perhaps, someone from the Solr team, > if using Eclipse, could share his experience. > > "These are the sort of things", he said with bit of sarcasm and humor, "that > make you feel lucky to use Maven." :-) > > Let me know how it goes. > > Paolo > > [1] https://issues.apache.org/jira/browse/SOLR-1531 > [2] https://issues.apache.org/jira/browse/HADOOP-6407 > [3] > http://wiki.apache.org/solr/HowToContribute#Notes_for_Eclipse_and_the_New_Merged_Lucene.2BAC8-Solr_checkout > > Rich Cariens wrote: >> Ahoy ahoy, >> Would anyone be willing to share their Eclipse project files for Solr and >> Lucene? I can go through the motions but I'd rather be consistent with >> other Eclipse users. >> Thanks in advance, >> Rich > -- Grant Ingersoll http://www.lucidimagination.com/ Search the Lucene ecosystem using Solr/Lucene: http://www.lucidimagination.com/search
Re: Eclipse project files...
On Mon, Apr 12, 2010 at 5:15 AM, Paolo Castagna < [email protected]> wrote: > > For Lucene, I needed two more jars from Ant project: > > - ant-1.7.1.jar > - ant-junit-1.7.1.jar > > Paolo, I put these in the lib directory now, to hopefully make IDE configuration easier. By the way, thanks for your ideas here. I think its worth our time to try to make Lucene/Solr as easy as possible for someone to bring up in their IDE, or we scare people away... -- Robert Muir [email protected]
Re: Eclipse project files...
Yes, I meant: File > New > Java Project > Create project from existing source
I also ripped out the backward stuff, benchmark, some other things
that did not compile since Solr does not use them.
I use Eclipse search a lot, and with everything in the project, text
searching takes way too long. Having the individual chunks imported
via the Eclipse 'link source' gives a much slimmer source base. That
is, make an empty Java project and pull in whatever you want as
individual 'Link source' commands in the Build Path.
Another trick is that to run the unit tests from inside Eclipse: run
it, have it fail, edit the configuration it makes, and in the second
tab set the current directory to workspace_loc/src/test/test-files.
The contrib unit tests all have to be set to their own
contrib/project/src/test/test-files or whatever. It would be really
handy if JUnit had an annotation for 'this test wants this relative
current directory'.
On Mon, Apr 12, 2010 at 4:45 PM, Rich Cariens wrote:
> I think that's what Lance meant ("Create project from existing source"). I
> had more luck with that, but I still have around 100 errors in Lucene and 5
> or so in Solr. I'm not worried about it though; I'm pretty sure I can get
> it all sorted out and do what I need to do.
>
> Best,
> Rich
>
> On Mon, Apr 12, 2010 at 7:25 AM, Koji Sekiguchi wrote:
>
>> Paolo Castagna wrote:
>>
>>> Hi,
>>> could you be more precise about 'import project from source tree'.
>>>
>>> I think he suggested
>>
>> File > New > Java Project > Create project from existing source
>>
>> ?
>>
>> Koji
>>
>> --
>> http://www.rondhuit.com/en/
>>
>>
>
--
Lance Norskog
[email protected]
Re: Eclipse project files...
I think that's what Lance meant ("Create project from existing source"). I
had more luck with that, but I still have around 100 errors in Lucene and 5
or so in Solr. I'm not worried about it though; I'm pretty sure I can get
it all sorted out and do what I need to do.
Best,
Rich
On Mon, Apr 12, 2010 at 7:25 AM, Koji Sekiguchi wrote:
> Paolo Castagna wrote:
>
>> Hi,
>> could you be more precise about 'import project from source tree'.
>>
>> I think he suggested
>
> File > New > Java Project > Create project from existing source
>
> ?
>
> Koji
>
> --
> http://www.rondhuit.com/en/
>
>
Re: Eclipse project files...
Paolo Castagna wrote: Hi, could you be more precise about 'import project from source tree'. I think he suggested File > New > Java Project > Create project from existing source ? Koji -- http://www.rondhuit.com/en/
Re: Eclipse project files...
Hi, could you be more precise about 'import project from source tree'. With Eclipse I see only two options which might be what you mean: - File > Import... > General > File System - File > Import... > General > Existing Projects into Workspace None of these two options would work properly with Lucene and/or Solr. I have also tried with: - File > New > Project... > Java Project from Existing Ant Buildfile But, again, no luck. Eclipse complains about javac missing from build.xml since it's in common-build.xml. Thanks, Paolo Lance Norskog wrote: Just say 'import project from source tree' and eclipse will find everything for you. I made two separate projects 'lucene' and 'solr', and 'solr' depends on 'lucene'. If you don't want to compile stuff like contrib/ remove them from the build path. It's hard to get rid of files you don't want to scan with a full project search, which I do all the time. On Fri, Apr 9, 2010 at 11:42 AM, Rich Cariens wrote: Ahoy ahoy, Would anyone be willing to share their Eclipse project files for Solr and Lucene? I can go through the motions but I'd rather be consistent with other Eclipse users. Thanks in advance, Rich
Re: Eclipse project files...
Just say 'import project from source tree' and eclipse will find everything for you. I made two separate projects 'lucene' and 'solr', and 'solr' depends on 'lucene'. If you don't want to compile stuff like contrib/ remove them from the build path. It's hard to get rid of files you don't want to scan with a full project search, which I do all the time. On Fri, Apr 9, 2010 at 11:42 AM, Rich Cariens wrote: > Ahoy ahoy, > > Would anyone be willing to share their Eclipse project files for Solr and > Lucene? I can go through the motions but I'd rather be consistent with > other Eclipse users. > > Thanks in advance, > Rich > -- Lance Norskog [email protected]
Eclipse project files...
Ahoy ahoy, Would anyone be willing to share their Eclipse project files for Solr and Lucene? I can go through the motions but I'd rather be consistent with other Eclipse users. Thanks in advance, Rich
