I tried the mvn eclipse:eclipse and it does generate .project and .classpath files. Unfortunately, it generates two sets of them: one in /core and one in /examples. I copied the relevant entries from the /examples version into my main .classpath and Eclipse now seems to be happy.
Thanks,
Jeff

Grant Ingersoll wrote:
I think you can do "mvn eclipse:eclipse" and it will generate an Eclipse file for you. I'm not an Eclipse user, so YMMV.

I'll look into the tarball issue tonight.

On Mar 3, 2009, at 5:07 PM, Jeff Eastman wrote:

Re: my last post.

The trunk checkout actually does compile, so I must have used the wrong "release" tarball. On my Mac, I had to set the default Java compiler to the 1.6 version to make maven in a text window compile. To get the Eclipse maven plugin to work, I also had to set the Eclipse default JRE to 1.6 even though the project's JRE was set to 1.6.

My problem with Eclipse is getting its classpath set so it can find the lib jars and do its normal compile thing. I understand they are buried somewhere in .m2/repository?

Jeff
<jeastman.vcf>

--------------------------
Grant Ingersoll
http://www.lucidimagination.com/

Search the Lucene ecosystem (Lucene/Solr/Nutch/Mahout/Tika/Droids) using Solr/Lucene:
http://www.lucidimagination.com/search




begin:vcard
fn:Jeff Eastman
n:Eastman;Jeff
org:Windward Solutions Inc.
adr:;;;Los Altos;CA;;USA
email;internet:[email protected]
title:President
tel;pager:http://[email protected]
tel;cell:+1.415.298.0023
x-mozilla-html:TRUE
url:http://www.windwardsolutions.com
version:2.1
end:vcard

Attachment: PGP.sig
Description: PGP signature

Reply via email to