On Thu, Jun 14, 2012 at 7:20 AM, Alex Hall <[email protected]> wrote: > I did a check-out of the Jena source from SVN, and now I'm having a little > bit of trouble getting it set up in Eclipse. > > I'm using Eclipse 3.7 (Indigo) on Windows, Jave EE distribution, with the > m2e Maven plugin. > > When I import the Jena projects as Maven projects, they build (albeit with > Maven warnings) but m2e generates a lot of cruft that gets SVN confused, > which tells me that this isn't the way folks normally develop in Eclipse > (else the :svn-ignore properties would have been set up to ignore this > stuff).
I use Eclipse and m2e, and I too see a bunch of cruft (.project/.classpath files and the .settings directory). Personally, I'd love to remove and svn ignore em, but I think other developers use them :) > When I import the Jena projects as a regular Java project, I get unresolved > build dependencies because (for example) jena-core is looking for the > latest jena-iri snapshot in my Maven repository. I think this will work if > I do a 'mvn clean install' from the Jena root directory, but it also seems > that if I do this, changes will not propagate from one project to another > without doing a mvn build/install cycle. > > Any guidance on how the best way to set this up is? I would recommend using m2e and either add those eclipse files to your SVN global ignore (a client-side property for the your whole machine) or pretend you don't see them hanging around (easier to do in a graphical SVN client than command line). -Stephen
